
adccommunitymod (AutomationDirect) asked a question.
H0-ECOM100 in a DL06 has error light after trying to update firmware
Created Date: July 20,2016
Created By: commander
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
I was updating the firmware using Netedit3. The transfer stopped and the module disappeared from the network list. I now have an error light on the H0-ECOM100 module. Cycling power does not clear the fault. I cannot restore the default settings because Netedit3 does not see it. Is there some way to clear the module and restore it using the jumpers? I installed another H0_ECOM100 module and that one is working.
Created Date: July 20,2016
Created by: commander
I was updating the firmware using Netedit3. The transfer stopped and the module disappeared from the network list. I now have an error light on the H0-ECOM100 module. Cycling power does not clear the fault. I cannot restore the default settings because Netedit3 does not see it. Is there some way to clear the module and restore it using the jumpers? I installed another H0_ECOM100 module and that one is working.
Created Date: July 20,2016
Created by: kewakl
What version of netedit3?
Created Date: July 21,2016
Created by: Do-more PE
We need to know what mode it is stuck in. Here are the blink codes:
2 blinks - Firmware is not running (i.e. ECOM/ECOM100 is stuck in its booter): This is usually remedied either by updating the firmware using NetEdit3, or simply power cycling.
3 blinks - There is a problem initializing the Ethernet interface: This could be a hardware problem. Try disconnecting the Ethernet cable and power cycling. If it doesn't go away, you will need to have the ECOM/ECOM100 repaired.
4 blinks - Booter version is not valid for firmware: This is remedied by updating the booter, or downgrading the firmware using NetEdit3.
Created Date: July 22,2016
Created by: commander
Using NetEdit Version 3.14a
I was told the error light was ON. He did not mention it was blinking.
Created Date: July 22,2016
Created by: Do-more PE
The answer then is a definite maybe. It really all depends on what the error light is doing. If it is steady on or it is 3 blinks and NetEdit can't find the card then it is probably bad and would need to be sent back to the manufacturer to potentially be repaired.
If it is 2 blinks or 4 blinks then it will likely be able to be fixed by NetEdit. You might have to set dip switch 6 on and power cycle to clear the IP address from the card, then turn it back off and power cycle again to see if it appears in NetEdit. If not then it is probably bad and could be potentially repaired by the manufacturer.
Created Date: July 28,2016
Created by: commander
Thanks Do-more PE.