how to setup agilent u1252b with sigrok - Page 1
Forum section: electronics / testgear

author: linux-works
author_rank: Super Contributor
timestamp: March 04, 2018, 11:22:52 pm
content: I can't seem to get this to work.I have the actual agilent usb opto cable, its plugged into my u1252b and if I run a term program on linux and use 9600 with /dev/ttyUSB1 (say),, if I press and hold the log button on the meter, a single ascii quoted value comes out of the serial port. so the hardware seems to work.I got the meter used, with no sw or manual. I first need to know if I have to set the meter up in some special way and then run sigrok-cli on linux?(I guess this really is a bidirectional cable and its not a 'push only' receive cable?)next question, I have installed the sigrok utils on linux:Code:# dpkg -l | grep sigrokii libsigrok-dev:amd64 0.3.0-1build1 amd64 sigrok hardware driver library - development filesii libsigrok2:amd64 0.3.0-1build1 amd64 sigrok hardware driver library - shared libraryii libsigrokdecode-dev:amd64 0.3.0-1build1 amd64 sigrok protocol decoding library - development filesii libsigrokdecode2:amd64 0.3.0-1build1 amd64 sigrok protocol decoding library - shared libraryii pulseview 0.2.0-1.1 amd64 sigrok logic analyzer, oscilloscope, and MSO GUIii sigrok 0.2-3 all Logic analyzer and protocol decoder software suite (metapackage)ii sigrok-cli 0.5.0-1 amd64 command-line frontend for the sigrok softwareii sigrok-firmware-fx2lafw 0.1.2-1 amd64 Firmware for Cypress FX2(LP) based logic analyzersbut when I try to scan, I get nothing:Code:# sigrok-cli --samples 2 -l 5 --driver=agilent-dmmsr: libsigrok loglevel set to 5.sr: backend: Sanity-checking all drivers.sr: backend: Sanity-checking all input modules.sr: backend: Sanity-checking all output modules.srd: libsigrokdecode loglevel set to 5.sr: hwdriver: Initializing driver 'agilent-dmm'.sr: hwdriver: Scan of 'agilent-dmm' found 0 devices.No devices found.I've tried forcing it to be ttyUSB1, with no more luck.I am running as root or user; neither works.what am I doing wrong?

author: tridentsx
author_rank: Regular Contributor
timestamp: March 05, 2018, 12:54:20 am
content: Did you check from terminal that the meter responds correctly to*IDN?just to make sure everything is working before adding sigrok into the picture.The below page gives some information etc on the protocol for these meters and the serial interface.https://sigrok.org/wiki/Agilent_U12xxx_series

author: linux-works
author_rank: Super Contributor
timestamp: March 05, 2018, 12:58:23 am
content: I missed that page, that's a good one, thanks!I was able to runhttp://sourceforge.net/projects/dmmutils/stuff, though, and that's kind of cool. it takes close to a second to fetch a value. how fast can data be gotton from this series? I can set the baud rate to 9600 or 19200 and its 9600 now.I could type *IDN? into minicom and get an agilent reply. so the com port and even dmmutils are working fine.still not able to get sigrok cli to work.

author: linux-works
author_rank: Super Contributor
timestamp: March 05, 2018, 01:01:30 am
content: /home/bryan/dmmutils0.1> time ./dmmutils -f1 --port=/dev/ttyUSB1100.0000 uV0.000u 0.002s0:00.580.0% 0+0k 0+0io 0pf+0w/home/bryan/dmmutils0.1>but that could just be dmmutils taking that long.

author: abraxa
author_rank: Frequent Contributor
timestamp: March 05, 2018, 08:57:19 am
content: Quote from: linux-works on March 04, 2018, 11:22:52 pmThese versions are roughly 3 years old, so even though they should work, I suggest either getting newer versions from your distribution or grabbing the sigrok-cli AppImage binary fromhttps://sigrok.org/wiki/Downloadsand using that.Quote from: linux-works on March 04, 2018, 11:22:52 pmNot sure what exactly you did to "force it to be ttyUSB1" but indeed, you need to tell sigrok-cli which device to use, like so:Code:# sigrok-cli --samples 2 -l 5 --driver agilent-dmm:conn=/dev/ttyUSB1

