• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Fieldbus Ports not working
#1
Hello,

i have to use the Fieldbus Ports as normal Ethernet Ports. I installed the Docker Container as explained here: https://github.com/HilscherAutomation/ne...hernet-lan

I cant get any access to the ports, not even the LED of the Ports are blinking

With another netPi RTE3 its working.

Docker Log:
starting ssh ...

Starting OpenBSD Secure Shell server: sshd.

Waiting for added 'cifx0' network interface ...

'cifx0' network interface not ready in time

nnot find device "cifx0"

nnot find device "cifx0"

cifx0 ip address/subnet mask set to 192.168.140.6/255.255.255.0
  Reply
#2
Well, the netX controller chip on netPI RTE 3 has 4 LEDs that are basically telling in which state the industrial network controller chip is.

Those are the upper four LEDs on netPI's front named NS, MS, APL and SYS. Please tell me the status of these?

Also very important is that no other container is using the netX controller the same time the LAN container occupies the netX for its purpose. Can you confirm?
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#3
The SYS-LED is blinking Green/Yellow.
The LAN Container is the only one that is running.
  Reply
#4
Well LED flashing green/yellow means the netX chip is not loaded with any firmware or software. So in this case it is quite natural that your two RJ45 ports do not indicate any LED activity since the PHYs are not enabled.

By default netPI RTE 3 is delivered with a PROFINET IO device firmware loaded in netX controller. For me a flashing LED green/yellow means that there was indeed a try from any host software package to load a new firmware to the netX chip ... which apparantly was your LAN container. At the moment I have no explanation why it failed.

But with flashing green/yellow netX chip is still operational and waiting to accept a new software. So what is if you restart the container ... what happens then in the log file?

Thx
Armin
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#5
It was blinking from the first start.
With a restart of the container the log shows the following:
Starting OpenBSD Secure Shell server: sshd.


Waiting for added 'cifx0' network interface ...


'cifx0' network interface not ready in time


nnot find device "cifx0"


nnot find device "cifx0"


cifx0 ip address/subnet mask set to 192.168.140.6/255.255.255.0


terminating ssh ...


Stopping OpenBSD Secure Shell server: sshd.


starting ssh ...


Starting OpenBSD Secure Shell server: sshd.


Waiting for added 'cifx0' network interface ...


'cifx0' network interface not ready in time


nnot find device "cifx0"


nnot find device "cifx0"


cifx0 ip address/subnet mask set to 192.168.140.6/255.255.255.0
  Reply
#6
Well, before the netPIs are packaged in the cardboard box the two RJ45 ports are physically tested with a loop ethernet cable. So the chip must have been worked well.

I cannot exclude that meanwhile something happened with your netX chip, its internal security chip and and and... . This is the first time I see a netX chip of being not loadable any more on netPI.

So I can just recommend you to send back this device to hilscher repair and you will get an immediate replacement. Sorry for this inconvenience.

Before you send it back, can you please tell me the MAC address that is printed outside on the label please.

Thx
Armin
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#7
Thanks Armin,

the MAC-Address is: B827EBCEA272
  Reply
#8
Hello Schoko,

I got your device you sent back and examined the unit.

Based on the written log file under /opt/cifx/cifX0.log I found out that indeed loading the firmware into netX controller failed.

The first thing I did was to modify the container in that way that the driver in case of such an error also outputs the log file to the Web-GUI in order to have better diagnostics in future.

The log file contained the following error:
28.10.2019 14:41:09.517.679: Error downloading firmware to device '/opt/cifx/deviceconfig/FW/channel0//R160D000.nxf'- (lRet=0x00006196)!

Based on internal Hilscher documentation the referenced error 0x00006196 means "File system inconsistent, needs reformatting". In other words the firmware download procedure is not able to load a firmware since the file system in netX controller is corrupt by any reason (maybe power loss during firmware download).

I changed the cifX0deamon application now accordingly to send a format command to netX controller whenever it indicates not to have a valid firmware running. With this new setup I got your device back into running state and netX SYS LED is now static green as it should. With this new daemon a recovery is handled automatically in future in case a netX file system is getting corrupt.

Thx
Armin
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  [SOLVED] activate LED1/2 with Node-RED + fieldbus nodes container Christian_Rau 6 89 October-21st-2019, 10:30 AM
Last Post: Armin@netPI
  netPI Node-Red fieldbus node Error PersEE 5 53 October-8th-2019, 03:55 PM
Last Post: Armin@netPI
  [SOLVED] Help with fieldbus node Farani 5 48 August-20th-2019, 07:22 AM
Last Post: Armin@netPI
  [SOLVED] netPI stops working (502 - Bad Gateway) Andi 3 38 June-19th-2019, 03:58 PM
Last Post: Andi
  [SOLVED] WebConfig netpi-nodered-fieldbus JohnyD94 13 66 May-6th-2019, 12:20 AM
Last Post: JohnyD94
  Modbus TCP Connection via RTE Ethernet Ports Flo_Lo 18 481 April-15th-2019, 09:50 PM
Last Post: Armin@netPI
  [SOLVED] hilschernetpi/netpi-nodered-fieldbus Fieldbus configurator can't be open Andreas 6 201 June-11th-2018, 09:12 AM
Last Post: Armin@netPI
  [SOLVED] Modifying ports after container is being added. SteveO 2 132 May-9th-2018, 02:39 PM
Last Post: SteveO
  3 Network Ports possible on NIOT-E-NPI3-51-EN-RE? yulian 7 199 April-3rd-2018, 02:57 PM
Last Post: Armin@netPI
  fieldbus in error Schranz 7 165 March-13th-2018, 07:28 AM
Last Post: Armin@netPI

Forum Jump:


Users browsing this thread: 1 Guest(s)