I use node-red-contrib-s7 to communicate one S7-1214C PLC .But I write wrong address length at DB6001,S1556.30 and there show error message in node-red .
OK , there two questions .
First :
I also write wrong address like DB6001,S1466.100 and the right address is DB6001,S1466.30.But NODE-RED not show error message.
Second question:
AND NODE-RED show error message address is DB6001,R1536 .But this address is valid.
Hope this help U like me do this communication !
Can you check the absolute offset using cross-reference? I see that the struct where the number is is not the first one in the list, and it may have a different offset than the one you can see in the list.
As you can see in the previous picture, the offset listed next to the variable is relative to the struct, not the absolute offset in the DB. But if you check in cross-reference (or properties) you can get the absolute offset value for the DB.
It could be that the variable where you don't get an error has actually the right offset, and the one you think is right but don't get an error is actually wrong.
1 Like
Yes,I shortcut offset address is absolute address in DB data, and I have right data from node-red to PLC . I want upload picture but network not good .
Thanks for your advice.
I think what it has to do is that, s7 node sets translation of all tags of your connection, meaning if one of tags is unavailable whole batch of variables is regarded as bad and that's why you get an error.
If your defined variables are in range of your DB you can point to any memory area and will get some kind of result, but it might look like gibberish. No error in this case
Your variables definitions allow received buffer of values to be parsed in correct format.
1 Like
Good.
You give me the right answer.
Thank U very much!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
