Hello, I have trouble reading several Modbus TCP "register groups".

Hardware: 1214C
TIA: V16

Transmitter: E+H CM44R
CM44R

Here is the Modbus guideline, which can be found under "Downloads > Manuals and Datasheets > Special Documentation (SD)":
SD01189CEN_07.22.pdf

Overview

I want to read out various registers. This works so far; however, I have created a separate FC for each "register group."
The tricky part now is reading out all the existing "register groups" together.

My Plan

My idea was to create an FB that contains an MB client block. Variables like MB_Mode, address, length, and storage location are passed via variables.
Under the MB block, I would simply use a switch-case statement. In each case, I would assign different values to the MB_Mode, address, length, and storage location variables (MB_DATA_PTR). The loop variable for the switch case would increment by one each time the status is DONE.

The Problem

The problem with this approach is that the data I already receive is directly stored in various DBs, and some are even converted into UDTs. For example, data in a float is automatically converted into a real. At first, I thought this was great, but now I see the problem: I can't change the storage location variable because it uses different data types, such as from an array of Word [0...X] to an array of [UDT name(0...X)].

Possible Solution?

I have come across pointers, but I don't fully understand them, so I would prefer a different approach:
Instead of converting the data into UDTs or other data types, I plan to leave the data in Word format and then adjust the length dynamically using a variable array. Once I have all the data, I can transfer it to my predefined UDTs using a MOVEBLK.

This does not work, because for the MOVEBLK the source needs to have the same datatype like the target. Not the case when moving from Array of Word to Array of (UDT name).

Below is a list of all the registers to be read and their corresponding page numbers in the Modbus guideline (SD01189CEN_07.22.pdf).

Registers:

1. Measured Values
   • Register: 0 - 31
   • Total Size: 48 bytes
   • Type: Holding/Input, FC: 03, 16, 23, 04 (Use mode 0 and adress 40001)
   • Page: 46
2. Device Status
   • Register: 503
   • Total Size:1 byte
   • Type: Input, FC04
   • Page: 48
3. Serial number Sensor 1 & Sensor 2
   • Register: 770 & 786
   • Total Size: 64 bytes
   • Type: Input, FC04
   • Page: 50
4. Sensor Diagnostics
   • Register: 1095 & 2095
   • Total Size: 4 bytes
   • Type: Input, FC04
   • Page: 28-29
5. Heartbeat Data Sensor 1
   • Register: 10016 - 10051
   • Total Size: 72 bytes
   • Type: Input, FC04
   • Page: 85
6. Heartbeat Data Sensor 2
   • Register: 10216 - 10251
   • Total Size: 72 bytes
   • Type: Input, FC04
   • Page: 85

Reading Register 0 - 10251 in one go? 125 Words the limit?!

Looking forward to your feedback, suggestions, and ideas.

Thanks

~Daniel

Hello,

first important thinjg:

The tricky part now is reading out all the existing "register groups" together.

Hope yo understand that you can do only one job at the time (one read or one write) not all or multiple jobs at the time.