Function Recommanded: AddressTagOrganizer for PlcXXXRequest.Builder

[parallelbgls]

Sometimes, server implements in a non standard protocol and will need some specific ways for client to communicate.

One Example for modbus.
Client required 400100 to 400214. But server implements with a non standard way.
They offered a document said that client need to send 3 packs to read those datas.
400100-400149 400150-400199 400200-400249
Any other read request will be rejected with no response.

Another example is more common in real.
Server set 6 bit datas in 400074.1 - 400074.6
and 400074.7-400074.16 has no space.
That means if client read any data 400074.7-400074.16 or 400074, server will return ILLEGAL_DATA_ACCESS.

One recommanded solution is to add a class called AddressTagOrganizer for PlcXXXRequest.Builder for those Requests having data reading ability.
Default value of organizer is null for default.

There are 4 methods in organizer

1. Include -- include addresses explicitly, any tag address covered by include will not been used in auto packet.
2. Exclude -- exclude addresses explicitly, auto packet will never pack those tag addresses.
3. MaxPacketLength -- explicitly set max packet length for specific request and response.
4. MaxCoveragable -- explicitly set percentage of data that will be readed but never been used.

builder.organizer = new AddressTagOrganizer();
builder.organizer.include("400100:UINT[50]").include("400150:UINT[50]").include("400200:UINT[50]").exclude("400074.7:BOOL[10]").maxPacketLength(100).maxCoveragable(34.44);