7i76e was working, now CR1 LED does not go off

More
7 years 7 months ago #130039 by macla
Here is the output from the "verbose" command.
I noticed one thing, though: When I apply power with an external 5V supply, but no field power to TB1, I can issue the "verbose" command and get the reply, as attached. I cannot launch Linuxcnc, as this requires field power.
If I then also apply 12V to the field bus on TB1, I can launch Linuxcnc, but the "mesaflash --device 7i76e --verbose" returns "No 7i76e device detected".
I seem to loose ethernet connection when the field power is attached

Please Log in or Create an account to join the conversation.

More
7 years 7 months ago #130040 by PCW
That's very odd since the field I/O section is completely isolated from the Ethernet part
Power supply issue of some kind?

Can you ping the card with field power applied?

Please Log in or Create an account to join the conversation.

More
7 years 7 months ago #130042 by macla
I can ping and use mesaflash with both 5V and 12V field power as long as Linuxcnc is not running. But when I start linuxcnc, CR1 goes yellow and I am no longer allowed to ping from the terminal. With linuxcnc started I also get no replies when using mesaflash (it cannot find the 7i76e)

Please Log in or Create an account to join the conversation.

More
7 years 7 months ago #130044 by PCW
That's correct, access to the card is blocked when linuxCNC is running

Please Log in or Create an account to join the conversation.

More
7 years 7 months ago #130046 by macla
Is there a way to debug what is going wrong during the startup of Linuxcnc? Why does the init fail at 7i76e? We now know the eeprom isn't corrupt, but when linuxcnc is starting up, I guess a startup sequence is initiated in the 7i76e. Can I get a log out or similar?

Please Log in or Create an account to join the conversation.

More
7 years 7 months ago - 7 years 7 months ago #130047 by PCW
/INIT _and_ /DONE going on at power up is a indication of failure to load the FPGA
(bad CRC for example)

/INIT going on by itself is an indication of

1. Watchdog bite or
2. Some kind of protocol or packet error
Last edit: 7 years 7 months ago by PCW.

Please Log in or Create an account to join the conversation.

Moderators: PCW, jmelson
Time to create page: 0.351 seconds
Powered by Kunena Forum