On Tue, Dec 20, 2016 at 18:33 +0100, Uwe Hermann wrote: > > On Mon, Nov 28, 2016 at 10:10:45PM +0100, Gerhard Sittig wrote: > > Got my hands on a Metrix MX56C, which is said to be compatible > > with or identical to the BK Precision 5390. The DMM chip is > > referred to as "ASYC-II", see the image in the info box at > > https://sigrok.org/wiki/Metrix_MX56C . > > > > Wrote a driver for the "dumb" UART mode where users have to press > > the PRINT button. This requires an RX only connection to the PC. > > Merged, thanks a lot!
You asked about string routines and potential improvements on portability. See git://repo.or.cz/libsigrok/gsi.git serial-dmm-asycii http://repo.or.cz/libsigrok/gsi.git/shortlog/refs/heads/serial-dmm-asycii for quick web access. NB: I like the "commitdiff" links to get an idea, as they are most similar to "log -p --stat" that I use locally, and are similar to format-patch output for ML traffic. Commit 321cc31a661c is rather straight forward, and I'm confident about it. But I'd like to get a review on commit 216ea623bb75. I didn't quite get that "exponent" stuff, which is why the comments about it are a little fuzzy ("augments the number value" was the best I could do back then). I guess it's not really an "exponent", but neither is it strict "precision" as it does not cover the integer part. The best description I could come up with in the meantime is "(significant) length of the fractional part" of a measurement value. That is required in addition to the float variable, as the internal representation of the value does not tell how much of it was significant at the origin. The HEAD of the branch is operational though. Have tested with kiloOhms, milliVolts, and nanoFarad. Output from sigrok-cli matches the meter's display. The "has prefix" approach might not translate to metex14.c which asycii.c was derived from. Metex14 code is case _insensitive_ (but does not suffer from the "adjacent flags" constraint, I guess, and can keep getting away with the existing casecmp). For strcmp(3) there might be g_strcmp0() as a replacement. The sscanf(3) call could become sr_atof_ascii(). virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
