« previous next »
Pages: Prev 1 2 3 [4] 5 6 7 8 9 ... 11 Next  All   Go Down

Author Topic: UltraDMM Software Project  (Read 132013 times)

0 Members and 1 Guest are viewing this topic.

Offline Monkeh

  • Super Contributor
  • ***
  • Posts: 7992
  • Country: gb
Re: UltraDMM Software Project
« Reply #75 on: September 03, 2012, 09:22:19 pm »
Well then, it's not raw, is it? :)

Let's go over this test output so we can make sure you're reading it right.

2B 30 30 30 30 20 31 11 00 00 80 00 0D 0A
0010.1011 0011.0000 0011.0000 0011.0000 0011.0000 0010.0000 0011.0001 0001.0001 0000.0000 0000.0000 1000.0000 0000.0000 0000.1101 0000.1010

First byte: ASCII, + or -.
Second, third, fourth, and fifth bytes: ASCII, numerical, 0 to 9.
Sixth byte: ASCII, space.
Seventh byte: ASCII, 0, 1, 2, or 4, for decimal place (this is where the datasheet is incorrect).
Eighth to eleventh bytes: Hex encoded bit array. As datasheet.
Twelfth byte: Hex encoded bit array, for the bar graph. Bit 7 is +/-, 1 for +. I'm not sure of the rest of that as I haven't looked at it.
Thirteenth byte: ASCII CR
Fourteenth byte: ASCII LF
Logged
 

Offline Monkeh

  • Super Contributor
  • ***
  • Posts: 7992
  • Country: gb
Re: UltraDMM Software Project
« Reply #76 on: September 03, 2012, 09:27:35 pm »
Quote from: BThunderW on September 03, 2012, 09:10:37 pm
Hmm. If you can humor me and try the latest patch. I'm wondering if the newline character is being excluded from the buffer. That would make the buffer length 13 characters and not 14.

Tom

That's more like it. It is, however, misinterpreting the output. Volts as ohms (AC and DC), ohms come up as negative, overload is causing an incorrect input string (I'll check the meter output with OL displayed shortly), temperature is negative and decimal place is reversed, not indicating unit. hFE is coming up as inductance, and microamps as diode test.

Progress!

E: Okay, overload display: ASCII again, ?0:?.
« Last Edit: September 03, 2012, 09:30:12 pm by Monkeh »
Logged
 

Online mariush

  • Super Contributor
  • ***
  • Posts: 5017
  • Country: ro
  • .
Re: UltraDMM Software Project
« Reply #77 on: September 03, 2012, 09:32:14 pm »
I get this with the latest patch posted here. See attached image. That doesn't look like raw bytes to me... it's not a consistent output, it varies when flipping between modes as you can see (i just changed to the next setting on the meter every few seconds)

later edit:  And the refusal to exit is back. With only the raw log window open , File , Exit , do you want to save before exit, no , .... nothing. Exited after accepting to save.
« Last Edit: September 03, 2012, 09:38:14 pm by mariush »
Logged
 

Offline BThunderWTopic starter

  • Regular Contributor
  • *
  • Posts: 118
  • Country: ca
Re: UltraDMM Software Project
« Reply #78 on: September 03, 2012, 11:38:49 pm »
Patch released: http://www.ultradmm.com/release/wip/UltraDMMPatch.7z

The fail to exit issue should be resolved.
Raw Log displays output in hex format to avoid further confusion
Modified the FS9922 Code as per Monkeh's suggestions. Hopefully this will mean progress.

Cheers,

Tom
Logged
 

Offline BThunderWTopic starter

  • Regular Contributor
  • *
  • Posts: 118
  • Country: ca
Re: UltraDMM Software Project
« Reply #79 on: September 03, 2012, 11:40:51 pm »
Actually, that's exactly what the meter returns. I see the same output via serial console.



Quote from: mariush on September 03, 2012, 09:32:14 pm
I get this with the latest patch posted here. See attached image. That doesn't look like raw bytes to me... it's not a consistent output, it varies when flipping between modes as you can see (i just changed to the next setting on the meter every few seconds)

