Host Engineering Forum

General Category => EBCs and EBC100s => Topic started by: alectek on January 15, 2019, 02:27:40 PM

Title: When EBC100 slave lost communication to the master, will the output turn off?
Post by: alectek on January 15, 2019, 02:27:40 PM
Will the output on the slave rack turn off or keep the last status? Or it is settable?

Will the master keep looking for the slave (the master set to keep running when slave error), and get back to normal if the slave is online again, or the master gets st154 error, then ignore the slave forever?


Thanks!
Title: Re: When EBC100 slave lost communication to the master, will the output turn off?
Post by: BobO on January 15, 2019, 04:54:55 PM
Will the output on the slave rack turn off or keep the last status? Or it is settable?

Can be either. Configurable by slave.

Will the master keep looking for the slave (the master set to keep running when slave error), and get back to normal if the slave is online again, or the master gets st154 error, then ignore the slave forever?

It will log it back in.
Title: Re: When EBC100 slave lost communication to the master, will the output turn off?
Post by: alectek on January 15, 2019, 06:13:39 PM
Thank you Bob.

I open the slave only see input be optional either be held or cleared on slave error; but I don't see the output. Could you make it clear?
Title: Re: When EBC100 slave lost communication to the master, will the output turn off?
Post by: BobO on January 16, 2019, 12:35:26 AM
Thank you Bob.

I open the slave only see input be optional either be held or cleared on slave error; but I don't see the output. Could you make it clear?

Does it say inputs only? Sorry...I misremembered then. Outputs will go off.
Title: Re: When EBC100 slave lost communication to the master, will the output turn off?
Post by: alectek on January 17, 2019, 10:30:53 AM
Got it, thank you.
Title: Re: When EBC100 slave lost communication to the master, will the output turn off?
Post by: BobO on January 17, 2019, 10:46:00 AM
During development, we often discuss doing things several different ways. While I knew the final answer at the point it was developed, seems like 5 years later I am as likely to remember the wrong one of three implementations as I am the right one. ::)