Firmware File Names 6/18
Specification
Firmware
File Names
Hilscher Gesellschaft für Systemautomation mbH
www.hilscher.com
DOC101102SPC03EN | Revision 3 | English | 2013-11 | Released | Confidential
Firmware | File Names
DOC101102SPC03EN | Revision 3 | English | 2013-11 | Released | Confidential © Hilscher, 2011-2012
Firmware File Names 6/18
Table of Contents
1 Introduction 3
1.1 About this Document 3
1.2 List of Revisions 3
2 Firmware File Names 4
2.1 Existing Names 4
2.2 Requirements 5
2.3 Firmware File Names 6
2.3.1 Overview Structure 6
2.3.2 1. Letter for Device Family and 2. Letter for Device Form 6
2.3.3 3. Letter for CPU Power (netX Type) 7
2.3.4 4. and 5. Letter for the Primary Protocol and 6. and 7. Letter for Secondary Protocol 8
2.3.5 8. Letter – Hardware Compatibility Index (HWI) 15
2.3.6 Examples 15
3 Appendix 16
3.1 List of Tables 16
3.2 Contacts 17
Firmware | File Names
DOC101102SPC03EN | Revision 3 | English | 2013-11 | Released | Confidential © Hilscher, 2011-2012
Firmware File Names 6/18
1 Introduction
1.1 About this Document
This manual specifies the file names for loadable firmware for Hilscher products.
1.2 List of Revisions
Rev / Date / Name / Chapter / Revision /1 / 2011-09-22 / HH / all / Created
2 / 2012-04-23 / HH / 2.3.2 / netRAPID and EATON Gateway in Table 3 added
2.3.3 / netX 51 and netX 52 in Table 4 added
2.3.4 / SmartWire-DT Master in Table 5 added
3 / 2012-05-09 / HH / 2.3.2 / netSMART Gateway in Table 3 added
2012-06-04 / AB / 2.3.2 / Basic (B500) for netHMI in Table 3 added
2012-06-05 / HH / 2.3.4 / Table 9: QVis added
2012-08-09 / HH / 2.3.4 / Table 5: Marshaller added
2012-09-11 / HH / 2.3.2 / Table 3: netDIMM added
2013-04-03 / HH / 2.3.2 / Table 3: netHOST added
2013-06-04 / AB / 2.3.4 / Table 5: Modbus RTU Slave Only added
2013-11-29 / HH / 2.3.4 / To name firmware files that contain a limited protocol stack the 4. or 6. letter is ‘Z’.
Table 1: List of Revisions
Firmware | File Names
DOC101102SPC03EN | Revision 3 | English | 2013-11 | Released | Confidential © Hilscher, 2011-2012
Firmware File Names 6/18
2 Firmware File Names
2.1 Existing Names
Names used today (2011)
CIFX (netX 100) cifxdpm.nxf
COMX (netX 100) comxecm.nxf
NT 50 N5COSASC.NXF
NT 100 NTCOSCOM.NXF
NB 100 NBEISCOM.NXF
NIC 50 NICMBCPS.NXF
NICPNSFO.NXF
NPLC 100 (CoDeSys) NPC1CDPM.NXF
NPLC 100 (IBH S7) S7PLC.NXF
Problem: Missing (2011)
COMX 10, NIC 10, NJ 10, NJ 50, NJ 100, NJ 500
2.2 Requirements
Keep existing
SYCON.net uses for NT 50 (N5xxxxxx.NXF), NT 100 (NTxxxxxx.NXF), NB 100 (NBxxxxxx.NXF). These names have to be kept as they are!
netX Configuration Tool uses CIFXxxx.NXF respectively NICMBxxx.NXF. These names have to be kept as they are!
L51NPSDL.NXF is used for Firmware for NL 51N-DPL
Use new systematic for new types
netX 10 and netX 50 and netX 100/500 each has its own firmware compilation! As a result of this, the netX type has to be part of the firmware name.
COMX will have PROFIBUS-DP Slave for COMX 10 and COMX 100
NJ will have hardware with netX 10, netX 50, netX 100 and netX 500.
netIC will have NIC 10-CCS (and NIC 50-CCS)
NXF / netX 10 / netX 50 / netX 100 / netX 500 /CIFX C / - / - / CIFXDPM / -
COMX M / new needed / new needed / COMXDPM / -
netIC I / new needed / NICMBCPS / - / -
netTAP T / - / N5COSASC / NTEISCOM / -
netBRICK B / - / - / NBEISCOM / -
netJACK J / new needed / new needed / new needed / new needed
netLINK L
netPAC P
netPLC S / NPC1CDPM
netHMI H
netX X / new needed? / NX50DPS / NX100S3M / NX500DPS
Open Points
Firmware name for Fiber Optics.
2.3 Firmware File Names
2.3.1 Overview Structure
The firmware name has to match the 8+3 (DOS) convention. The 8 characters are specified below. The file extension for a firmware file is always .NXF and for a firmware module .NXO.
1. Letter / 2. Letter / 3. Letter / 4. Letter / 5. Letter / 6. Letter / 7. Letter / 8. Letter /Device family / Device Form / CPU Power
(netX Type) / Primary Protocol / Secondary Protocol / HWI (Hardware Compatibility Index)
Table 2: Firmware Name - Overview Structure
General naming: Hardware first, then protocol
2.3.2 1. Letter for Device Family and 2. Letter for Device Form
Device Family / 1. Letter / Device Form / 2. Letter /netBRICK / B / - / 0 (zero)
CIFX / C / - / 0 (zero)
netDIMM / D / - / 0 (zero)
EU5C (EATON Gateway) / E / - / 0 (zero)
netHOST / F / T100 / T
netSMART Gateway / G / - / 0 (zero)
netHMI / H / J500 (Jack)
B500 (Basic) / J
B
netIC / I / Standard / 0 (zero)
Fiber optic (FO) / F
netJACK / J / - / 0 (zero)
netLINK / L / U (USB)
N (Ethernet) / U
N
COMX / M / - / 0 (zero)
(do not use O) / O / -
netPAC / P / - / 0 (zero)
netRAPID / R / - / 0 (zero)
netPLC / S / C100
D100
J100/J500
M100
T100 / C
D
J
M
T
netTAP / T / - / 0 (zero)
netX / X / - / 0 (zero)
rcX base firmware
Table 3: Firmware Name – 1. and 2. Letter
Remark: A loadable firmware for netX starts with X0 and ends with .NXF and a rcX base firmware starts with X0 and ends with .NXO.
2.3.3 3. Letter for CPU Power (netX Type)
/ 3. Letter (Number) /netX 5 / 4
netX 6 / 8
netX 10 / 5
netX 50 / 3
netX 51 / 6
netX 52 / 7
netX 100 / 2
netX 500 / 1
Table 4: Firmware Name – 3. Letter
Remark: The numbering is 1, 2, …, 9, A, B, …, N, P, … and Z (Letter O must not be used).
2.3.4 4. and 5. Letter for the Primary Protocol and 6. and 7. Letter for Secondary Protocol
Protocol / 4. and 5. Letter (Number)6. and 7. Letter (Number) /
rcX / 00
PROFIBUS DP Master / 01
PROFIBUS DP Slave / 02
PROFIBUS MPI / 03
CANopen Master / 04
CANopen Slave / 05
DeviceNet Master / 06
DeviceNet Slave / 07
AS-Interface Master / 08
CC-Link Slave / 09
CompoNet Slave / 0A
IO-Link Master / 0B
PROFINET IO Controller / 0C
PROFINET IO Device / 0D
EtherCAT Master / 0E
EtherCAT Slave / 0F
EtherNet/IP Scanner/Master / 0G
EtherNet/IP Adapter/Slave / 0H
sercos III Master / 0I
sercos III Slave / 0J
POWERLINK Controlled Node / 0K
Open Modbus/TCP / 0L
RFC 1006 / 0M
DF1 / 0N
must not be used / (no letter O)
3964R / 0P
ASCII / 0Q
Modbus RTU (Master/Slave) / 0R
netSCRIPT (Programmable Serial) / 0S
Varan Client (Server) / 0T
SmartWire-DT Master / 0U
Marshaller / 0V
Modbus RTU Slave only / 0W
Reserved / 0X
Reserved / 0Y
Reserved / 0Z
Table 5: Firmware Name – 4., 5., 6. and 7. Letter (0x)
Protocol / 4. and 5. Letter (Number)6. and 7. Letter (Number)
Http Atvise (Ethernet) / 10
PROFIBUS DP Master and CoDeSys / 11
12
13
14
15
DeviceNet Master (implies CANopen 3S) and CoDeSys / 16
17
18
19
1A
1B
PROFINET IO Controller and CoDeSys / 1C
1D
1E
1F
EtherNet/IP Scanner/Master and CoDeSys / 1G
1H
1I
1J
1K
1L
1M
1N
(1O no letter O must be used)
1P
1Q
1R
1S
1T
1U
1V
1W
1X
1Y
CoDeSys and local I/O / 1Z
Table 6: Firmware Name – 4., 5., 6. and 7. Letter (1x)
Protocol / 4. and 5. Letter (Number)6. and 7. Letter (Number)
20
PROFIBUS DP Master and ProConOS eCLR / 21
22
23
CANopen Master and ProConOS eCLR / 24
25
DeviceNet Master and ProConOS eCLR / 26
27
28
29
2A
2B
2C
2D
2E
2F
2G
2H
2I
2J
2K
2L
2M
2N
(2O no letter O must be used)
2P
2Q
2R
2S
2T
2U
2V
2W
2X
2Y
ProConOS eCLR and local I/O / 2Z
Table 7: Firmware Name – 4., 5., 6. and 7. Letter (2x)
Protocol / 4. and 5. Letter (Number)6. and 7. Letter (Number)
30
PROFIBUS DP Master and IBH S7 / 31
32
33
CANopen Master and IBH S7 / 34
35
DeviceNet Master and IBH S7 / 36
37
38
39
3A
3B
3C
3D
3E
3F
3G
3H
3I
3J
3K
3L
3M
3N
(3O no letter O must be used)
3P
3Q
3R
3S
3T
3U
3V
3W
3X
3Y
IBH S7 and local I/O / 3Z
Table 8: Firmware Name – 4., 5., 6. and 7. Letter (3x)
Protocol / 4. and 5. Letter (Number)6. and 7. Letter (Number)
QViS (without a protocol) / 40
41
42
QViS and PROFIBUS MPI / 43
44
45
46
47
48
49
4A
4B
4C
4D
4E
4F
4G
4H
4I
4J
4K
QViS and Open Modbus/TCP / 4L
QViS and RFC 1006 / 4M
QViS and DF1 / 4N
(4O no letter O must be used)
4P
4Q
QViS and Modbus RTU (Master/Slave) / 4R
4S
4T
4U
4V
4W
4X
4Y
4Z
Table 9: Firmware Name – 4., 5., 6. and 7. Letter (4x)
(not defined CDS remote V2, CDS remote V3)
Protocol / 4. and 5. Letter (Number)6. and 7. Letter (Number)
reserved / 50 ... YZ
Table 10: Firmware Name – 4., 5., 6. and 7. Letter (50 … YZ)
Continued on next page.
To name firmware files that contain a limited protocol stack the 4. or 6. letter is ‘Z’.
6. and 7. Letter (Number) /
Reserved / Z0
PROFIBUS DP Master Limited / Z1
PROFIBUS DP Slave Limited / Z2
PROFIBUS MPI Limited / Z3
CANopen Master Limited / Z4
CANopen Slave Limited / Z5
DeviceNet Master Limited / Z6
DeviceNet Slave Limited / Z7
AS-Interface Master Limited / Z8
CC-Link Slave Limited / Z9
CompoNet Slave Limited / ZA
IO-Link Master Limited / ZB
PROFINET IO Controller Limited / ZC
PROFINET IO Device Limited / ZD
EtherCAT Master Limited / ZE
EtherCAT Slave Limited / ZF
EtherNet/IP Scanner/Master Limited / ZG
EtherNet/IP Adapter/Slave Limited / ZH
sercos III Master Limited / ZI
sercos III Slave Limited / ZJ
POWERLINK Controlled Node Limited / ZK
Open Modbus/TCP Limited / ZL
RFC 1006 Limited / ZM
DF1 Limited / ZN
must not be used / (no letter O)
3964R Limited / ZP
ASCII Limited / ZQ
Modbus RTU (Master/Slave) Limited / ZR
netSCRIPT (Programmable Serial) Limited / ZS
Varan Client (Server) Limited / ZT
SmartWire-DT Master Limited / ZU
Marshaller Limited / ZV
Modbus RTU Slave only Limited / ZW
Reserved / ZX
Reserved / ZY
Reserved / ZZ
Table 11: Firmware Name – 4., 5., 6. and 7. Letter (Zx)
2.3.5 8. Letter – Hardware Compatibility Index (HWI)
The 8. letter is exactly the value of the Hardware Compatibility Index, which is in the security memory.
0 (zero), 1 (one), 2 (two), etc.
2.3.6 Examples
netLINK
NL 50-MPI: The NL 50-MPI has to be compatible with the NL-MPI. Therefore it has its own firmware name, which is NL50MPI.E50
NL 50N-MPI-ATVISE: LN510030.NXF
NL 10U-DP with PROFIBUS-DP Master: LU501000.NXF
netPLC
NPLC-T100-DP/S7/ATVISE: ST210310.NXF
3 Appendix
3.1 List of Tables
Table 1: List of Revisions 3
Table 2: Firmware Name - Overview Structure 6
Table 3: Firmware Name – 1. and 2. Letter 6
Table 4: Firmware Name – 3. Letter 7
Table 5: Firmware Name – 4., 5., 6. and 7. Letter (0x) 8
Table 6: Firmware Name – 4., 5., 6. and 7. Letter (1x) 9
Table 7: Firmware Name – 4., 5., 6. and 7. Letter (2x) 10
Table 8: Firmware Name – 4., 5., 6. and 7. Letter (3x) 11
Table 9: Firmware Name – 4., 5., 6. and 7. Letter (4x) 12
Table 10: Firmware Name – 4., 5., 6. and 7. Letter (50 … YZ) 13
Table 11: Firmware Name – 4., 5., 6. and 7. Letter (Zx) 14
3.2 Contacts
HeadquartersGermany
Hilscher Gesellschaft für
Systemautomation mbH
Rheinstrasse 15
65795 Hattersheim
Phone: +49 (0) 6190 9907-0
Fax: +49 (0) 6190 9907-50
E-Mail:
Support
Phone: +49 (0) 6190 9907-99
E-Mail:
Subsidiaries
China
Hilscher Systemautomation (Shanghai) Co. Ltd.
200010 Shanghai
Phone: +86 (0) 21-6355-5161
E-Mail:
Support
Phone: +86 (0) 21-6355-5161
E-Mail:
France
Hilscher France S.a.r.l.
69500 Bron
Phone: +33 (0) 4 72 37 98 40
E-Mail:
Support
Phone: +33 (0) 4 72 37 98 40
E-Mail:
India
Hilscher India Pvt. Ltd.
New Delhi - 110 065
Phone: +91 11 43055431
E-Mail:
Italy
Hilscher Italia S.r.l.
20090 Vimodrone (MI)
Phone: +39 02 25007068
E-Mail:
Support
Phone: +39 02 25007068
E-Mail: / Japan
Hilscher Japan KK
Tokyo, 160-0022
Phone: +81 (0) 3-5362-0521
E-Mail:
Support
Phone: +81 (0) 3-5362-0521
E-Mail:
Korea
Hilscher Korea Inc.
Suwon, Gyeonggi, 443-734
Phone: +82 (0) 31-695-5515
E-Mail:
Switzerland
Hilscher Swiss GmbH
4500 Solothurn
Phone: +41 (0) 32 623 6633
E-Mail:
Support
Phone: +49 (0) 6190 9907-99
E-Mail:
USA
Hilscher North America, Inc.
Lisle, IL 60532
Phone: +1 630-505-5301
E-Mail:
Support
Phone: +1 630-505-5301
E-Mail:
Firmware | File Names
DOC101102SPC03EN | Revision 3 | English | 2013-11 | Released | Confidential © Hilscher, 2011-2012