We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According the TypeScript definitions, IServiceVector::getMultipleHoldingRegisters() support returning Promise<number[]>.
IServiceVector::getMultipleHoldingRegisters()
Promise<number[]>
However, when this is used, the return length check in servertcp_handler.js::300 will always fail. The corresponding code part is:
servertcp_handler.js::300
const values = vector.getMultipleHoldingRegisters(address, length, unitID); if (values.length === length) {
As values is Promise{[...]} its length check fails and this results in a Modbus exception sent to client instead of the provided read result.
values
Promise{[...]}
When getMultipleHoldingRegisters() returns number[] directly, without a Promise, everything works as expected.
getMultipleHoldingRegisters()
number[]
The text was updated successfully, but these errors were encountered:
No branches or pull requests
According the TypeScript definitions,
IServiceVector::getMultipleHoldingRegisters()
support returningPromise<number[]>
.However, when this is used, the return length check in
servertcp_handler.js::300
will always fail. The corresponding code part is:As
values
isPromise{[...]}
its length check fails and this results in a Modbus exception sent to client instead of the provided read result.When
getMultipleHoldingRegisters()
returnsnumber[]
directly, without a Promise, everything works as expected.The text was updated successfully, but these errors were encountered: