Lookout 6.5 critical crash - writes to random modbus addresses

[rob_v]

Anybody? 2 days of silence

We did series of tests, but we are for sure; the modbus.cbx has a bug.

What's next?

[Ryan.S]

I'm looking at the dump, and trying to reproduce the crash.

What else should I do after I make two ethernet connections? Do I need to operate some pots?

[T W]

Nothing really special needs to be done - I always do acknowledge all alarms after startup; open the "Properties" window and click around on the main screen a bit; and I've also

encountered it a few times while clicking around in the "Reference" screen.

But even when leaving it alone I've encountered it a few times.

We do have more active modbus connections in our testing (5) and live setup (15).

If you'd like an address list of the devices we are using or specific info; you have my e-mail address from the readme in the first zip. If it helps or speeds things up I could also give you a phone number or arrange a VPN connection so you can talk to some of the devices we use directly.

[Ryan.S]

From the txt log file and the wireshark log file, it looks like the crash usually happens after the "random write" which is function code 16. I'm looking at the "random write" because I want to know if it's really "random".

It's not sure if the "random write" is the reason of crash. But I'm thinking maybe you can try not to use the function code 16. It is set in the Modbus's properties->Advanced. Could you test it again with the function code 16 disabled? If it still crashes, it has nothing to do with the function 16. But if it becomes good, we can focus on this specific function.

I will also try to figure out the "random write". Based on your process's design, do you think this kind of write as an unexpected behaviour?

I also sent this message by email to you.