Hi Tomas,

Thank you for your help. I understand how it works now, what you provided is where i wasn't sure what to do. It makes sense to me now.

Cheers

Mike

Hi Jaroslav,

That explains why i could not find it. I will look into a TCP version or another PLC with more serial ports.

Thanks,
Richard

PS
I now have a slightly used 750-652 for sale 😉

Hi Jaroslav,

I will email you the documentation for the device.

Cheers

Mike

Hi Richard,
there are various "simplifications", using various offsets to distinguish between the four tables of data. For Holding registers, the most typical is offset of 40000, but as you already noticed, this is no standard.

Best regards,
Jaroslav

Thank you Jaroslav, you learn something every day! That will help more than you know with all of my projects. especially ones with process models 🙂

Cheers

Mike

Hello,
thanks for sharing your experience and findings. There's nothing to add, only that from the nearest release the REXYGEN compiler will issue a warning when two drivers use the same configuration .rio file.

Jaroslav

@reitinge Thank you very much! That is what I am doing right now 🙂 It works good enough.

@apollo I understand. Just keep in mind that the Passive feature is available both at Modbus RTU and Modbus TCP.

Kind Regards,
Tomas

@mikeyh Hi Mike,

thanks for update. Could you please try to test one Raspberry Pi with certain SD card (i.e. OS) and check with working Monarco HAT and then switch the one failing so we can say it is Monarco HAT failure afterwards?

Thanks for cooperation.

Kind Regards,
Tomas

@rexpeter
Hi Peter,
no problem. I'm glad, it's works.

Cheers,
Jan

Hi Mike,

I recommend checking out the examples in the 0401_Modbus_RTU folder or take a look at the 0121-10_Monarco_HAT_Modbus_RTU_ADAM-4024 and 0121-11_Monarco_HAT_Modbus_RTU_Loopback_USB examples. These are all provided in REXLANG. Hopefully, these examples will provide some assistance.

Cheers,
Jan

@MikeyH Hi Mike,

This error is related to the timing issue of the Modbus Driver. It means that the Modbus Driver exceeded the allotted time 800x from the executive start for some reason. In your case, I would inspect the timing of the whole project and also the diagnostics of tasks related to the Modbus driver.

Without knowledge of your project, communication frame and timing, I'm not able to provide more details.

Cheers, Tomas