I am indeed seeing data values. The options the sw provides are not ideal, at least as I am able to understand it, but data does come across.
I would need to understand more (i.e., something) about pyserial to make the change to ttyUSB0, but all this is more progress than I have had in all the time spent beating on this. -Denis On Sun, Jan 7, 2018 at 11:37 AM, Russell Senior <russ...@personaltelco.net> wrote: > Do you mean you are seeing data values from the DMM? If so, does the same > software work with the USB-serial cable? You might need to modify the code > to use /dev/ttyUSB0 instead of /dev/ttyS0. > > On Jan 7, 2018 10:04 AM, "Denis Heidtmann" <denis.heidtm...@gmail.com> > wrote: > > > > > On Mon, Jan 1, 2018 at 11:46 AM, Denis Heidtmann < > > denis.heidtm...@gmail.com> > > wrote: > > > > > I am looking into ways to examine the serial traffic to/from my dmm. > > > <snip> > > I found a python script intended to interface with the mas-345: > https://github.com/markrages/py_test_interface > https://github.com/markrages/py_test_interface/blob/master/mas345.py > > I gave it a try on my desktop (which has a serial port). To get it to run > I changed a couple of parameters and commented out one that was generating > a no-such-parameter error. Then I put it into debug mode so I could see > the traffic from the meter. The good news is it appears that the meter > does report values as the documented protocol indicates. How the > communication is done is buried in the "serial" Python module. Someone who > understands Python could learn from this; I cannot. > > -Denis > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
