Stopping the service doesn't appear to make any difference.
Thanks for all your help Christo. I've just about run out of steam for
sigrok. I was thinking getting the Fluke 45 DMM working would be a
simple matter. And later I would try to contribute back by getting my
Agilent scope (something that's not part of sigrok yet) working. But
after all this investment in time it looks like we're getting no where.
Maybe I'll try again in the fall. We'll see.
-thanks.
On 6/1/21 8:42 AM, Christo Crause wrote:
Hi Stuart,
One guess is that modem manager is probing the serial port[1], messing
up the device state.
Test after disabling modem manager with:
sudo systemctl stop NetworkManager.service
Hope this helps...
1. See e.g. https://sourceforge.net/p/sigrok/mailman/message/35571999/
<https://sourceforge.net/p/sigrok/mailman/message/35571999/>
On Tue, Jun 1, 2021 at 2:20 PM stuart <stu...@xnet.com
<mailto:stu...@xnet.com>> wrote:
Hi Christo,
Well, this is getting interesting:
> ./sigrok-cli --driver
fluke-45:conn=/dev/ttyUSB0:serialcomm=9600/8n1 --scan
> The following devices were found:
> FLUKE [S/N: 6123456] with 2 channels: P1 P2
And turning on logging and setting it to 5 have pushed out and endless
stream of events. I'll look at this in more detail later, but after
failing a transaction where sigrok sent "*IDN?" closing and re-opening
the ttyUSB0 port, sigrok endlessly sends out "FUNC1?", "AUTO?", "FUNC2"
& "AUTO?". The repeats these 4 commands endlessly.
On 6/1/21 2:42 AM, Christo Crause wrote:
>
> On Tue, Jun 1, 2021 at 12:14 AM stuart <stu...@xnet.com
<mailto:stu...@xnet.com>
> <mailto:stu...@xnet.com <mailto:stu...@xnet.com>>> wrote:
>
> I should also note that the FTDI adapter I am using contains what
> appears to be transmit and receive LEDs. Both of which are
flashing
> when using sigrok-cli w/the --continuous option. Just to verify,
> when I
> use minicom and successfully obtain the current voltage
reading from
> the
> fluke-45. I see the transmit and receive LEDs flash while
using minicom
> as expected. So it would seam something is being sent to the
fluke-45
> and something is being returned from the fluke-45 while
running sigrok.
> But noting is printed out as expected at standard output.
>
>
> My only suggestion is to get diagnostics from sigrok. Try the
following
> commands:
> sigrok-cli --driver
fluke-45:conn=/dev/ttyUSB0:serialcomm=9600/8n1 --scan
>
> This should identify the fluke and confirm that communication is
working
> properly.
> You can also try omitting the serialcomm option,
> the sigrok-cli example command for scan omits this for its serial
based
> example.
>
> You can also increase the log level from 0 (None) to 5 (spew)
using the
> --loglevel option,
> which may shed some light on the activity you observe.
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