later edit:  And the refusal to exit is back. With only the raw log window open , File , Exit , do you want to save before exit, no , .... nothing. Exited after accepting to save.
Logged
 

Online mariush

  • Super Contributor
  • ***
  • Posts: 5017
  • Country: ro
  • .
Re: UltraDMM Software Project
« Reply #80 on: September 04, 2012, 12:06:42 am »
Thanks. Hex output is better. At least it's the same width and no random characters introduced.

Nope, exit still fails when I say No at the question. App closes fine when I say yes, after a popup saying "saved ok". But the point is it shouldn't ask at all if all i did was watch raw log and maybe show a graph.
Logged
 

Offline BThunderWTopic starter

  • Regular Contributor
  • *
  • Posts: 118
  • Country: ca
Re: UltraDMM Software Project
« Reply #81 on: September 04, 2012, 12:22:44 am »
Hmm. I can't really reproduce this issue.  Can you send me your save file? What OS are you using?

The system prompts to save because it'll attempt to save open windows and their location. Some windows are not meant to be saved though.

Tom

Quote from: mariush on September 04, 2012, 12:06:42 am
Thanks. Hex output is better. At least it's the same width and no random characters introduced.

Nope, exit still fails when I say No at the question. App closes fine when I say yes, after a popup saying "saved ok". But the point is it shouldn't ask at all if all i did was watch raw log and maybe show a graph.
Logged
 

Online mariush

  • Super Contributor
  • ***
  • Posts: 5017
  • Country: ro
  • .
Re: UltraDMM Software Project
« Reply #82 on: September 04, 2012, 12:45:48 am »
I had the save file as c:\temp\a.xml
I wanted to record the screen to show you what I do when that happens but had some "sensitive" files in c:\temp so used the "save as" option in the software to save it as c:\temp\udmm\a.xml

After I closed and started the app again, I can't reproduce the not quitting on no issue anymore. Both xml files are identical though, so not sure what happened there.

I was ready with SysInternals' ProcMon started to export the log just in case I can reproduce it :(

Sorry for potentially wasting your time with this.

Found this though while trying to make the app refuse to quit ... connect to meter, open raw output, go to edit meters, properties, click test ... it will lock for a few seconds and then asks if meter is turned on. Raw output then resumes and everything seems ok.
« Last Edit: September 04, 2012, 12:47:20 am by mariush »
Logged
 

Offline Psi

  • Super Contributor
  • ***
  • Posts: 9930
  • Country: nz
Re: UltraDMM Software Project
« Reply #83 on: September 04, 2012, 12:49:25 am »
I have an older meter that uses the ES51986 chip
http://www.cyrustek.com.tw/spec/ES51986.pdf

It isn't going to work currently, as there are a few small differences, but its pretty close.

*The packet length is different
- 1 less digit packet (no digit 4)
- 1 less option packet (no option 3,4)

*The option packets contents are slightly different

*The range byte has differnt ranges due to 22000 count vs 6000 count

Other than that it looks identical.
-Same serial settings, baud/parity etc.
-Same packet structure (except less info)
« Last Edit: September 04, 2012, 12:51:58 am by Psi »
Logged
Greek letter 'Psi' (not Pounds per Square Inch)
 

Offline BThunderWTopic starter

  • Regular Contributor
  • *
  • Posts: 118
  • Country: ca
Re: UltraDMM Software Project
« Reply #84 on: September 04, 2012, 12:50:23 am »
No worries.

Regarding the Test button. You can't Test on a port that's already open. I suppose I can add a check for that :)

Tom

Quote from: mariush on September 04, 2012, 12:45:48 am
I had the save file as c:\temp\a.xml
I played with the software and used save as option and saved it as c:\temp\udmm\a.xml

After I closed and started the app again, I can't reproduce the not quitting on no issue anymore.

I was ready with SysInternals' ProcMon started to export the log just in case I can reproduce it :(

Sorry for potentially wasting your time with this.

