Hey, yes, its in the module scraper or plc-scraper. Its easily configurable by yaml, json or programmatically.
Julian Am 25.06.20, 10:30 schrieb "Niclas Hedhman" <nic...@hedhman.org>: Thanks.... Another question; is there any "loop" system that just continuously reads until I tell it to stop? On Thu, Jun 25, 2020, 15:16 Julian Feinauer <j.feina...@pragmaticminds.de> wrote: > Hi Nic, > > I have to dig in a bit later to give you good answers but AFAIR the > connection can be left open and configuration should be as you wrote it. > I also did some tests with it but that was some months ago... > > Hope to have some more information later. > > Julian > > Am 25.06.20, 05:58 schrieb "Niclas Hedhman" <nic...@hedhman.org>: > > Hi, > IIUIC, the connection string for Serial Modbus would be something like; > > modbus:serial:/dev/ttyS0?unit-identifier=7 > > assuming I want to communicate with device with address 7. > > That would mean that I have one connection per device I talk to over a > single serial port. Is that correct? (Personally, I would not made the > device part of the connection abstraction, but realize that it is a bit > late for that) > > Are there any issues here, regarding which connection has access to the > port, or do I need to open and close the connection on each set of > messages? > > Couldn't find info about this in the documentation. > > > The serial port page is missing information on the configuration (data, > parity, stop,...). The source code doesn't have the > @ConfigurationParameter > annotations, so will they still work or do I need to add that > programmatically somehow? > > > Cheers > Niclas > >