I'm stumped. I have a ut61e communicating via a prolific PL2303. It works
fine if I run:
sigrok-cli --driver=uni-t-ut61e-ser:conn=/dev/ttyUSB1 --samples 1
I created a udev rule that creates the following symlink for the device:
/dev/ttyUSBut61e
Here is the udev rule:
SUBSYSTEM=="tty", ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303",
SYMLINK+="ttyUSBut61e", ENV{ID_SIGROK}="1"
If I run: sigrok-cli --driver=uni-t-ut61e-ser:conn=/dev/ttyUSBut61e
--samples 1
I get:
sr: serial: Attempt to open serial port with invalid parameters.
No devices found.
Everything looks good with the symlink as far as i can tell...I know enough
linux to be dangerous. Also, when I try to use that symlink with python,
it appears to work (or get farther at least):
>>> import minimalmodbus
>>> i = minimalmodbus.Instrument('/dev/ttyUSBut61e', 1)
>>> i
minimalmodbus.Instrument<id=0xb66be8d0, address=1, mode=rtu,
close_port_after_each_call=False, precalculate_read_size=True,
clear_buffers_before_each_transaction=True, handle_local_echo=False,
debug=False, serial=Serial<id=0xb66be870,
open=True>(port='/dev/ttyUSBut61e', baudrate=19200, bytesize=8, parity='N',
stopbits=1, timeout=0.05, xonxoff=False, rtscts=False, dsrdtr=False)>
Anyone have any ideas? Could this be a bug with libserial?
Best,
Nate Costello
*first post so sorry if I violated some norms. Also tried the IRC channel
but got no bytes.
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
