modbus_master 2.1.4
modbus_master: ^2.1.4 copied to clipboard
An easy to use package using which a dart program can work as a Modbus/TCP master device.
1.0.0 #
- Initial version.
2.0.0 #
- Simplified read and write method:- Now only two methods are provided for reading and writing (i.e. read and write) as opposed to 6 methods previously.
- Intuitive method names for object creation. "start" method creates object & initializes all resouces. "stop" method shuts down all resources & disconnects all TCP connections.
- Asynchronous
isStoppedAsync
method to check whether object is stopped. - Bug fixes.
2.0.1 #
- Updated README.md file
- Provided docstrings
- updated modbus_slave.py file
2.1.0 #
- Updated README.md file
- Added two more fields
isReadResponse
andisWriteResponse
in classSlaveResponseConnectionError
as well as classSlaveResponseTimeoutError
2.1.1 #
- Bug fixes:- In case of Error Response, field
isReadResponse
/isWriteResponse
istrue
andreadValue
/writeValue
is null of object of classSlaveResponseDataReceived
is true.
2.1.2 #
- Bug fixes:-
- Inside Worker Isolate :- When
UserRequestShutdown
is received in worker isolate, then all sockets are now closed usingawait socket.close()
instead ofsocket.destroy()
. - Inside Main Isolate:- When
SlaveResponseShutdownComplete
is received in main isolate, then receive port of main isolate is also closed.
- Inside Worker Isolate :- When
2.1.3 #
- Bug fixes :-
socket.destroy()
is not used- In worker isolate,
await socket.close()
is used instead ofsocket.destroy()
. - This is done because in few scenarios in case of hard socket closing from server side, network isolate was getting killed.
- In worker isolate,
- Extra getter
maximumNumberOfTCPConnectionsAllowed
provided for object of classModbusMaster
. This is done so that users explicity know about maximum how many concurrent TCP connections can be made. - Refactoring changes
2.1.4 #
- Message framing was done for message received from socket
- When multiple Modbus ADU was received from socket as single Uint8List, then those messages were getting dropped, as multiple ADU together were more than length as per 1st ADU
- Created method
splitMessageFromSocketIntoMultipleModbusADU
to split message incoming into multiple ADU.