After changing yesterday to V0.15 I had to adjust my code using the DataBlockDataItem constructor and adding the arguments to this:
signalDataItem = new DataBlockDataItem<Boolean>(dataBlockNumber, byteAddress, bitAddress);
Because there is a constructor like
public DataBlockDataItem(BigEndianShort dbNumber, int startByte, int length = 1) : this(dbNumber, startByte, 0, length)
it used this one instead of the one I intended to use:
public DataBlockDataItem(BigEndianShort dbNumber, int startByte, int bit, int length = 1)
If I the make an item with bit address '0' if have got an ArgumentOutOfRangeException of Length is 0
To use the correct constructor I now add the parameter names like this:
signalDataItem = new DataBlockDataItem<Boolean>(dbNumber: dataBlockNumber, startByte: byteAddress, bit: bitAddress);
and it is fine.
I don't know if there is some better way of making the constructor for an boolean so that it can not use by mistake the constructor without the bit address.
After changing yesterday to V0.15 I had to adjust my code using the DataBlockDataItem constructor and adding the arguments to this:
Because there is a constructor like
it used this one instead of the one I intended to use:
If I the make an item with bit address '0' if have got an ArgumentOutOfRangeException of Length is 0
To use the correct constructor I now add the parameter names like this:
and it is fine.
I don't know if there is some better way of making the constructor for an boolean so that it can not use by mistake the constructor without the bit address.