Thanks Łukasz, I’ll take a look at the stack configurator, might take some time to understand it.
I’m assuming that would result in having it all under the same maven module. Niclas, For floating point and large integers, this is already supported, where we serialized/parse multiple modbus registers to the different data types. You should be able to use something like 40001:REAL as the Address field. On Mon, Aug 16, 2021 at 7:49 AM Niclas Hedhman <nic...@hedhman.org> wrote: > On 2021-08-15 22:40, Łukasz Dywicki wrote: > > Then each driver flavor of modbus (rtu, ascii, tcp) would simply need > > to > > wrap and unwrap structures coming from an transport. > > I have come across a lot of Modbus over the years, but I can't recall > seeing the ascii variant since the 1980s or early 1990s. IIUIC, it was > mostly used for hand terminals, and not to connect to computers. > So I wouldn't spend time on that, unless nothing else is around. > > I haven't checked the mspec in details, but I suspect it is close to > formal specification. But I would like to bring attention to that a fair > amount of equipment has extensions that are not in the specification > (well, at least last time I read it about 20 years ago), namely floating > point numbers and 32/64-bit integers. It would be neat to support > that... > > Unfortunately, I don't have cycles to help out with it. > > Cheers > Niclas >
