So this would be the second time this has happened while a co-worker is developing a project on these. the first time we thought it was just an off chance that it died, but now it's starting to look like a consistent problem with these.
apparently this has happened while doing a download, at some point the download just fails and says it couldn't finish the download and there was a problem (he didn't screenshot the error unfortunately....). After this only the Enet and SD lights remain on, but they are on permanently, no blinking or anything. Run light never comes on, and if you wait a few minutes the controller faults out to the solid red fault light.
Removing power and starting back up. the top four of the six lights will flash in a powerup sequence and then it goes back to a solid Enet and SD light.
Notes on the symptoms.
Enet light is on regardless of there being an ethernet connection in it.
SD light is on regardless of the presence of a card in the slot.
If you power up the unit with an SD card in it, it will flash the SD light like it's attempting to read it, but all attempts to use the SD card to change the IP, revert firmware, put it in Program mode, etc, all fail. Nothing happens after the few flashes of the SD. Multiple SD cards have been tried, all are known good and class 10 Fat 16/32 formatted to match the 820.
Ethernet won't show up at all anymore, it doesn't show up on dhcp or bootp either. there is basically a constant startup activity on the ethernet, even while pinging the IP it was set to before the incidents. both orange and green LED for the ethernet remain on solid the entire time save for one flash on startup.
Attempted to connect to it through the serial comms and that won't show up either, it's likely stuck in some kind of boot sequence.
The lack of physical reset button, run/program switch, or other physical switches and accesibilities that normally help you restore a dead or faulted controller are a huge problem with these things. they make it pretty much impossible to do any troubleshooting other than cross your fingers and hope it does what it's supposed to behind the veil of secrecy within the ports that you can't even verify are operating right.
apparently this has happened while doing a download, at some point the download just fails and says it couldn't finish the download and there was a problem (he didn't screenshot the error unfortunately....). After this only the Enet and SD lights remain on, but they are on permanently, no blinking or anything. Run light never comes on, and if you wait a few minutes the controller faults out to the solid red fault light.
Removing power and starting back up. the top four of the six lights will flash in a powerup sequence and then it goes back to a solid Enet and SD light.
Notes on the symptoms.
Enet light is on regardless of there being an ethernet connection in it.
SD light is on regardless of the presence of a card in the slot.
If you power up the unit with an SD card in it, it will flash the SD light like it's attempting to read it, but all attempts to use the SD card to change the IP, revert firmware, put it in Program mode, etc, all fail. Nothing happens after the few flashes of the SD. Multiple SD cards have been tried, all are known good and class 10 Fat 16/32 formatted to match the 820.
Ethernet won't show up at all anymore, it doesn't show up on dhcp or bootp either. there is basically a constant startup activity on the ethernet, even while pinging the IP it was set to before the incidents. both orange and green LED for the ethernet remain on solid the entire time save for one flash on startup.
Attempted to connect to it through the serial comms and that won't show up either, it's likely stuck in some kind of boot sequence.
The lack of physical reset button, run/program switch, or other physical switches and accesibilities that normally help you restore a dead or faulted controller are a huge problem with these things. they make it pretty much impossible to do any troubleshooting other than cross your fingers and hope it does what it's supposed to behind the veil of secrecy within the ports that you can't even verify are operating right.
