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 Fluke 45's echo when connecting to Sigrok.
[ The length seems to be necessary, a short "show the log" went unanswered. Hope the extended context helps to better understand the cause of the frustration, and avoids it the next time around. ] Until you got a wiki account (don't know if the bot is currently active which is involved in the account creation), or somebody with an account and the information at hand will update the page, you can do something even better. Do _show_ the UART communication between the application and the device. It's essential information, and still has not become available yet. That's the point I tried to make, and failed to get across so far. (No, the personal mail -- which nobody else could see, reason about and help or learn from -- neither had it. You quoted part of the operating system loading an application, but specifically dropped the essential part of the device being talked to and responding in ways which the application does not expect.) If you could make that sigrok log output available which contains the device communication, this would be really helpful. More than the mere statement that you are not affected any longer, while others still are. If you are concerned about the log's volume, then at least provide the important section where the device gets identified (IDN) up to the completion of one or two measurement attempts (FUNC/AUTO). That several or all of them fail, and keep failing, is well understood. But it's so damn frustrating when you ask for help and then let down those who try to help you by specifically not providing the information that they need to help you. While you do have that information at hand and nobody else has it. For the motivation of that request see this commit message. https://sigrok.org/gitweb/?p=libsigrok.git;a=commitdiff;h=a36b21fb89ca56a92cd27b3098ef391fa61adbc3 It's based on what's available so far. Assumes that the serial echo either breaks the identification even before measurements are taken, or that disabled echo lets identification as well as measurements succeed. Which seemed plausible to me at that time, and is all I could make of what has become available so far. If that assumption is wrong (your recent communication suggests that it is), then something should be done about it. In the driver which can rub the "echo is enabled, turn it off" in the user's face. A note in the wiki is easily missed. Right now any developer who wanted to improve that situation in the users' interest can't do a thing, because: You guessed it, essential information is missing. So we are stuck. Consider spending the few minutes to help your fellow users. Thank you! Regarding the wiki: Can you suggest a text in case somebody else applies the update to the page? All the information currently available is "some echo needs to get checked and disabled". Would be nice to outline how to do that, unless it's totally obvious to those who have these devices. The front panel image https://sigrok.org/wimg/f/f4/Fluke_45_front.jpg doesn't suggest any of the buttons. See some of the handheld DMM pages (121GW, UT181A) where a button needs to get pressed or a menu item needs to get enabled before serial communication becomes available. We want that hint in a prominent place in the device pages. And in README.devices, too. Source code is often more up to date than wiki pages are. https://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=README.devices A previous version of the fluke-45 driver did check for the echo as you noticed. But did so in an inappropriate location, where a workaround for one rarely used device kept breaking several other people's more popular devices. That's why the test got disabled, and recently was removed. The available information at the time strongly suggested that automatic detection would not be possible. Would be nice if we could have the best of all: other devices unaffected, _and_ reliable operation for the fluke-45 device, _and_ helpful diagnostics to users when a known fatal condition is seen. Can we get there, please? 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. _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
