Q

Which LFW - Loadable Firmware Variants - are offered for netX 90?

Does netX 90 Loadable Firmware feature a OPC-UA server and/or MQTT client?

A

Hilscher offers different types of firmware with different feature sets.

Firmware Type	LFW Variant	Features	supported DPM channels	external memory required SQI Fash, SDRAM	Flash Layout
Type 1	Legacy Fieldbus	Legacy Fieldbus PROFIBUS, ...	channel 0	not required	use case A, B
Type 2	Real Time Ethernet	Real-Time Ethernet PROFINET, EthernetIP, EtherCAT, OpenModbus TCP, ... Basic Webserver for Firmwareupdate over network, Web Interface API	channel 0 channel 1	not required	use case A, B
Type 3	Real Time Ethernet + Webserver	Real-Time Ethernet PROFINET, EthernetIP, EtherCAT Extended Web Server Basic functionality plus webpage content delivery from flash filesystem	channel 0 channel 1	yes	use case C
Type 4	Real Time Ethernet + IIoT	Real-Time Ethernet PROFINET, EthernetIP, EtherCAT Extended Web Server Basic functionality plus webpage content delivery from flash filesystem IIoT OPC UA OPC-UA server via netPROXY Interface MQTT will not be supported in the first version of this LFW	channel 0 channel 1 channel 2	yes	use case C

LFW Software Structure

Type 4: Full feature set including IIoT

Type 3: Real-Time Ethernet plus extended Webserver

Type 2: Plain Real-Time Ethernet Functinality, including basic Webserver

Flash Layout use cases

Firmware Filenames

The Loadable Firmwares - LFWs - are provided as momolithic binary files (suffix *.nxi and *.nxe)
This firmware is executed on the netX 90 COM (communication) side.

LFWs for netx 90 chip or netRAPID 90 chip carrier are commercial products and must be licenced by Hilscher.
Please contact sales@hilscher.com for further information.

Different use cases (A, C) require dedicated LFW files with unique filenames.

X*0.nxi: type 1 or 2 LFW, use case A/B, external Flash and SDRAM is optional
X*1.nxi: type 3 LFW, use case C, external Flash and SDRAM is mandatory

Please refer also to the description of Firmware Filename Definition

Please assure that the matching Hardware Config (*.hwc) and Flash Device Label (*.fdl) files
are loaded together with the LFW into the flash memory of netX 90.
The use cases require different FDLs.

Video Tutorial

Software Architecture LFW - netX 90

See also...

Page:

A Raspberry Pi supports multiple SPI signals, which ones are used for communication between RPi and netHAT?
Page:

Can other expansion HAT boards be used in combination with the netHAT?
Page:

Is other protocol fimware than PROFINET, EtherCAT and EtherNet/IP available for netHAT?
Page:

The SYS LED of netHAT flashing alternately yellow and green, is this normal?
Page:

How fast can be the data update cycle with an application running above netHAT?
Page:

Where can I find API documentation about the netHAT supported protocols?
Page:

Is there a 3D CAD model of the netHAT available?
Page:

A netX52 chip could support multiple communication channels at a time, does the netHAT support more than one channel?
Page:

Can I use netHAT with more than 32 bytes inputs or outputs?
Page:

Which operating systems does the netHAT support?
Page:

Which SD card size do I require?
Page:

Whom should I contact if I have technical questions relating to the netHAT?
Page:

Which power supply unit do I require?
Page:

Where can I find documentation and further information of the netHAT module?
Page:

Supported Flash Types netX100/500

Browser not supported