author: WhichEnt2
author_rank: Regular Contributor
timestamp: March 08, 2018, 05:09:26 am
content: I tried u1252a with sigrok and give up on that some time ago.Any attempt to acquire some live readings from meter beyond the --show stuff comes to nothing. DMM are randomly beeping until the sigrok-cli is stopped.Works with native software and dmmutils, though.

author: linux-works
author_rank: Super Contributor
timestamp: March 08, 2018, 05:53:32 am
content: I wonder why ubuntu/mint have such OOD versions? 3 years does sound like a long time.I tried building this from source and it was not a fun thing.. not even sure I was able to fully build everything. it reminds me of when I tried to build gnome, fully from source, pkg by pkg. half a day later, I gave up.ok, there's an appimage. I'll try that. I don't love those things, but I understand why they exist.the reverse engineered dmmutils does seem to work, I've been showing people at work this util and the meters I grabbed off the bay. (for some reason, its hard to find/buy that ir/usb expensive dongle cable thing. found one for $80, shipped from UK to the US. can't find anyone in the US who still has them. shame, as the meters are easily buyable and without some ir/usb cable, half the reason for owning this meter is lost).

author: linux-works
author_rank: Super Contributor
timestamp: March 08, 2018, 05:56:26 am
content: for any sigrok devs watching, a bit more debug info (higher -d levels) might be advised. show me more about what you tried (the program) and what failed. yeah, you didn't see my dmm on a wire. tell me a bit more about what you tried and when you gave up. it might help me debug it better. don't force me to strace it, I don't wanna do that

author: WhichEnt2
author_rank: Regular Contributor
timestamp: March 08, 2018, 06:41:53 am
content: I don't really want to dig into this again and don't think the sigrok devs might potentially care about it.https://www.pastiebin.com/5aa0d7eb6354ftest run on loglevel 5Ir interface -https://www.medo64.com/agir/schematic with use of typical chinese FT232RL usb to serial adapter.

author: abraxa
author_rank: Frequent Contributor
timestamp: March 08, 2018, 09:51:16 am
content: Quote from: linux-works on March 08, 2018, 05:56:26 amUsually, log level 5 is sufficient but I understand that in certain cases, debug information may be missing. Can you please put the output of "sigrok-cli --samples 2 -l 5 --driver agilent-dmm:conn=/dev/ttyUSB1" into a pastebin and link to it here?

author: abraxa
author_rank: Frequent Contributor
timestamp: March 08, 2018, 09:54:14 am
content: Quote from: WhichEnt2 on March 08, 2018, 06:41:53 amI understand you may be frustrated but it's not nice to imply that we don't care about people's problems. The issue you're seeing is unknown to me, so if you had filed a bug athttps://sigrok.org/bugzilla/enter_bug.cgi?product=libsigrokthen we would've been able to fix it. I suggest you file a bug, assign it to the agilent-dmm driver and copy the pastebin's content into the bug report.

author: WhichEnt2
author_rank: Regular Contributor
timestamp: March 08, 2018, 12:59:39 pm
content: Quote from: abraxa on March 08, 2018, 09:54:14 amSorry if I upset you. But usually this is the way how many of the opensource projects works.This is not a problem any longer, because I do not want to waste no more time on that. Either mine or persons which may potentially working on fixing the bug.Thanks.

author: s8548a
author_rank: Regular Contributor
timestamp: June 08, 2018, 10:39:15 am
content: Sorry, a dumb question:Sigrok is basically a logic analyzer sw right? what it has to do with the DMM's? I mean what exactly the possibilities/usage?