Created Date: March 16,2006

Created by: rex2802

I have tried the examples in the manual, but cannot still cannot reset the faults.

I can inhibit the EBC 'c but X330 never comes ON. The manual example mentions resetting Terminator I/O modules. I am using the H2-EBC in standard racks.

Sometimes I can clear the error by a power cycle to the faulted rack. Most times I can only reset the fault by using ERM workbench.

I must be over looking something.

Created Date: March 21,2006

Created by: rex2802

The error exists in the PLC Input (X300-X303) assigned to the respective EBC module. The EBC module error LED is OFF, but the I/O isn't updated in the EBC.

I end up going resetting the error using ERM Workbench. That's the only way I 've been able to clear the error bit. (X300-X303). The error shows up Yellow in ERM not Red. I haven't figured it out yet.

Created Date: March 21,2006

Created by: franji1

First, what is causing the error? Is the ERM's watchdog firing? You may need to enable the Pet frequency in the ERM configuration (set it to HALF the Watchdog value). If it's not a timeout, what is the error and what is causing the error?

We messed up in the ERM workbench when we ENabled the watchdog timer, but DISabled petting it, by default. We forgot that runtime edits will cause the ERM watchdog to fire just about EVERY time and cause an error. You can change that in your ERM config and in the "default " config for any future ERM configuration (see View->Options). In the Options dialog, the Slave Defaults section, set the Pet Frequency equal to half the Watchdog value.

Also, make sure your watchdog timer value is at least twice your typical scan time, but at least 250 ms (it doesn't help too much to make it fast - it just causes more errors). Do you have LONG PLC scan times? Then this may causing the problem???

You reset the slave by disabling it, then reenabling it as simpsonjcat pointed to page 4-16 of the ERM manual. You must have the right Y address based off your ERM configuration. These "disable bits " take up the first 16 bits of the "discrete output " map. The ERM must recognize the Y value to be ON, then turn it OFF. This may take multiple PLC scans, hence the need to monitor X330 (in the manual's example) to know when it is "done " disabling a slave.

Make sure YOUR Y address and YOUR X address are the right ones in your "reset slave " logic

Created Date: March 22,2006

Created by: rex2802

The error (slave not responding) can be caused by unplugging the EBC or when the rack is powered down and then back on.

If the slave Watchdog timeout is Disabled the following occurs. I unplug the ethernet cable, X303 goes ON. When I reconnect the Ethernet cable the X303 goes OFF. If the Watchdog timer is Enabled, 250 MS, and ERM Pet Frequency is 125 ms, replugging in the Ethernet cable will NOT reset X303.

My scan times during this test was 21 ms, max = 24. During machine operation 60-80 ms are typical.

I can disable the EBC by forcing Y303 OFF. The modules Error light goes on. Turning Y303 OFF clears the error light.

All 4 of my slaves will show their repective faults (X300-X303) if powered down and then up. ERM Workbench reports "slave not responding " yet the activity light on the EBC will show activity, and the inputs will reflect the true input status and I can energize outputs. But the fault bit will be on. At this point I think there is an hardware issue here with being able to disable and re-enable the EBC to clear reset the fault bit.

Adjusting,enabling,disabling watchdog timers and pet frequency haven't helped resolve this issue.

I may have to remove the logic that signals the operator that a rack is faulted at this point since I haven't been able to resolve this issue.