Replies: 1 comment
-
Help is always welcome.
The idea is that you only define the registers you need for your device, SimCore then handles marking the rest as invalid.
yes.
you define the registers normally, and then use offset in SimDevice to set the start address for a block.
Not needed! and it would complicate matter since it would make it possible to mix shared and non-shared registers.
That principle makes it clear that a device is either shared or non shared. Please do not forget that nowadays it is pretty rare to see a nom-shared device. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
I know those classes are not yet for production, I just want to test them as a beta tester, but first I would like to understand some points. I could help to develop it as well.
If my help is not needed, please don't hesitate to tell me: I can understand.
SimDevice
In the docstring, it is made mention of a
block:If I understand it correctly, a block is a list of contiguous registers defined as a list of SimData's.
Must those SimData's be in contiguous registers or are non-defined registers allowed?
Here the registers 1-6 are not defined, I guess this is allowed and the SimDevice will return the
defaultvalue if a non defined register is read request. Am I right?SimDevice with non-shared registers
I the non-shared mode, there are 4 blocks of registers: coils, discrete inputs, holding registers, input registers. Every block can have registers with address 0-65535. How to declare such a device?
And then? How should be
offset_addressdefined?Maybe, SimData should have an optional
block_typeorregister_typeparameter?With
And the principle of offset_address should be forgotten?
Beta Was this translation helpful? Give feedback.
All reactions