On Sat, 2021-06-05 at 08:36 -0500, stuart wrote:
>
> I'd be happy to update the Flue 45 wiki. If someone would add me so
> I could log in.
>
> Spot checking a few other wikis, I didn't see a "Hint" section.
> Perhaps that would be a good place to add 1 or 2 sentences regarding
> turning off the Fl
Stuart,
I have a vague recollection that I ran into the same problem while
working with the Fluke 45. As you point out, by default the meter will
echo back the command it was sent (along with a prompt character if
memory serves) but Sigrok expects raw data. On the other hand, humans
like to s
Hi Stuart,
Good news! I think a note about disabling echo mode should be added to the
wiki to help future users. Perhaps also a mention of baud rate, but that
will probably be dependent on the connecting hardware.
On Thu, 3 Jun 2021, 05:37 stuart, wrote:
> Hi Gerhard,(and Christo)...
>
> I figu
Hi Gerhard,(and Christo)...
I figured it out. I'm running Linux so I can run sigrok w/STRACE. I
found STRACE and sigrok's loglevel=5 are the same. Both produced too
much data. But I did see what looked like communication and what looked
like many communication failures. I started looking
On Tue, 2021-06-01 at 07:20 -0500, stuart 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
On Wed, Jun 2, 2021 at 3:55 AM stuart wrote:
> 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 co
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
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/
On Tue, Jun 1, 202
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
On Tue, Jun 1, 2021 at 12:14 AM stuart 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
Hi Christo,
The udev rules were not installed. I followed these instructions and
rebooted just to be safe:
https://sigrok.org/wiki/Fx2lafw#Install_the_udev_rules_file
I installed the 61-libsigrok-plugdev.rules because the user was already
a member of the plugdev group. These files came out
Hi Stuart,
Regarding user access to the FT232R, can you check if the sigrok udev rules
[1,2] are installed? I guess you could run sigrok as root, but it really
should work for regular users too. I can use a FT232H as a normal user,
with the sigrok udev rules installed, on Linux Mint (so quite sim
Hi Christo,
The output of:
"sudo lsusb -v -d 0403:6001"
Bus 001 Device 005: ID 0403:6001 Future Technology Devices International, Ltd
FT232 Serial (UART) IC
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass0
Hi Stuart,
That error seems to originate from libftdi, suggesting that libusb_open
failed (
http://developer.intra2net.com/git/?p=libftdi;a=blob;f=src/ftdi.c;hb=HEAD#l407).
If so it cannot be fixed on sigrok's side since it relies on the underlying
drivers to communicate with the devices.
Can you
14 matches
Mail list logo
