Re: AW: Modbus RTU

2021-08-18 Thread Łukasz Dywicki
Hey Stephen, It really depends how you copied the repository. Have a look on output of "git remote -v" command. For me its: connectorio g...@github.com:ConnectorIO/plc4x.git (fetch) connectorio g...@github.com:ConnectorIO/plc4x.git (push) origin g...@github.com:apache/plc4x.git (fetch)

Re: AW: Modbus RTU

2021-08-18 Thread Stephen Snow
Hi Ben, I forked the repo, actually had it forked for snapshot 0.7.0 so just had to merge the commits from the repo. On Wed, 2021-08-18 at 07:12 +1000, Ben Hutcheson wrote: > Hi Stephen, > > I have pushed support for RTU to the branch feature/modbusrtu, it > seems to > work. I've only used RTU

Re: AW: Modbus RTU

2021-08-17 Thread Stephen Snow
Thanks Ben, I'll get set up and fork the branch you noted. I'm sure I'll need some hand holding, but I'll try to not be much bother. Regards, Stephen On Wed, 2021-08-18 at 07:12 +1000, Ben Hutcheson wrote: > Hi Stephen, > > I have pushed support for RTU to the branch feature/modbusrtu, it >

Re: AW: Modbus RTU

2021-08-17 Thread Ben Hutcheson
Hi Stephen, I have pushed support for RTU to the branch feature/modbusrtu, it seems to work. I've only used RTU over TCP using the connection string modbus-rtu:tcp://127.0.0.1:502. There is also a few things to update docs, test and refactoring. Until it gets merged into the develop branch it

Re: AW: Modbus RTU

2021-08-17 Thread Stephen Snow
Hi Ben, On Tue, 2021-08-17 at 06:50 +1000, Ben Hutcheson wrote: > Hi Stephen, > > Thank you for the offer and if it's ok I'll certainly take you up on > it. > Sure, what snapshot should I point maven to? Currently I have 0.8.0 that I was playing with a bit yesterday. > Next week I'll be

Re: AW: Modbus RTU

2021-08-16 Thread Ben Hutcheson
Hi Stephen, Thank you for the offer and if it's ok I'll certainly take you up on it. Next week I'll be starting a new job so I won't be contributing for a while, However I'll try and get something up and running this week. If you are able to test it and/or take over the implementation from there

Re: AW: Modbus RTU

2021-08-16 Thread Stephen Snow
I'd be more than willing to setup some equipment for a lab to test with. Readily available to me are a couple of Omron CP1-H CPU's and a Red Lion G3800C (which is outdated, but communicates with everything ootb), plus I can easily get some Modicon stuff as well. The Omrons are fitted with serial

AW: Modbus RTU

2021-08-16 Thread Christofer Dutz
Hi Stephen, it's not that we're dropping anything ... it's just that we haven't put any work into creating such a driver. Some day, if someone stumbles over PLC4X with the need to use ASCII, we might implement it for them (Mabe as a paid-gig or not). In the inital days of PLC4X I invested a

Re: AW: Modbus RTU and RTU over TCP

2021-04-17 Thread Stavros Nicolakopoulos
you started. > > Chris > > Holen Sie sich Outlook für Android<https://aka.ms/AAb9ysg> > > > From: Stavros Nicolakopoulos > Sent: Saturday, April 17, 2021 9:27:27 AM > To: dev@plc4x.apache.org > Subject: Re: AW: Modbus RT

Re: AW: Modbus RTU and RTU over TCP

2021-04-17 Thread Christofer Dutz
he.org Subject: Re: AW: Modbus RTU and RTU over TCP You are right about the RTU over TCP -it should be the same as RTU over Serial, just using the TCP transport- but the RTU protocol is slightly different. You don't write the transaction ID, the protocol ID and the data length to the

Re: AW: Modbus RTU and RTU over TCP

2021-04-17 Thread Stavros Nicolakopoulos
You are right about the RTU over TCP -it should be the same as RTU over Serial, just using the TCP transport- but the RTU protocol is slightly different. You don't write the transaction ID, the protocol ID and the data length to the buffer. And then you must compute the CRC (Cyclic Redundancy

AW: Modbus RTU and RTU over TCP

2021-04-16 Thread Christofer Dutz
Hi Stavros, and welcome to our cool little project list :-) As I mentioned on SO I would assume that it should be simple to implement Modbus RTU as in general it should just be a different encapsulation and the serial transport, we already have (or in case of RTU over TCP well that should be