Found this though while trying to make the app refuse to quit ... connect to meter, open raw output, go to edit meters, properties, click test ... it will lock for a few seconds and then asks if meter is turned on. Raw output then resumes and everything seems ok.
Logged
 

Offline BThunderWTopic starter

  • Regular Contributor
  • *
  • Posts: 118
  • Country: ca
Re: UltraDMM Software Project
« Reply #85 on: September 04, 2012, 12:51:49 am »
What's the model number of the meter?

If you're willing to work with me, I can certainly add it to the software.

Tom

Quote from: Psi on September 04, 2012, 12:49:25 am
I have an older meter that uses the ES51986 chip
http://www.cyrustek.com.tw/spec/ES51986.pdf

It isn't going to work currently, as there are a few small differences, but its pretty close.

*The packet length is different
- 1 less digit packet (no digit 4)
- 1 less option packet (no option 4)

*The option packets contents are slightly different

*The range byte has differnt ranges due to 22000 count vs 6000 count

Other than that it looks identical.
-Same serial settings, baud/parity etc.
-Same packet structure (except less info)
Logged
 

Offline Psi

  • Super Contributor
  • ***
  • Posts: 9930
  • Country: nz
Re: UltraDMM Software Project
« Reply #86 on: September 04, 2012, 12:54:52 am »
It's an "APPA 71"

http://www.appatech.com/upload/download/file113039186215566.pdf


You may notice that the manual says RS232 is for the APPA 73 only (not 71,72).
While this is true physically, the APPA 71 uses the same IC and it's easy to wire up your own cable inside from the IC's rs232 out pin to a connector on the case somewhere.
Also the button to enable RS232 does exist on the 71, they just cut off the top of the rubber and didn't put a hole in the plastic for it.  But you can cut your own hole in the plastic and then have a working rs232 button (its just a little below the surface, or you can swap the rubber bit with one of the other buttons you don't use, like hold,range, minmax)

This is exactly what i've done to get data logging from my APPA 71

I'm pretty sure the APPA 72  is the same.
« Last Edit: September 04, 2012, 01:08:39 am by Psi »
Logged
Greek letter 'Psi' (not Pounds per Square Inch)
 

Online mariush

  • Super Contributor
  • ***
  • Posts: 5017
  • Country: ro
  • .
Re: UltraDMM Software Project
« Reply #87 on: September 04, 2012, 01:28:31 am »
Maybe this will help : 

http://flashingleds.wordpress.com/2010/11/30/unlocking-rs232-output-from-your-multimeter/

The guy has an iso-tech with the ES51978...  Lots of other links in the comments

Found it from this older thread: https://www.eevblog.com/forum/general-chat/unlocking-rs232-output-from-cyrustek-ic-multimeter/

Amprobe 34XR-A multimeter apparently uses  ES51960: http://www.cyrustek.com.tw/spec/ES51960.pdf

later edit: Maybe you can also export some presets from this linux software:  http://www.mtoussaint.de/qtdmm.html
« Last Edit: September 04, 2012, 01:53:43 am by mariush »
Logged
 

Offline Monkeh

  • Super Contributor
  • ***
  • Posts: 7992
  • Country: gb
Re: UltraDMM Software Project
« Reply #88 on: September 04, 2012, 01:46:34 am »
Quote from: BThunderW on September 03, 2012, 11:38:49 pm
Patch released: http://www.ultradmm.com/release/wip/UltraDMMPatch.7z

The fail to exit issue should be resolved.
Raw Log displays output in hex format to avoid further confusion
Modified the FS9922 Code as per Monkeh's suggestions. Hopefully this will mean progress.

Cheers,

Tom

Decimal place now correct for temperature, all other issues still remain.

Something is being misparsed.

Raw output in UltraDMM is: 2B-30-30-30-30-20-31-11-00-00-3F-00-0D-0A
True meter output is: 2B 30 30 30 30 20 31 11 00 00 80 00 0D 0A

SB4 is getting mangled somewhere.
« Last Edit: September 04, 2012, 01:50:45 am by Monkeh »
Logged
 

Offline BThunderWTopic starter

  • Regular Contributor
  • *
  • Posts: 118
  • Country: ca
Re: UltraDMM Software Project
« Reply #89 on: September 04, 2012, 04:14:00 am »
Ok. New update deployed.

Changed the ISO Encoding on the Serial Port. Should fix the FS9922 mangling issue. (This one stumped me for a bit)
Added (Untested) ES51986 and ES51960 support (APPA 71/73 and Amprobe 34XR-A)

http://www.ultradmm.com/release/wip/UltraDMMPatch.7z

Tom
Logged
 

Offline Psi

  • Super Contributor
  • ***
  • Posts: 9930
  • Country: nz
Re: UltraDMM Software Project
« Reply #90 on: September 04, 2012, 11:40:03 am »
Quote from: BThunderW on September 04, 2012, 04:14:00 am
Added (Untested) ES51986 and ES51960 support (APPA 71/73 and Amprobe 34XR-A)

Just tested it, it does work for the APPA 71, mostly :)

Here are a few bugs i found while using it with my APPA 71
OS = Windows 7 x64

Values out by a factor of 10
Detail...
All values displayed in the app are out by a factor of 10.
for example 5.167V on DMM is showing as 51.67V
RAW signal = 30-35-31-36-36-3B-38-30-3A-0A
Happens on other things too, ACV, Ohms, capacitance etc.

Continuity range showing kV
Detail...
With the DMM on continuity/diode mode, and with the probes open, the digital display shows ~2.4 kilovolts. hehe, thats a lot of volts
RAW = 30-32-34-31-32-31-39-30-30-0A
With probes shorted it shows zero.

Sometimes the app will refuse to close.
Detail...
I couldn't see any pattern to why it occurs but sometimes when i click the window close [X] the app prompts to save, I click "no" but it doesn't close.
It continues to run, and ignores repeated attempts to close and must be killed in task manager.
Other times it closes fine.

App will crash if you try use it without any multimeter device configured
Detail..
If you run the app with no meters configured then click meters/connect and gauges/add/digital it will throw a Unhanded exception.
"InvaidArgument=Value of "0" is not valid for 'index'
Parameter named index.

Here is the detail for the exception
Code: [Select]
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of '0' is not valid for 'index'.
Parameter name: index
   at System.Windows.Forms.ComboBox.ObjectCollection.get_Item(Int32 index)
   at Gauges.frmGaugeOptions.frmGaugeOptions_Load(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 (RTMGDR.030319-2600)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
UltraDMM
    Assembly Version: 1.0.3.41597
    Win32 Version: 1.0.3.41597
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/UltraDMM.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.278 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.282 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
TriggersUI
    Assembly Version: 1.0.4629.41597
    Win32 Version: 1.0.4629.41597
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/TriggersUI.DLL
----------------------------------------
Infragistics4.Win.Misc.v12.1
    Assembly Version: 12.1.20121.2038
    Win32 Version: 12.1.20121.2038
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Infragistics4.Win.Misc.v12.1.DLL
----------------------------------------
Infragistics4.Win.v12.1
    Assembly Version: 12.1.20121.2038
    Win32 Version: 12.1.20121.2038
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Infragistics4.Win.v12.1.DLL
----------------------------------------
Infragistics4.Shared.v12.1
    Assembly Version: 12.1.20121.2038
    Win32 Version: 12.1.20121.2038
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Infragistics4.Shared.v12.1.DLL
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.233 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Utils
    Assembly Version: 1.0.4629.40437
    Win32 Version: 1.0.4629.40437
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Utils.DLL
----------------------------------------
Triggers
    Assembly Version: 1.0.4629.41596
    Win32 Version: 1.0.4629.41596
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Triggers.DLL
----------------------------------------
Meters
    Assembly Version: 1.0.4629.41596
    Win32 Version: 1.0.4629.41596
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Meters.DLL
----------------------------------------
CommonForms
    Assembly Version: 1.0.4629.41597
    Win32 Version: 1.0.4629.41597
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/CommonForms.DLL
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.233 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
DataReader
    Assembly Version: 1.0.4629.41596
    Win32 Version: 1.0.4629.41596
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/DataReader.DLL
----------------------------------------
Gauges
    Assembly Version: 1.0.4629.41597
    Win32 Version: 1.0.4629.41597
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Gauges.DLL
----------------------------------------
Infragistics4.Win.UltraWinGauge.v12.1
    Assembly Version: 12.1.20121.2038
    Win32 Version: 12.1.20121.2038
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Infragistics4.Win.UltraWinGauge.v12.1.DLL
----------------------------------------
CommonControls
    Assembly Version: 1.0.4629.40437
    Win32 Version: 1.0.4629.40437
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/CommonControls.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.



« Last Edit: September 04, 2012, 11:47:22 am by Psi »
Logged
Greek letter 'Psi' (not Pounds per Square Inch)
 

Offline BThunderWTopic starter

  • Regular Contributor
  • *
  • Posts: 118
  • Country: ca
Re: UltraDMM Software Project
« Reply #91 on: September 04, 2012, 11:55:31 am »
Thanks for the feedback. Will implement shortly. I really gotta find the cause of the fail-to-close issue.

Tom

Quote from: Psi on September 04, 2012, 11:40:03 am
Quote from: BThunderW on September 04, 2012, 04:14:00 am
Added (Untested) ES51986 and ES51960 support (APPA 71/73 and Amprobe 34XR-A)

Just tested it, it does work for the APPA 71, mostly :)

Here are a few bugs i found while using it with my APPA 71
OS = Windows 7 x64

Values out by a factor of 10
Detail...
All values displayed in the app are out by a factor of 10.
for example 5.167V on DMM is showing as 51.67V
RAW signal = 30-35-31-36-36-3B-38-30-3A-0A
Happens on other things too, ACV, Ohms, capacitance etc.

Continuity range showing kV
Detail...
With the DMM on continuity/diode mode, and with the probes open, the digital display shows ~2.4 kilovolts. hehe, thats a lot of volts
RAW = 30-32-34-31-32-31-39-30-30-0A
With probes shorted it shows zero.

Sometimes the app will refuse to close.
Detail...
I couldn't see any pattern to why it occurs but sometimes when i click the window close [X] the app prompts to save, I click "no" but it doesn't close.
It continues to run, and ignores repeated attempts to close and must be killed in task manager.
Other times it closes fine.

App will crash if you try use it without any multimeter device configured
Detail..
If you run the app with no meters configured then click meters/connect and gauges/add/digital it will throw a Unhanded exception.
"InvaidArgument=Value of "0" is not valid for 'index'
Parameter named index.

Here is the detail for the exception
Code: [Select]
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of '0' is not valid for 'index'.
Parameter name: index
   at System.Windows.Forms.ComboBox.ObjectCollection.get_Item(Int32 index)
   at Gauges.frmGaugeOptions.frmGaugeOptions_Load(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 (RTMGDR.030319-2600)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
UltraDMM
    Assembly Version: 1.0.3.41597
    Win32 Version: 1.0.3.41597
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/UltraDMM.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.278 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.282 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
TriggersUI
    Assembly Version: 1.0.4629.41597
    Win32 Version: 1.0.4629.41597
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/TriggersUI.DLL
----------------------------------------
Infragistics4.Win.Misc.v12.1
    Assembly Version: 12.1.20121.2038
    Win32 Version: 12.1.20121.2038
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Infragistics4.Win.Misc.v12.1.DLL
----------------------------------------
Infragistics4.Win.v12.1
    Assembly Version: 12.1.20121.2038
    Win32 Version: 12.1.20121.2038
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Infragistics4.Win.v12.1.DLL
----------------------------------------
Infragistics4.Shared.v12.1
    Assembly Version: 12.1.20121.2038
    Win32 Version: 12.1.20121.2038
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Infragistics4.Shared.v12.1.DLL
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.233 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Utils
    Assembly Version: 1.0.4629.40437
    Win32 Version: 1.0.4629.40437
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Utils.DLL
----------------------------------------
Triggers
    Assembly Version: 1.0.4629.41596
    Win32 Version: 1.0.4629.41596
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Triggers.DLL
----------------------------------------
Meters
    Assembly Version: 1.0.4629.41596
    Win32 Version: 1.0.4629.41596
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Meters.DLL
----------------------------------------
CommonForms
    Assembly Version: 1.0.4629.41597
    Win32 Version: 1.0.4629.41597
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/CommonForms.DLL
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.233 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
DataReader
    Assembly Version: 1.0.4629.41596
    Win32 Version: 1.0.4629.41596
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/DataReader.DLL
----------------------------------------
Gauges
    Assembly Version: 1.0.4629.41597
    Win32 Version: 1.0.4629.41597
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Gauges.DLL
----------------------------------------
Infragistics4.Win.UltraWinGauge.v12.1
    Assembly Version: 12.1.20121.2038
    Win32 Version: 12.1.20121.2038
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/Infragistics4.Win.UltraWinGauge.v12.1.DLL
----------------------------------------
CommonControls
    Assembly Version: 1.0.4629.40437
    Win32 Version: 1.0.4629.40437
    CodeBase: file:///C:/Program%20Files%20(x86)/Kaskingo%20Inc/UltraDMM/UltraDMM/CommonControls.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Logged
 

Offline Monkeh

  • Super Contributor
  • ***
  • Posts: 7992
  • Country: gb
Re: UltraDMM Software Project
« Reply #92 on: September 04, 2012, 12:30:11 pm »
Quote from: BThunderW on September 04, 2012, 04:14:00 am
Ok. New update deployed.

Changed the ISO Encoding on the Serial Port. Should fix the FS9922 mangling issue. (This one stumped me for a bit)
Added (Untested) ES51986 and ES51960 support (APPA 71/73 and Amprobe 34XR-A)

http://www.ultradmm.com/release/wip/UltraDMMPatch.7z

Tom

Excellent, that did it. Although why there's any encoding stumps me.. the dangers of using silly libs? :)

Still left:
  • Overload handling
  • hFE unit
  • Temperature units
Logged
 

Offline BThunderWTopic starter

  • Regular Contributor
  • *
  • Posts: 118
  • Country: ca
Re: UltraDMM Software Project
« Reply #93 on: September 04, 2012, 12:59:07 pm »
For some reason the SerialPort library uses ASCIIEncoding as default. It was rolling over Extended ASCII values.

Can you send me the raw dumps of the outstanding issues?

Tom


Quote from: Monkeh on September 04, 2012, 12:30:11 pm

Excellent, that did it. Although why there's any encoding stumps me.. the dangers of using silly libs? :)

Still left:
  • Overload handling
  • hFE unit
  • Temperature units
Logged
 

Offline Monkeh

  • Super Contributor
  • ***
  • Posts: 7992
  • Country: gb
Re: UltraDMM Software Project
« Reply #94 on: September 04, 2012, 01:04:35 pm »
Quote from: BThunderW on September 04, 2012, 12:59:07 pm
For some reason the SerialPort library uses ASCIIEncoding as default. It was rolling over Extended ASCII values.

Can you send me the raw dumps of the outstanding issues?

Tom


Quote from: Monkeh on September 04, 2012, 12:30:11 pm

Excellent, that did it. Although why there's any encoding stumps me.. the dangers of using silly libs? :)

Still left:
  • Overload handling
  • hFE unit
  • Temperature units

Overload (in ohms range): 2B 3F 30 3A 3F 20 32 21 00 10 20 3D 0D 0A
hFE you're detecting fine, but the UI is indicating inductance (the chip can't even do inductance).
Temperature in Celsius: 2B 30 32 33 31 20 34 20 00 00 02 3D 0D 0A
Temperature in Fahrendumb: 2B 30 37 33 37 20 34 20 00 00 01 3D 0D 0A

