-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Register 0 not accepted. #33
Comments
aldas
added a commit
that referenced
this issue
Jul 11, 2019
…dress incorrectly when value is 0. also fixes case when addresses overlap then quantity was calculated incorrectly
aldas
added a commit
that referenced
this issue
Jul 11, 2019
…dress incorrectly when value is 0. also fixes case when addresses overlap then quantity was calculated incorrectly
aldas
added a commit
that referenced
this issue
Jul 11, 2019
1. it calculates start address incorrectly when value is 0. 2. also fixes case when addresses overlap then quantity was calculated incorrectly
aldas
added a commit
that referenced
this issue
Jul 11, 2019
1. it calculates start address incorrectly when value is 0. 2. also fixes case when addresses overlap then quantity was calculated incorrectly
Hi! thanks reporting the problem. your described problem is in method where addresses are splitted into separate requests. 4157cab#diff-f5ead4071f50c5dfafce5c6459c3ac7dR50 I have made a bug fix. could you checkout master/latest changes see if it helps. |
It works! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This could be related to #28.
I am reading a Janitza UMG604.
It provides a register 0 but I cannot read it (I can request any register > 0):
The error is
Address out of bounds
and comes fromReadHoldingRegistersResponse.php
, line 180:The error happens if we read more than 1 register and the first starts at 0.
These are some variables in
getQuadWordAt
(getDoubleWordAt
for examples 5 and 6, becausegetQuadWordAt
is not called) according to my tests.It looks like
$byteCount
is wrong but I couldn't find the issue:The text was updated successfully, but these errors were encountered: