I do not see any data to the QtDMM in the display or in diagram with the protocols for MASTECH M9803R, ELV etc

Bug #164913 reported by leif sandahl
6
Affects Status Importance Assigned to Milestone
qtdmm (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: qtdmm

Sorry but I am new on this and do not really known if "MERGE" is my problem. But here is my BUG:

I have probably find a bug in QtDMM ver 0.8.8 and 0.8.10 used in Ubuntu and Debian (after new versions). I have only problems with the protocols for MASTECH M9803R, ELV etc. I do not see any data to the QtDMM in the display or in diagram. But the cursor move on zero and go further when I start. My MAS 345 work ok in QtDMM ver 0.8.8 and 0.8.10.

Revision history for this message
leif sandahl (15aleif) wrote : Re: [Bug 164913] Re: I do not see any data to the QtDMM in the display or in diagram with the protocols for MASTECH M9803R, ELV etc

Same problem with the Qtdmm ver 0.8.12 as in 0.8.8 and 0.8.10 do not see the
data from protocol for MASTECH M980R (11 bytes binary, continous) but other
protocols work well. Version 0.8.6 works ok for M980R.

Regards Leif

2007/11/25, Arnaud Blouin <email address hidden>:
>
> ** Summary changed:
>
> - I have probably find a bug in QtDMM ver 0.8.8 and 0.8.10 used in Ubuntu
> and Debian (after new versions). I have only problems with the protocols for
> MASTECH M9803R, ELV etc. I do not see any data to the QtDMM in the display
> or in diagram. But the cursor move on zero and go further when I start. My
> MAS 345 work ok in QtDMM ver 0.8.8 and 0.8.10.
> + I do not see any data to the QtDMM in the display or in diagram with
> the protocols for MASTECH M9803R, ELV etc
>
> --
> I do not see any data to the QtDMM in the display or in diagram with the
> protocols for MASTECH M9803R, ELV etc
> https://bugs.launchpad.net/bugs/164913
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
leif sandahl (15aleif) wrote :

I have installed Ubuntu 8.10. I tried to use the QtDMM ver 0.8.12 and the multimeter Mastech M9803R which not have work earlier in the software. I have now find it is a wrong setting in the software for Mastech M9803R. The parity is set to EVEN in the software and it do not work. If I change the parity to NONE from default settings in software the Mastech MR9803R works with visible data. How is the routine to set right default settings in software?

Revision history for this message
Daniel T Chen (crimsun) wrote :

Can you describe which specific models function correctly with the default settings in intrepid?

Changed in qtdmm:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
leif sandahl (15aleif) wrote :

Dear Daniel,

Sorry I am not relay understand your question. If you need more information
, please write simple English to me. But I try to give answer. The default
settings in QtDMM software is EVEN parity for MASTECH M9803R and ELV M9803R
(11 bytes binary, continuous). After upgrade Ubuntu versions and at same
time get new version of QtDMM was the displays figures disappeared. But my
other multimeters with other settings work ok. Now have I found it was or
have been some bad changes in the default settings in software for M9803R
protocol. If I changes parity from EVEN (is set default) to NONE it work ok.

I have copied 2 images to this mail with different settings one with ok
function and one not function.

Best Regards
Leif

2008/11/16 Daniel T Chen <email address hidden>

> Can you describe which specific models function correctly with the
> default settings in intrepid?
>
> ** Changed in: qtdmm (Ubuntu)
> Importance: Undecided => Low
> Status: New => Incomplete
>
> --
> I do not see any data to the QtDMM in the display or in diagram with the
> protocols for MASTECH M9803R, ELV etc
> https://bugs.launchpad.net/bugs/164913
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in qtdmm (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.