News:

  • November 16, 2026, 07:16:40 PM

Login with username, password and session length

Author Topic: BRX PLC BX-DM1E-10ER3-D Lock up  (Read 67 times)

icreateproblems

  • Newbie
  • *
  • Posts: 1
BRX PLC BX-DM1E-10ER3-D Lock up
« on: November 15, 2026, 07:55:10 PM »
I have multiple BRX PLC on site locking up either half locking up, reading some data and transferring some. Other times completely locking up transferring / reading now data at all. We pretty much purely use the plcs for modbus data via ethernet. the only way we are fixing the lock ups are by power cycling, cant access the plc via ethernet directly either until power cycled. We seem to be getting the driver error - st143 error pops up, but hard to tell exactly if this is coming from the power cycle or before it. do more 2.11.0 and os 2.11.2. any work arounds here guys. has been going on for a while and need a better solution then just "power cycle".  8)

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6180
  • Yes Pinky, Do-more will control the world!
Re: BRX PLC BX-DM1E-10ER3-D Lock up
« Reply #1 on: Today at 10:59:39 AM »
I have multiple BRX PLC on site locking up either half locking up, reading some data and transferring some. Other times completely locking up transferring / reading now data at all. We pretty much purely use the plcs for modbus data via ethernet. the only way we are fixing the lock ups are by power cycling, cant access the plc via ethernet directly either until power cycled. We seem to be getting the driver error - st143 error pops up, but hard to tell exactly if this is coming from the power cycle or before it. do more 2.11.0 and os 2.11.2. any work arounds here guys. has been going on for a while and need a better solution then just "power cycle".  8)

Gonna need more info.
1. When you say "locking up", do you mean the PLC continues to run but the Modbus stops working?
2. ST143 suggests that you are using MRX/MWX, but can you confirm which side of the Modbus conversion stops working? Is it master comms (MRX/MWX) or slave comms (the PLC's Modbus server is responding to external requests)?
3. How often does this happen? Does it require a long run (many weeks) or is it more random?

ST143 is a generic error that says a driver based error failed. It's usually just a timeout. The "Last Error(s)" section should give you a text description of the errors you are getting.
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO