S7-1200 modbus tcp communication with Victron CERBO GX

Question

question

petrnovotny75 asked Mar 29, '23

S7-1200 modbus tcp communication with Victron CERBO GX

Ahoj všichni,

mám problém s komunikacemi modbus tcp s jednotkou cerbo gx.

V dostupných službách CERBO GX jsem vybral ID100.

Podle dokumnetace jsem nejjednodušší dotaz na protékající proud měniče, tj. ID:100, MB_MODE = 0 /čtení dat/, MB_DATA_ADDR: 808, DATA_LEN: 1.

Bohužel se mi vrátí chyba 16#8384 - Chyba v datové hodnotě pro funkci 5 ???

V případě, že použiji Simply Modbus TCP Client 8.1.2 pak mě CERBO GX bezproblému odpoví.

Proč Cerbo vrací cybu ID255, když je dotazována jednotka ID100 ??

Nenapadá Vás, kde může být chyba ??

Viz. obrázky.

Moc děkuji za případné odpovědi. Petr

Modbus TCP

mb-client.png (23.0 KiB)

cerbo-gx-error.jpg (37.5 KiB)

cerbo-gx-modbus-tcp-services.jpg (34.1 KiB)

sw-client.png (64.3 KiB)

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

virginio answered · Jul 21, 2023 at 02:58 PM

rd-osek,

Ahoj, taky mám stejný problém, jak jsi to vyřešil?

Díky za pomoc...

Hi, I have the same problem, how did you solve it?

Thanks for help...

1

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

rd-osek commented · Jul 24, 2023 at 09:34 PM

Hi virginio,

solution is almostly easy than it looks like.

You need to go to the DB of your MB_CLIENT block. In my case it is an DB216.

I have got it at the system blocks - program resources:

You have to change at the DB row MB_Unit_ID -> this specifies the slave ID. That is important for the Victron communication with the Cerbo unit or other accessories. Slave ID needs to be typed in according to the Victron manual or at the (my case) Cerbo GX unit (MB TCP services menu). Byte 16#64 is in DEC format 100 -> communication for the main values of the Cerbo GX.

Be also careful of the Connect parameters. Connection ID must be unique. If you have got more MB communications set, you have to adjust it also to be working. My opinion is to restart PLC when you are changing this parameter. Sometimes it already saw, that parameter "freezes" at the memory.

Let me know if you will have any more asks and your try won't still be working. :-)

Best regards

Honza

1 ·

1690233449731.png (80.5 KiB)

1690233656336.png (467.9 KiB)

1690233890668.png (31.1 KiB)

1690234394106.png (229.2 KiB)

Modifications Space

Node Red Space

Answer 1 · 2023-07-09T22:54:36Z

rd-osek answered · Jul 09, 2023 at 10:54 PM

Ahoj,

dořešil jsi svůj problém s komunikací Victron/PLC?

Řešil jsem stejný problém, narazil na tvůj dotaz, a po pár hodinách tápání v TIA Portalu našel funkční řešení.

Ahoj,

Honza

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Answer 2 · 2024-03-06T08:16:55Z

sventheschu answered · Mar 06 at 08:16 AM

Hello together,

finally the Modbus connection works with the tip from rd-osek.

But how do I know the register, when I look in the Manual of Cerbos, there is no register like 40841? I need the total production, the actual production, the total consumption and the actual consumption.

Best regards

Sven

1

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

rd-osek commented · Mar 08 at 10:56 PM

Hi @SvenTheSchu,

register 40841 is existing under the Cerbo GX, but it is interpreted like a 841 in the table:

CCGX-Modbus-TCP-register-list-2.90.xlsx

So you need to read modbus holding register (4x) --> 40841.

Try to search you requested values in the table attached.

For total E produced it should be: 44204 (com.victronenergy.dcsource/Total energy produced)

For ac. consumption AC: L1 reg. 40817, L2 reg. 40818, L3 reg. 40819

it's hard to find the right registers, sometimes, but it works.

rd-osek

0 ·

ccgx-modbus-tcp-register-list-290.xlsx (61.4 KiB)

question