Modbus issues after the latest update 3.11.0

Technical Questions
1

Software version: 3.11.0
Robot generation: CB31UR5

Steps to reproduce:

  1. First step: Load program with used Modbus I/Os
  2. Second step: start the program

Expected behavior: just start the program

Actual behavior: multiple Exceptions thrown …“Softwarefehler!”
Exception Caught in Thread AWT-EventQueue-0
Trackinginformation.java:54
.
.
In the logfile -> PolyScope: C0A0
.
.
I/O Screen (PolyScope)
MODBUS-Einheit: 192.168.0.8
“Keine Zahl”! <- MODBUS_1 [8000]

Hi,
After the update (UR5) to 3.11.0, there were problems with “old” programs using Modbus I / O. After the start of these programs there are several error messages “Software error!” with NullPointerExceptions. After closing the messages, the program and the Modbus communication are running smoothly.

20191001_135420
20191001_1354202268×4032 3.72 MB

in the logfile an error message with the code C0A0 is generated.

20191001_135435
20191001_1354352268×4032 3.8 MB

If we update the Modbus on the Installation tab before starting the program, these error messages will not be displayed.
(Or less of them)

The I / O tab displays an error message on the Modbus screen. “Not a Number” appears on the Modbus units instead of an integer value (word).

20191001_134808
20191001_1348082268×4032 3.83 MB

is this a bug or have we done anything wrong with the update?

Ronny

P.S.
the logfile says :
3.5 :: 0068d21h26m20.735s :: 2019-09-30 13:59:34.647 :: -5 :: C0A0:0 :: null :: 2 :: :: java.lang.NullPointerException :: null
3.5 :: 0068d21h26m20.735s :: 2019-09-30 13:59:34.647 :: -5 :: C0A0:0 :: null :: 2 :: :: java.lang.NullPointerException :: null

2

We have found this bug internally as well.
It will be fixed in 3.12.0.

1 Like
3

Okay thanks for the info :+1:

4

Is there any chance to predict a date for the 3.12 release? We’re having the same issues.

Good to know that it’s a bug!

Thanks so far.

5

3.12.0 is expected around end of year.

6

I’m having very inconsistent results access the modbus server of the UR. Is this related?

Node Red connects, but any attempt to read registers comes back with “Port not open” but nmap shows it is.

Simply Modbus can’t read registers but modscan64 can.

Should I downgrade?