News:

  • June 28, 2026, 10:52:45 AM

Login with username, password and session length

Author Topic: Error connecting to BRX via Ethernet  (Read 8970 times)

MarkTTU

  • Hero Member
  • *****
  • Posts: 293
    • SamJackson.com
Error connecting to BRX via Ethernet
« on: August 08, 2024, 09:09:48 PM »
Trying to connect to a BRX today and I'm getting Comm error connecting to PLC. When I look at the detailed error list for the comm link I see:

Task code error response    Code = 2: Out of session handles

What in the world does that mean? Besides the obvious that the CPU couldn't handle another session... but what could have it so busy it can't allow the programming software to connect?

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6164
  • Yes Pinky, Do-more will control the world!
Re: Error connecting to BRX via Ethernet
« Reply #1 on: August 08, 2024, 09:38:37 PM »
Trying to connect to a BRX today and I'm getting Comm error connecting to PLC. When I look at the detailed error list for the comm link I see:

Task code error response    Code = 2: Out of session handles

What in the world does that mean? Besides the obvious that the CPU couldn't handle another session... but what could have it so busy it can't allow the programming software to connect?

When a client (DmD, HMI, RX/WX) logs into a Do-more PLC, a session is allocated and the client is given a handle. Do-more PLCs can support up to 32 sessions. Sessions time out after 30 seconds of inactivity.

Not sure what would be causing issues, but I don't know of any similar reports.
"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

MarkTTU

  • Hero Member
  • *****
  • Posts: 293
    • SamJackson.com
Re: Error connecting to BRX via Ethernet
« Reply #2 on: August 08, 2024, 09:43:18 PM »
Trying to connect to a BRX today and I'm getting Comm error connecting to PLC. When I look at the detailed error list for the comm link I see:

Task code error response    Code = 2: Out of session handles

What in the world does that mean? Besides the obvious that the CPU couldn't handle another session... but what could have it so busy it can't allow the programming software to connect?

When a client (DmD, HMI, RX/WX) logs into a Do-more PLC, a session is allocated and the client is given a handle. Do-more PLCs can support up to 32 sessions. Sessions time out after 30 seconds of inactivity.

Not sure what would be causing issues, but I don't know of any similar reports.

I might know the issue. Working a program where another device initiates a connection to my BRX, but I haven't actually written the bit of code to listen for the connection yet. Could be that other device is flooding the BRX trying to get connected.

Will have to check tomorrow, left the site and only have VPN access now.

Thanks Bob!

MarkTTU

  • Hero Member
  • *****
  • Posts: 293
    • SamJackson.com
Re: Error connecting to BRX via Ethernet
« Reply #3 on: August 09, 2024, 10:59:06 AM »
Trying to connect to a BRX today and I'm getting Comm error connecting to PLC. When I look at the detailed error list for the comm link I see:

Task code error response    Code = 2: Out of session handles

What in the world does that mean? Besides the obvious that the CPU couldn't handle another session... but what could have it so busy it can't allow the programming software to connect?

When a client (DmD, HMI, RX/WX) logs into a Do-more PLC, a session is allocated and the client is given a handle. Do-more PLCs can support up to 32 sessions. Sessions time out after 30 seconds of inactivity.

Not sure what would be causing issues, but I don't know of any similar reports.

I might know the issue. Working a program where another device initiates a connection to my BRX, but I haven't actually written the bit of code to listen for the connection yet. Could be that other device is flooding the BRX trying to get connected.

Will have to check tomorrow, left the site and only have VPN access now.

Thanks Bob!

Looks like the culprit wasn't what I thought it was and was actually the two CM5-RHMI touch screens. Not sure why they hosed the PLC comms, but I'll try to dig into it more later.