As per datasheet.

Oh, and there are excess decimal places displayed in temperature mode.

E: Okay, excess decimal places in all modes.

Can you please lock the units and decimal places to what the meter is capable of reporting? Setting it to the 1kV range and seeing 1.0000V, when the meter is incapable of that resolution, is misleading, imo.
« Last Edit: September 04, 2012, 01:11:28 pm by Monkeh »
Logged
 

Offline Mechatrommer

  • Super Contributor
  • ***
  • Posts: 11622
  • Country: my
  • reassessing directives...
Re: UltraDMM Software Project
« Reply #95 on: September 04, 2012, 01:57:04 pm »
got it! UT71A use ES51966P. can you add? pleasure to be your acquaintance! i only can find datasheet for ES51966Q (or V?) not sure if its any different...
http://www.datasheetcatalog.org/datasheets2/52/521394_1.pdf
Logged
Nature: Evolution and the Illusion of Randomness (Stephen L. Talbott): Its now indisputable that... organisms “expertise” contextualizes its genome, and its nonsense to say that these powers are under the control of the genome being contextualized - Barbara McClintock
 

Offline Monkeh

  • Super Contributor
  • ***
  • Posts: 7992
  • Country: gb
Re: UltraDMM Software Project
« Reply #96 on: September 04, 2012, 02:13:20 pm »
Quote from: Mechatrommer on September 04, 2012, 01:57:04 pm
got it! UT71A use ES51966P. can you add? pleasure to be your acquaintance! i only can find datasheet for ES51966Q (or V?) not sure if its any different...
http://www.datasheetcatalog.org/datasheets2/52/521394_1.pdf

