Host Engineering Forum
 
*
Welcome, Guest. Please login or register.
Did you miss your activation email?
February 17, 2018, 06:16:19 pm


Login with username, password and session length


Pages: [1] 2 3 ... 10
 1 
 on: Today at 01:53:02 pm 
Started by davidbgtx - Last post by davidbgtx
I'll stick with the plan of call ADC for replacement and them forwarding the unit to HOST

BRX has been pretty good for a new product, but every new product will have some issues. Host's policy is to aggressively pursue issues with new(er) products and to quickly make changes to the design or manufacturing process. We take it seriously.

And that's one of the reasons I stick with your products. Good Job

 2 
 on: Today at 12:45:04 pm 
Started by davidbgtx - Last post by BobO
I'll stick with the plan of call ADC for replacement and them forwarding the unit to HOST

BRX has been pretty good for a new product, but every new product will have some issues. Host's policy is to aggressively pursue issues with new(er) products and to quickly make changes to the design or manufacturing process. We take it seriously.

 3 
 on: Today at 12:24:02 pm 
Started by davidbgtx - Last post by davidbgtx
No, but I will try try powering up with devices disconnected and see what happens. What did you do to resolve your issue?

His HMI was busted.

I'll stick with the plan of call ADC for replacement and them forwarding the unit to HOST

 4 
 on: Today at 12:09:16 pm 
Started by davidbgtx - Last post by BobO
No, but I will try try powering up with devices disconnected and see what happens. What did you do to resolve your issue?

His HMI was busted.

 5 
 on: Today at 12:00:50 pm 
Started by davidbgtx - Last post by davidbgtx
No, but I will try try powering up with devices disconnected and see what happens. What did you do to resolve your issue?

 6 
 on: Today at 11:49:58 am 
Started by davidbgtx - Last post by ATU
I had a problem where I believe my device was not sending string lengths correctly causing a watchdog timeout in the BRX. Could the devices be trying to communicate before the BRX is ready?  Have you tried powering it up with devices disconnected?

 7 
 on: Today at 11:03:25 am 
Started by davidbgtx - Last post by davidbgtx
yes, through a Stride unmanaged switch, to 2 GS4 Durapulse drives and 1 CMore HMI, and eventually to a WINPLC (which it will communicate with). All comms are working once it boots up correctly.

 8 
 on: Today at 10:21:22 am 
Started by davidbgtx - Last post by ATU
Do you have any Ethernet Devices connected?  HMI?

 9 
 on: February 16, 2018, 12:01:41 pm 
Started by davidbgtx - Last post by BobO
It seems odd that I had this issue with a DM1E, is there a common denominator? However I have 7 or 8 DM1E,s and 1 other BRX with no issues yet.

The issue with the H2s was due to a manufacturing change by a chip supplier that resulted in behavioral changes with the part. I think we use the same part on BRX, so I guess it is theoretically possible, but the failure was very specific to the way we stage power supply startup in 205, and we have not seen the same issue in either Terminator or BRX.

 10 
 on: February 16, 2018, 11:32:26 am 
Started by davidbgtx - Last post by davidbgtx
You can go through returns at ADC.  Be sure to put "Attn: BRX Product Engineer, please deliver ASAP" on the label and I will get it to HOST as soon as I receive it.
OK, I'm at home now, will contact ADC Monday morning 1st thing.

Pages: [1] 2 3 ... 10
Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines

Valid XHTML 1.0! Valid CSS! Dilber MC Theme by HarzeM