tuxmaster / qtdmm Goto Github PK

When in either DC or AC modes, the terminal gets spammed with

Unknown unit!
Unknown unit!
Unknown unit!
Unknown unit!
Unknown unit!
Unknown unit!
Unknown unit!
Unknown unit!
Unknown unit!

And doesn't display a reading.

I'm not sure where to start debugging this.

Working great with a Metex ME-11.

http://i.imgur.com/KB12dkC.jpg

Thanks for the Qt5 port, it's made it easier to build since that's the env I'm running now. Not sure if you know that the original author did an update he calls QtDMM2 and I believe he breaks out the code into a commandline tool( CDMM ) and a GUI display(QTDMM2). It's built with Qt4 so I've not been able to try it yet.

I found it while looking for a commandline tool since I'd like to stick a single lithium cell powering an rPiZW and do some data logging without a big laptop connected and using ssh and scp to see what's going on.

Again, thanks for the Qt5 port.
http://www.mtoussaint.de/qtdmm2.html#description

The QtDMM version as specified in the License file is GPL-3.0.

I just wanted to know if there are plans to support Uni-Trend UT61B and UT61D and Metex-3840 as per post-fork 0.9.2 changes.

I'd create a PR myself but I don't know this code at all.

Hi,

at first I want to thank you that you provide QtDMM for Qt5 on Github. I found your repository today and want to use it together with my Voltcraft VC870. But back to that device later...

1st issue) In order to build QtDMM, I had to modify the file src/src.pro:

Before:
lrelease.commands = $$[QT_INSTALL_BINS]/lrelease-qt5 ${QMAKE_FILE_IN} -qm translations/${QMAKE_FILE_BASE}.qm

After:
lrelease.commands = $$[QT_INSTALL_BINS]/lrelease ${QMAKE_FILE_IN} -qm translations/${QMAKE_FILE_BASE}.qm

On my system (Gentoo Linux, Qt-5.6.1) there is no file "lrelease-qt5". Here, it is just called "lrelease" without the suffix. If you also have the "lrelease" file on your disk, it would be better to refer to that instead.

2nd issue) For the INSTALL instructions file:
I have both "Qt 4.8.6" and Qt 5.6.1" installed on my system. If I just configure with a plain "qmake" call it will refer to Qt4 and break later during the make process. The solution was to invoke it using "QT_SELECT=qt5 qmake". Perhaps this is worth to be mentioned in your instructions file. Or better, maybe there is some kind of additional statement that Qt5 is a requirement, so that qmake automatically selects Qt5 instead of Qt4?

Regarding the VC870 multimeter: this device is currently not supported as it uses a 23 byte protocol that was not implemented for QtDMM yet. The specs for that are available and I already had a look into your sources and am sure that I can add the missing functionality easily. But before doing that, can you please clarify how your project relates to "http://www.mtoussaint.de/qtdmm.html" in terms of updates / merges? His repository seems active, but it still depends on Qt4. Is it better to add support for the VC870 there, and you merge it, or did both repositories diverted too much? What do you recommend?

Thanks, kind regards,
Florian

Hi,

I nearly finished the support for the Voltcraft VC870 multimeter in my branch :-) Please do not merge it yet, as to complete the frequency mode I have to get a frequency synthesizer from work first in order to fix scaling and the position of the decimal dot.

However, there is a problem with the display of the bar graph. In line 380 of file src/sources/displaywid.cpp the wrong color is selected: instead of using palette().window().color(), which is the background color, one has to use palette().windowText().color(). Otherwise you paint gray on gray ;-)

See:
Strunzdesign@f75fea7

Feel free to change that in your branch, or just wait for my pull request as soon as I completed support for the frequency mode. Then you'll get that for free.

Regards,
Florian

Hallo,

wenn ich per Import eine zuvor per Export erzeugte Datei laden will, dann bekomme ich ein "Segmentation fault". Verwendete Version QtDMM 0.9.8 unter gentoo linux.

I'm getting a build error on my MacBook running on macOS Monterey 12.1

/opt/homebrew/bin/../../../bin/qt5/lrelease translations/qtdmm_de.ts -qm translations/qtdmm_de.qm
make[1]: /opt/homebrew/bin/../../../bin/qt5/lrelease: No such file or directory
Putting child 0x600000e39cc0 (qtdmm_de.qm) PID 8491 on the chain.
Live child 0x600000e39cc0 (qtdmm_de.qm) PID 8491
Reaping losing child 0x600000e39cc0 PID 8491
make[1]: *** [qtdmm_de.qm] Error 1
Removing child 0x600000e39cc0 PID 8491 from chain.
Reaping losing child 0x600000cf4000 PID 8485
make: *** [sub-src-make_first-ordered] Error 2
Removing child 0x600000cf4000 PID 8485 from chain.

I installed qt5 via brew and lrelease is inside PATH. The error comes from the line 31 of src/src.pro:

 } else {
lrelease.commands      = $$[QT_INSTALL_BINS]/../../../bin/qt5/lrelease ${QMAKE_FILE_IN} -qm translations/${QMAKE_FILE_BASE}.qm
 }

This resolves the issue for me:

 } else {
 lrelease.commands      = $$[QT_INSTALL_BINS]/lrelease ${QMAKE_FILE_IN} -qm translations/${QMAKE_FILE_BASE}.qm
 }

I will provide an pull request, not sure if this breaks any other build that is not based on linux+g++.

Build fails on arch with the following error:

sources/main.cpp: In function ‘void myMessageOutput(QtMsgType, const QMessageLogContext&, const QString&)’:
sources/main.cpp:45:24: error: format not a string literal and no format arguments [-Werror=format-security]
45 |                  qFatal(QString("Fatal: %1").arg(msg).toUtf8());
cc1plus: some warnings being treated as errors
make[1]: *** [Makefile:925: ../tmp/obj/main.o] Error 1
make[1]: Leaving directory '/home/aakodadi/.local/qtdmm-qt5-git/src/qtdmm-qt5-git/src'
make: *** [Makefile:47: sub-src-make_first-ordered] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

I'm trying to build it on OS X High Sierra 10.13.6.
I use a UNI-T UT61E which is not supported with a custom serial to USB adapter. It can connect with official qtdmm 0.8.12 and show correct numbers but not decoding correctly. For example it shows 04898 when the multimeter reads 4.898V. (I connect it at 19200 7-O-1).
I found another qtdmm port here that is compatible with my multimeter but I cannot build it on OS X. Also there are many differences in the code to use a USB HID device instead of a serial adapter so I was thinking to keep only the decoding part from that user.
I built your code on OS X but it's not working as expected. It takes longer to connect to my multimeter and shows the same data with 0.8.12 version but it's not refreshing the data (might refresh once after a long time). I added the function for the UT61E decoding from the other user and it has the same issue. Connects after a while, shows correct data, but doesn't refresh.

What could be the issue? I know it's an old project but I'd really like to build it and share the code once it's 100% functional.