As the datasheet says, that is an ADC. A separate processor is used.
Logged
 

Offline Mechatrommer

  • Super Contributor
  • ***
  • Posts: 11622
  • Country: my
  • reassessing directives...
Re: UltraDMM Software Project
« Reply #97 on: September 04, 2012, 04:28:03 pm »
Quote from: Monkeh on September 04, 2012, 02:13:20 pm
Quote from: Mechatrommer on September 04, 2012, 01:57:04 pm
got it! UT71A use ES51966P.
As the datasheet says, that is an ADC. A separate processor is used.
i dont see its much different from ES51922 used by UT61E the OP owns.
http://www.cyrustek.com.tw/spec/ES51922.pdf
Logged
Nature: Evolution and the Illusion of Randomness (Stephen L. Talbott): Its now indisputable that... organisms “expertise” contextualizes its genome, and its nonsense to say that these powers are under the control of the genome being contextualized - Barbara McClintock
 

Offline T4P

  • Super Contributor
  • ***
  • Posts: 3697
  • Country: sg
    • T4P
Re: UltraDMM Software Project
« Reply #98 on: September 04, 2012, 04:42:30 pm »
You know what to do ...
Trace SCLK&STATUS from pin 54&55 to the master uC
Logged
 

Offline Monkeh

  • Super Contributor
  • ***
  • Posts: 7992
  • Country: gb
Re: UltraDMM Software Project
« Reply #99 on: September 04, 2012, 04:55:51 pm »
Quote from: Mechatrommer on September 04, 2012, 04:28:03 pm
Quote from: Monkeh on September 04, 2012, 02:13:20 pm
Quote from: Mechatrommer on September 04, 2012, 01:57:04 pm
got it! UT71A use ES51966P.
As the datasheet says, that is an ADC. A separate processor is used.
i dont see its much different from ES51922 used by UT61E the OP owns.
http://www.cyrustek.com.tw/spec/ES51922.pdf

... Read the datasheet would you?

Look at the number of pins. Look at how the ES51966 has no RS232 pin, no LCD pins, etc. It's not the processor, it's just an ADC.
Logged
 
Pages: Prev 1 2 3 [4] 5 6 7 8 9 ... 11 Next  All   Go Up
« previous next »

Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf

 


EEVblog Main Site EEVblog on Youtube EEVblog on Twitter EEVblog on Facebook EEVblog on Odysee