EEVblog Electronics Community Forum
Electronics => Projects, Designs, and Technical Stuff => Topic started by: BThunderW on September 01, 2012, 07:52:44 pm
-
About a month ago I purchased a couple of Uni-Trend UT61E meters. Based on some feedback here, these seemed like decent units to have for some light EE work. Unfortunately the software that came with the meters was *lacking* so I decided to write my own.
I originally posted in this https://www.eevblog.com/forum/product-reviews-photos-and-discussion/uni-t-ut61e-multimeter-teardown-photos/msg137030/#msg137030 (https://www.eevblog.com/forum/product-reviews-photos-and-discussion/uni-t-ut61e-multimeter-teardown-photos/msg137030/#msg137030)
(http://www.ultradmm.com/images/UltraDMMSmall.png)
The full feature list of the program can be found here: http://www.ultradmm.com (http://www.ultradmm.com)
The software is mostly functional now, barring some minor bugs. What I would like to do is get a confirmation of which meters in the list work as I currently only have the UT61E.
The meters currently supported are with the ES51922 Chip and the FS9922DMM4 chip. The implementation was of course taken from documentation of the chip, so I'd really appreciate confirmation that the supported meters actually do work.
The next step is to expand the supported multimeter list so if you have a meter that you'd like to see enhanced, or even if you have a meter that works with the existing chips please post here so I can add them to the supported meters list.
I'd appreciate any feedback, good or bad, feature requests, etc.
Current version: 1.0.2 can be grabbed here: www.ultradmm.com/release/1.0.2/udmm.msi (http://www.ultradmm.com/release/1.0.2/udmm.msi)
Tom
-
In about 1 or 2 months i should be able to get myself a MS8218 and a VC8145 along with the 86E for testing as well ( I assume it's really the cyrustek chip )
This is going to be much fun ;D ;D ;D ;D
-
System.ApplicationException: Uknown Model Name
at DataReader.Reader.GetMeter(String Model, String ComPort, Int32 Baud)
at Meters.Meter..ctor(String Model, String ComPort, Int32 Baud, String Name)
at Meters.frmEditMeter.btnSave_Click(Object sender, EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Is no good.
-
Yeah. Noticed that. Will fix in a bit. Last minute change I should have tested.
Tom
System.ApplicationException: Uknown Model Name
at DataReader.Reader.GetMeter(String Model, String ComPort, Int32 Baud)
at Meters.Meter..ctor(String Model, String ComPort, Int32 Baud, String Name)
at Meters.frmEditMeter.btnSave_Click(Object sender, EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Is no good.
-
Fixed.
-
Doesn't want to listen to my FS9922 meter at all.
Can you add a debug panel to see raw data off the COM port and the specific settings?
E: Can you not cut digits off? ie. 1.0780V becoming 1.078V. It makes things hard to read when the number of digits is jumping around.
-
10 MBytes? my speed here is 45 minutes download for that. i wish i could test it for my UT71A but until i have comformal that i wont downloading java, netbean or directx17 crap that wont run in WinXP.
-
10 MBytes? my speed here is 45 minutes download for that. i wish i could test it for my UT71A but until i have comformal that i wont downloading java, netbean or directx17 crap that wont run in WinXP.
Sucks to be stuck in the 90s.
It requires .NET Framework 4.0. That's all.
-
It does have a boat load of files. Not sure why. Can't it be done with pretty much just one exe file?
-
It does have a boat load of files. Not sure why. Can't it be done with pretty much just one exe file?
Not really, seeing as those are libraries he is, apparently, using.
Infragistics is, apparently, quite huge.
-
Indeed. I can probably slim down the release by removing the unneeded libraries. I simply included the entire Infragistics library. I just haven't considered 10MB a huge release.
It does have a boat load of files. Not sure why. Can't it be done with pretty much just one exe file?
Not really, seeing as those are libraries he is, apparently, using.
Infragistics is, apparently, quite huge.
-
Indeed. I can probably slim down the release by removing the unneeded libraries. I simply included the entire Infragistics library. I just haven't considered 10MB a huge release.
It does have a boat load of files. Not sure why. Can't it be done with pretty much just one exe file?
Not really, seeing as those are libraries he is, apparently, using.
Infragistics is, apparently, quite huge.
It isn't really, but.. efficiency.
Get a new installer package, too. The compression is lacking, and having to manually uninstall to upgrade sucks.
-
Yeah. Using Visual Studio 2012 and Microsoft in their infinite wisdom remove the Setup Project from Visual Studio.
I guess for now I can just release the bug fix releases as a zip file so you can just overwrite the install files.
Sounds good?
Tom
-
Yeah. Using Visual Studio 2012 and Microsoft in their infinite wisdom remove the Setup Project from Visual Studio.
I guess for now I can just release the bug fix releases as a zip file so you can just overwrite the install files.
Sounds good?
Tom
7z please, let's have some LZMA here. ;)
-
Sucks to be stuck in the 90s.
It requires .NET Framework 4.0. That's all.
every youngs want to move to big city i prefer stay in the village, its more peaceful here. i believe net4 is not bad at all, i think i can download the update later.
-
Ok. Iterim update released
http://www.ultradmm.com/release/wip/UltraDMM.7z (http://www.ultradmm.com/release/wip/UltraDMM.7z)
Just unzip and run UltraDMM.exe. No installer with this required.
Changes:
* Added Raw Output Log, shows raw data directly from configured meter.
* Added Error logging to Application Log. Should show any issues talking to FS9922
* Trimmed trailing zeros in digital gauge
* Removed a lot of Infragistics libraries. Size of download down to ~3.7MB. Looks like it still runs for me.
* Fixed registry write error on 32Bit Windows version.
* 7Zip!
Tom
-
* Trimmed trailing zeros in digital gauge
I'm hoping you mean stopped trimming trailing zeros.
-
LOL. I guess I misread that. Give me 5 minutes :)
Tom
* Trimmed trailing zeros in digital gauge
I'm hoping you mean stopped trimming trailing zeros.
-
LOL. I guess I misread that. Give me 5 minutes :)
Tom
* Trimmed trailing zeros in digital gauge
I'm hoping you mean stopped trimming trailing zeros.
Yeah. It was already trimming, which is.. awkward to read. Maintaining the same number of digits makes it much easier to read when it's changing.
It also does that in the meter log.
-
Indeed. Updated.
Cheers,
Tom
LOL. I guess I misread that. Give me 5 minutes :)
Tom
* Trimmed trailing zeros in digital gauge
I'm hoping you mean stopped trimming trailing zeros.
Yeah. It was already trimming, which is.. awkward to read. Maintaining the same number of digits makes it much easier to read when it's changing.
It also does that in the meter log.
-
I'll take a look at it when I arrive in front of a Windows machine again tomorrow.
-
Link is bad?
-
Doh. Stupid IIS blocks unknown file extensions. Fixed.
Link is bad?
-
Doh. Stupid IIS blocks unknown file extensions. Fixed.
Link is bad?
IIS? Really?
-
Much better.
Getting timeouts on the FS9922: 2012-09-02 14:09:02 : Error: Meter 2:The operation has timed out.: at System.IO.Ports.SerialPort.ReadTo(String value)
at DataReader.FS9922DMM4._Listener()
Try bringing DTR high if you're not already.
-
Doh. Stupid IIS blocks unknown file extensions. Fixed.
Link is bad?
IIS? Really?
IIS is harder to setup but i find it more stable compared to the likes of apache ... well at least it comes free with Windows Server and 7 Ultimate
-
Doh. Stupid IIS blocks unknown file extensions. Fixed.
Link is bad?
IIS? Really?
IIS is harder to setup but i find it more stable compared to the likes of apache ... well at least it comes free with Windows Server and 7 Ultimate
Yeah, okay, sure.
-
I'm a professional windows/asp.net developer. IIS is my bread and butter :)
Tho I do run some LAMP servers too. My blog is running on CentOS/Apache/MySql.
I've already set DTR High but I changed some data/parity settings. I've updated the file. Give it a try now.
I assume RS232 is being displayed on the MM screen?
Can you connect to the MM via a serial console? If so, what connection settings are you using (Parity, Stopbits, Databits, etc)
Tom
Doh. Stupid IIS blocks unknown file extensions. Fixed.
Link is bad?
IIS? Really?
-
I'm a professional windows/asp.net developer. IIS is my bread and butter :)
My condolences. You want somewhere a little.. faster, to host UltraDMM?
I've already set DTR High but I changed some data/parity settings. I've updated the file. Give it a try now.
I assume RS232 is being displayed on the MM screen?
Still no go. Yes, I did enable it :P
It's complaining about the format now. So that's a step.
Can you connect to the MM via a serial console? If so, what connection settings are you using (Parity, Stopbits, Databits, etc)
2400 8n1.
-
Don't think you can provide anything faster than I already have. One of my clients is an enterprise hosting company (Banks, Insurance companies) and they were kind enough to let me have a rack there. My rack is connected to a 1Gbit uplink and is extremely well peered :)
"It's complaining about the format now" - Can you be more specific please?
Tom
I'm a professional windows/asp.net developer. IIS is my bread and butter :)
My condolences. You want somewhere a little.. faster, to host UltraDMM?
I've already set DTR High but I changed some data/parity settings. I've updated the file. Give it a try now.
I assume RS232 is being displayed on the MM screen?
Still no go. Yes, I did enable it :P
It's complaining about the format now. So that's a step.
Can you connect to the MM via a serial console? If so, what connection settings are you using (Parity, Stopbits, Databits, etc)
2400 8n1.
-
I've updated the program to dump the output before it attempts to process it. That way we'll at least know what it is actually seeing before throwing the exception.
-
Don't think you can provide anything faster than I already have. One of my clients is an enterprise hosting company (Banks, Insurance companies) and they were kind enough to let me have a rack there. My rack is connected to a 1Gbit uplink and is extremely well peered :)
Use it, then, because 100KB/s is depressing. :)
"It's complaining about the format now" - Can you be more specific please?
2012-09-02 16:11:58 : Error: Meter 1:Input string was not in a correct format.: at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.Byte.Parse(String s, NumberStyles style, NumberFormatInfo info)
at DataReader.FS9922DMM4.UpdateValue(String Buffer)
at DataReader.FS9922DMM4._Listener()
-
Hmm. Weird, I'm getting over 1MB/s downloading the file. I guess the peering with UK is not so good?
I can also just 7z the program without 3rd party so it'll be much smaller.
http://www.ultradmm.com/release/wip/UltraDMMPatch.7z (http://www.ultradmm.com/release/wip/UltraDMMPatch.7z)
Run this and send me the raw output if you can.
Tom
-
Hmm. Weird, I'm getting over 1MB/s downloading the file. I guess the peering with UK is not so good?
Apparently not, because I can pull 4.8MB/s from anywhere I choose except there.
Run this and send me the raw output if you can.
Not getting any raw output at all.
-
I'll check the network settings. I've recently started using Squid as a forwarding proxy on the firewall (pfSense). Wondering if that's the cause of the slowdown. Even at 1MB I should be getting faster. I have another rack at their second DC that's much faster.
I've added more error logging. Can you see if you can get some detail now?
Tom
Hmm. Weird, I'm getting over 1MB/s downloading the file. I guess the peering with UK is not so good?
Apparently not, because I can pull 4.8MB/s from anywhere I choose except there.
Run this and send me the raw output if you can.
Not getting any raw output at all.
-
Will check shortly, am looking at the raw output myself via another method.
One protocol fix: Point byte is 34 for one decimal place, not 33.
-
2012-09-02 16:57:15 : Error: Meter 1:Unknown Data: '+0000 1
It won't C+P properly. Here, have hex and nibble output for this condition (manual ranging, 3 decimal places, DCV)
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
-
Interesting. According to the document spec for FS9922DMM4, the values are supposed to be hex values separated by dashes. e.g: 2D-33-32-31-30-20-31-11-00-00-80-80-0D-0A
Is it possible your meter is different chip?
Tom
-
Interesting. According to the document spec for FS9922DMM4, the values are supposed to be hex values separated by dashes. e.g: 2D-33-32-31-30-20-31-11-00-00-80-80-0D-0A
That's just an example for easy reading, like the spaced values I provided. Raw hex would be 2B30303030203111000080000D0A
Hence the spacing. Wouldn't be 14 bytes if it had dashes would it? :)
Is it possible your meter is different chip?
Oh, it's definitely a FS9922-DMM4. I have three of them and two of the chips are fried. The protocol is the same for the FS9922-DMM3 and the FS9721-LP3.
-
Updated. Please try.
Tom
-
Support for the "RadioShack 22-812" would be great if its easily do-able. Its a solid little cheap meter, but the software for it sucks and the 3rd party apps I have tried are almost as bad so far. I dont use is near as much as I used to, but sometimes you need "just one more meter" when working on projects lol
Documentation for it is here: http://support.radioshack.com/productinfo/DocumentResults.asp?sku_id=22-812&Name=Search+Results&Reuse=N (http://support.radioshack.com/productinfo/DocumentResults.asp?sku_id=22-812&Name=Search+Results&Reuse=N)
-
did install the 7zip version. i guess the app doesnt like my UT71A which use usb to serial converter connection :(
-
did install the 7zip version. i guess the app doesnt like my UT71A which use usb to serial converter connection :(
Well what chipset is it?
-
did install the 7zip version. i guess the app doesnt like my UT71A which use usb to serial converter connection :(
Well what chipset is it?
i dont know doesnt matter, the app doesnt even show the COM1 connection in the list. keep showing JIT debugger long message.
-
Which says.. what?
-
Tom, nice work!
I have a UT70B so I wasn't sure it would hook-up so I just ran it in virtual mode.
When I saw the desktop app icon I thought the application deserved better, so I created this one for you; that's if you want it that is.
(http://tinypixels.co.uk/projects/misc/sample.png)
tinypixels.co.uk/projects/misc/UltraDMM.ico (http://tinypixels.co.uk/projects/misc/UltraDMM.ico)
I tested the app on xp and vista - I just looked around at a few things but one thing I did notice was when I did a graph, after 10-15 minutes I got a red-cross image placeholder instead of the graph, and a debug exception thrown.
Also in the graph window you have a mouse-over graph value tool-tip type thing; I just thought it would be nice to show the time offset there as well perhaps?
I must say the graph window zoom - pan controls are very small and not easy to use. From a UI perspective perhaps you could keep the main graph area as a rolling display, then underneath have the entire data capture mini-graph drawing and getting compressed etc in the width of the window. The advantage of that is you could could select areas of interest within the mini graph below by a simple click to view. You could highlight the area chosen with a red rectangle selection.
-
Downloading it now, gonna try it on my UT61E
PS. I'm getting 70KB/s on both my home computer in Romania and on a dedicated server i have in Holland. Seems like some traffic shaping on the connections.
-
Which says.. what?
my ut71a uses this cable with infrared led on the end, no direct physical contact with DMM hardware, its just detected as usb to serial converter by winxp. since its not showing up in the "create digital gauge" option when i hit continue from exception box, i guess its not supported? attached is the exception box message...
ps: i also did install and run the dmm.exe posted by B@W on the other thread which detected my DMM and reading correctly.
-
Which says.. what?
my ut71a uses this cable with infrared led on the end, no direct physical contact with DMM hardware, its just detected as usb to serial converter by winxp. since its not showing up in the "create digital gauge" option when i hit continue from exception box, i guess its not supported? attached is the exception box message...
ps: i also did install and run the dmm.exe posted by B@W on the other thread which detected my DMM and reading correctly.
You have to add the meter.
-
ok... some feedback:
windows 7 64 bit , ran from c:\programs\ultradmm , ut61e , using some serial to usb adapter (prolific clone, windows driver installed automatically)
ran for the first time the application without anything connected.
Edit meters , click on icon, defaulted to first meter model, COM 1 , 2400 baud
Close app. Plugged the serial to usb adapter, Windows installed it as COM3. Connected meter and turned it on
Start app , edit meters, click on new, now defaulted to COM3 but still first meter from menu. Does it default to last com port or it somehow detected activity on the port?
Selected UT61E and changed automatically to 19200. Clicked Test button and said "Unknown model name". After saving the meter, if I click edit, it still says unknown model name when I press on Test.
The window is bad usability wise.. when hovering over buttons it should say add, edit, delete, close ... I actually stopped and wondered if i should click on the right button with the arrow. I wasn't sure if it's "Close and use" or just close.
Add gauge > digital gauge... it's nice but not really very useful when the meter refreshes so often. I had it on volts and just touching the probes with fingers and first thing I noted is that it switches to uV, mV and V ... I hate it that it switches , I'd rather have more digits and have a fixed decimal point somewhere. Why shift my eyes left and right to chase the value? In the worst case, maybe have [ auto / uv /mv / v ] selectable option.
It would also be super useful to have a sort of value history... maybe let me see below the digit gauge, the previous 10 measurements different and ignore the readings that repeat in that list.
Graph was nice. Right when I started the window was saying with a big red text error but then the graph was drawn.
I like that the graph stops and resumes without errors if I turn off the meter and start it again. But I'd rather have the graph pause or at least throw a warning and change to proper indicators when I switch from V to mV.
When on V it works fine showing 0, -0.018v etc but when you switch to mV it now hovers at around 100-150mV depending on how I hold the probes, so the graph gets messy ... picture me doing graph of a 1.8v source and with the device turned off I see 10-20 mV then flipping to mV and scale now jumps to 200 mV - the graph doesn't make sense anymore.
When pressing to switch to Hz or % the digital gauge shows Hz or %, but the graph shows mV and pV on the scale.
Other than that, I like it that at least it clears the graph when I switch to resistance measurement but I'd probably like to be able to have several graphs on screen that pause and resume when going into the proper setting, instead of clearing the graph.
Very nice so far, I like it.
ok .. strange... turned the app off, and started the uni-t software to compare... turned it off. Started the app again and went straight to meters and clicked connect ... got an exception. Closed it before I saw what it said out of reflex, but i went to meters > edit meters and there's no saved meter there. I saved it before i closed the app the previous time. Now file > exit doesn't work, it asks if I want to save and if I say No, it doesn't close.
I said Yes, tried to save to c:\temp\a.xml and there's an error message saying requested registry access is not allowed. Second time File > Exit , Do you want to save , yes > straight to the registry error message popup. So I have to kill the process to get out.
Restart > edit meters > no meters saved... added meter again , everything works. Exit , start app, edit meters .. list gone. So meters are not saved ... maybe as its running from c:\programs\ultradmm it doesn't have rights to registry or wherever it saves the list?
-
Thanks for the feedback. A lot of the issues have been fixed in the work-in-progress version here: http://www.ultradmm.com/release/wip/UltraDMMPatch.7z (http://www.ultradmm.com/release/wip/UltraDMMPatch.7z)
It would also be super useful to have a sort of value history... maybe let me see below the digit gauge, the previous 10 measurements different and ignore the readings that repeat in that list.
There is a window under Tools called Meter Log that displays all meter activity that you can even export to Excel
I'll work on the usability issues over time.
Tom
ok... some feedback:
windows 7 64 bit , ran from c:\programs\ultradmm , ut61e , using some serial to usb adapter (prolific clone, windows driver installed automatically)
ran for the first time the application without anything connected.
Edit meters , click on icon, defaulted to first meter model, COM 1 , 2400 baud
Close app. Plugged the serial to usb adapter, Windows installed it as COM3. Connected meter and turned it on
Start app , edit meters, click on new, now defaulted to COM3 but still first meter from menu. Does it default to last com port or it somehow detected activity on the port?
Selected UT61E and changed automatically to 19200. Clicked Test button and said "Unknown model name". After saving the meter, if I click edit, it still says unknown model name when I press on Test.
The window is bad usability wise.. when hovering over buttons it should say add, edit, delete, close ... I actually stopped and wondered if i should click on the right button with the arrow. I wasn't sure if it's "Close and use" or just close.
Add gauge > digital gauge... it's nice but not really very useful when the meter refreshes so often. I had it on volts and just touching the probes with fingers and first thing I noted is that it switches to uV, mV and V ... I hate it that it switches , I'd rather have more digits and have a fixed decimal point somewhere. Why shift my eyes left and right to chase the value? In the worst case, maybe have [ auto / uv /mv / v ] selectable option.
It would also be super useful to have a sort of value history... maybe let me see below the digit gauge, the previous 10 measurements different and ignore the readings that repeat in that list.
Graph was nice. Right when I started the window was saying with a big red text error but then the graph was drawn.
I like that the graph stops and resumes without errors if I turn off the meter and start it again. But I'd rather have the graph pause or at least throw a warning and change to proper indicators when I switch from V to mV.
When on V it works fine showing 0, -0.018v etc but when you switch to mV it now hovers at around 100-150mV depending on how I hold the probes, so the graph gets messy ... picture me doing graph of a 1.8v source and with the device turned off I see 10-20 mV then flipping to mV and scale now jumps to 200 mV - the graph doesn't make sense anymore.
When pressing to switch to Hz or % the digital gauge shows Hz or %, but the graph shows mV and pV on the scale.
Other than that, I like it that at least it clears the graph when I switch to resistance measurement but I'd probably like to be able to have several graphs on screen that pause and resume when going into the proper setting, instead of clearing the graph.
Very nice so far, I like it.
ok .. strange... turned the app off, and started the uni-t software to compare... turned it off. Started the app again and went straight to meters and clicked connect ... got an exception. Closed it before I saw what it said out of reflex, but i went to meters > edit meters and there's no saved meter there. I saved it before i closed the app the previous time. Now file > exit doesn't work, it asks if I want to save and if I say No, it doesn't close.
I said Yes, tried to save to c:\temp\a.xml and there's an error message saying requested registry access is not allowed. Second time File > Exit , Do you want to save , yes > straight to the registry error message popup. So I have to kill the process to get out.
Restart > edit meters > no meters saved... added meter again , everything works. Exit , start app, edit meters .. list gone. So meters are not saved ... maybe as its running from c:\programs\ultradmm it doesn't have rights to registry or wherever it saves the list?
-
Thanks for the feedback. A lot of the issues have been fixed in the work-in-progress version here: http://www.ultradmm.com/release/wip/UltraDMMPatch.7z (http://www.ultradmm.com/release/wip/UltraDMMPatch.7z)
That hasn't been updated.
-
I meant the decimal gauge and Unknown Model's been fix in the patch.
Tom
-
I meant the decimal gauge and Unknown Model's been fix in the patch.
Tom
The file didn't change when you last asked me to try it.
-
The downloads are very slow for me too. I just assumed it was hosted on a home connection.
-
Which says.. what?
my ut71a uses this cable with infrared led on the end, no direct physical contact with DMM hardware, its just detected as usb to serial converter by winxp. since its not showing up in the "create digital gauge" option when i hit continue from exception box, i guess its not supported? attached is the exception box message...
ps: i also did install and run the dmm.exe posted by B@W on the other thread which detected my DMM and reading correctly.
You have to go into right click computer into 'manage' or computer management and look for the device manager
after that go into Ports (COM&LPT)
then assign your USB to Serial Converter as COM1 if it's there even anyway.
Just in case you don't know
did install the 7zip version. i guess the app doesnt like my UT71A which use usb to serial converter connection :(
Well what chipset is it?
i dont know doesnt matter, the app doesnt even show the COM1 connection in the list. keep showing JIT debugger long message.
Not gonna help if you don't know what chipset it uses ...
-
Which says.. what?
my ut71a uses this cable with infrared led on the end, no direct physical contact with DMM hardware, its just detected as usb to serial converter by winxp. since its not showing up in the "create digital gauge" option when i hit continue from exception box, i guess its not supported? attached is the exception box message...
ps: i also did install and run the dmm.exe posted by B@W on the other thread which detected my DMM and reading correctly.
You have to go into right click computer into 'manage' or computer management and look for the device manager
after that go into Ports (COM&LPT)
then assign your USB to Serial Converter as COM1 if it's there even anyway.
Just in case you don't know
Or you just use whatever COM port it gets assigned..
-
Which says.. what?
my ut71a uses this cable with infrared led on the end, no direct physical contact with DMM hardware, its just detected as usb to serial converter by winxp. since its not showing up in the "create digital gauge" option when i hit continue from exception box, i guess its not supported? attached is the exception box message...
ps: i also did install and run the dmm.exe posted by B@W on the other thread which detected my DMM and reading correctly.
You have to go into right click computer into 'manage' or computer management and look for the device manager
after that go into Ports (COM&LPT)
then assign your USB to Serial Converter as COM1 if it's there even anyway.
Just in case you don't know
Or you just use whatever COM port it gets assigned..
In my situation at first my USB Serial Port Emulator had to be configured it wouldn't show anything without changing it to COM1
-
Tested the patch version linked here.
Yes, the meter gets saved. Yes, the gauge is now fixed with decimals after, cool. BUT the test button still says unknown model name.
However, there's still something preventing the soft from closing properly.
Started meter, connect , show gauge, close gauge, disconnect, file > exit , no, not closing. Yes, popup saved ok, exit.
and spotted the following bug with the chart, just by switching between v and mV :
http://youtu.be/1X0qitgQ7fw (http://youtu.be/1X0qitgQ7fw)
If you pay attention at some points it also pops the "line chart error" red text at several points.
-
In my situation at first my USB Serial Port Emulator had to be configured it wouldn't show anything without changing it to COM1
That's abnormal. It should not matter.
-
I'll work on the mentioned items. Will have a new update soon. I gotta look into the web server performance issues.
Cheers,
Tom
Tested the patch version linked here.
Yes, the meter gets saved. Yes, the gauge is now fixed with decimals after, cool. BUT the test button still says unknown model name.
However, there's still something preventing the soft from closing properly.
Started meter, connect , show gauge, close gauge, disconnect, file > exit , no, not closing. Yes, popup saved ok, exit.
and spotted the following bug with the chart, just by switching between v and mV :
http://youtu.be/1X0qitgQ7fw (http://youtu.be/1X0qitgQ7fw)
If you pay attention at some points it also pops the "line chart error" red text at several points.
-
Keep up the good work Tom. Remember to take the feedback as constructive criticism. :)
I've written a few free software tools over the years and I know what it can be like. :o
-
Lol. I'm a consultant, I always deal with picky, finicky clients :)
I really do appreciate the feedback, regardless of the tone.
-
New update deployed.
Took another stab at getting FS9922 Working. Please give that a try.
Graph rewritten. The jitter/errors were due to cross-thread issues and rendering times once the graph was populated with over 150 or so values. It now only displays last 50 values and you can use the track bar to scroll to older values. This is still a work in progress, but feedback on this appreciated.
Implemented the new Icon from "jucole". Thank You!
Fixed whole bunch of small bugs.
http://www.ultradmm.com/release/wip/UltraDMMPatch.7z (http://www.ultradmm.com/release/wip/UltraDMMPatch.7z)
Regarding the server slowness, I'll contact the data center tomorrow to see if we can figure out what the issue is.
Cheers,
Tom
-
2012-09-03 21:23:07 : Error: Meter 1:Insufficient Data: '+3474 41
It would help a lot to be able to see the code.
-
"+3474 41" is not what the meter is expecting. Is it not showing the values in the raw output?
I have no idea what format that is, as this is not what is documented in the spec. It's expecting something like "2B30303030203111000080000D0A".
From Document:
13.12 RS232 Output Format
2D-30-30-30-30-20-31-11-00-00-80-80-0D-0A
(my code will accept either dashes, spaces or no spaces)
Tom
-
"+3474 41" is not what the meter is expecting. Is it not showing the values in the raw output?
I have no idea what format that is, as this is not what is documented in the spec. It's expecting something like "2B30303030203111000080000D0A".
Tom
That is what I'm seeing in the app log and the raw log.
I gave you a sample of actual meter output up a few posts, in spaced hex and nibble format. The output is, with the exception of one small difference in the decimal place byte, as in the datasheet.
There are no spaces or dashes in the actual data. They are only present in the datasheet and the output I provided to make it easy to read. The output is to be interpreted as hex, it is not ASCII data displaying hex values.
-
Nice, test button works now, the icon is a checkbox which sends the message "ok" to me, so it's all good.
The only things that bug me are just cosmetics more or less at this point:
* tooltips when hovering over buttons
* would love to have a statusbar / resize gliph on the corner of the graph window - feels like I might accidentally click on the button when I try to resize window
* when selecting add graph, if there's a single meter added, maybe it should default on pre-selecting that meter instead of me having to keep doing 2 clicks do open the combo box and select the only meter.
* those black arrows seem maybe a bit too thick in the graph window but it may just be a personal taste.
other notes
* when changing the graph from voltage to resistance or capacitance, the graph continues on and shows on the left MV when on resistance and pV when on Capacitance (as i keep the probes in air it's the default 70ish pF)
* what's the point of the alerts window if it's constantly minimized there and doing nothing ?
*shouldn't raw log actually output the bytes in hexadecimal or something like that? it seems it outputs two numbers ? It's not really "raw" if you pre-process it
-
I got this from you:
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.1
I assumed the first line was the actual plaintext output.
I think I got it now. Try this:
http://www.ultradmm.com/release/wip/UltraDMMPatch.7z (http://www.ultradmm.com/release/wip/UltraDMMPatch.7z)
Tom
"+3474 41" is not what the meter is expecting. Is it not showing the values in the raw output?
I have no idea what format that is, as this is not what is documented in the spec. It's expecting something like "2B30303030203111000080000D0A".
Tom
That is what I'm seeing in the app log and the raw log.
I gave you a sample of actual meter output up a few posts, in spaced hex and nibble format.
-
I got this from you:
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.1
I assumed the first line was the actual plaintext output.
Yeah, it's not text, it's 14-byte hex.
No difference.
-
Still working on usability issues.
Raw output is just that. There's no processing on it. What are you seeing? Can you post screenshot.
Tom
Nice, test button works now, the icon is a checkbox which sends the message "ok" to me, so it's all good.
The only things that bug me are just cosmetics more or less at this point:
* tooltips when hovering over buttons
* would love to have a statusbar / resize gliph on the corner of the graph window - feels like I might accidentally click on the button when I try to resize window
* when selecting add graph, if there's a single meter added, maybe it should default on pre-selecting that meter instead of me having to keep doing 2 clicks do open the combo box and select the only meter.
* those black arrows seem maybe a bit too thick in the graph window but it may just be a personal taste.
other notes
* when changing the graph from voltage to resistance or capacitance, the graph continues on and shows on the left MV when on resistance and pV when on Capacitance (as i keep the probes in air it's the default 70ish pF)
* what's the point of the alerts window if it's constantly minimized there and doing nothing ?
*shouldn't raw log actually output the bytes in hexadecimal or something like that? it seems it outputs two numbers ? It's not really "raw" if you pre-process it
-
(http://monkeh.net/Raw.png)
That's not raw, that's being interpreted as ASCII by something.
-
Ok. Obviously there's something more being sent than what my code is expecting. Unless I actually get my hands on actual output from the meter, I'll have to get the meter in question myself and try it on my own.
Here's a chunk of code that's processing this:
char[] bytes;
if (buf.Length == 14)
bytes = buf.ToCharArray();
else
throw new ApplicationException(String.Format("Insufficient Data: '{0}'", buf));
Sing = Convert.ToByte(bytes[0]);
Data1 = Convert.ToByte(bytes[1]);
Data2 = Convert.ToByte(bytes[2]);
Data3 = Convert.ToByte(bytes[3]);
Data4 = Convert.ToByte(bytes[4]);
Point = Convert.ToByte(bytes[6]);
SB1 = Convert.ToByte(bytes[7]);
SB2 = Convert.ToByte(bytes[8]);
SB3 = Convert.ToByte(bytes[9]);
SB4 = Convert.ToByte(bytes[10]);
Tom
I got this from you:
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.1
I assumed the first line was the actual plaintext output.
Yeah, it's not text, it's 14-byte hex.
No difference.
-
It's definitely raw. I simply add the buffer contents to the listbox control. My guess is that the listbox control converts it to ascii.
(http://monkeh.net/Raw.png)
That's not raw, that's being interpreted as ASCII by something.
-
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
-
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
-
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:?.
-
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.
-
Patch released: http://www.ultradmm.com/release/wip/UltraDMMPatch.7z (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
-
Actually, that's exactly what the meter returns. I see the same output via serial console.
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.
-
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.
-
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
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.
-
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.
-
I have an older meter that uses the ES51986 chip
http://www.cyrustek.com.tw/spec/ES51986.pdf (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)
-
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
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.
-
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
I have an older meter that uses the ES51986 chip
http://www.cyrustek.com.tw/spec/ES51986.pdf (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)
-
It's an "APPA 71"
http://www.appatech.com/upload/download/file113039186215566.pdf (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.
-
Maybe this will help :
http://flashingleds.wordpress.com/2010/11/30/unlocking-rs232-output-from-your-multimeter/ (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/ (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 (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 (http://www.mtoussaint.de/qtdmm.html)
-
Patch released: http://www.ultradmm.com/release/wip/UltraDMMPatch.7z (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.
-
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 (http://www.ultradmm.com/release/wip/UltraDMMPatch.7z)
Tom
-
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
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.
-
Thanks for the feedback. Will implement shortly. I really gotta find the cause of the fail-to-close issue.
Tom
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
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.
-
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 (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
-
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
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
-
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
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.
-
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 (http://www.datasheetcatalog.org/datasheets2/52/521394_1.pdf)
-
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 (http://www.datasheetcatalog.org/datasheets2/52/521394_1.pdf)
As the datasheet says, that is an ADC. A separate processor is used.
-
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 (http://www.cyrustek.com.tw/spec/ES51922.pdf)
-
You know what to do ...
Trace SCLK&STATUS from pin 54&55 to the master uC
-
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 (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.
-
its very hard to get to the other side of the board, its stuck on its probe lead, maybe next time i have to unsolder those. iirc no other main mcu around, if its easier, i can just simply provide the photo, i'll surrender for now :(
-
Yes, give us photos.
-
New Update: http://www.ultradmm.com/release/wip/UltraDMMPatch.7z (http://www.ultradmm.com/release/wip/UltraDMMPatch.7z)
Added ES51978 (ISO-Tech IDM 98II)
Fixed ranging for ES51986
Fixes for FS9922DMM4
Hopefully squashed the no-exit bug, could never reproduce it.
Cheers,
Tom
-
New Update: http://www.ultradmm.com/release/wip/UltraDMMPatch.7z (http://www.ultradmm.com/release/wip/UltraDMMPatch.7z)
Checked on new version with APPA 71
Out by 10 display bug = confirmed FIXED
Unhanded exception with no meter setup = confirmed FIXED.
Application close bug = Still happening
(However i noticed that if i click "Yes" you get the saved successfully popup then it quits fine when you click ok.
It seems the close bug only occurs when you click "no" to saving).
Bugs still to be fixed
- Continuity/diode range
2.4 kV displayed when open circuit (meter is showing OL)
0-6.000V jumping around when shorted (meter is showing 0.00)
NOTE:
Is there supposed to be a minimized client window at the bottom of the main form called "Alerts"
It can be expanded to a white window but cannot be closed.
-
Can you detail the exact steps to reproduce the fail-to-exit?
Tom
New Update: http://www.ultradmm.com/release/wip/UltraDMMPatch.7z (http://www.ultradmm.com/release/wip/UltraDMMPatch.7z)
Checked on new version with APPA 71
Out by 10 display bug = confirmed FIXED
Close bug = Still happening
(However i noticed that if i click "Yes" you get the saved successfully popup then it quits fine when you click ok.
It seems the close bug only occurs when you click "no" to saving).
Unhanded exception bug with no meter setup = confirmed FIXED.
Bugs still to be fixed
- Continuity/diode range
2.4 kV displayed when open circuit (meter is showing OL)
0-6.000V jumping around when shorted (meter is showing 0.00)
-
Sure,
(Assuming you have one APPA 71 meter setup in the application before launching)
Step 1
Launch application
Step 2
Click Meter
Click Connect
Step 3
Click Meters
Click Add Gauges
Click Digital meter
Step 4
Select "Meter 1" in the meter1 drop down box
(everything else is grayed out except)
- combined meter values (unticked)
- Value (set to value)
Click Accept
A value will be displayed on the digital meter, for this example it is 0.0000V DC (matches meter)
Step 5
Click the close X on the digital meter
Click "Yes" to the confimation
Step 6
Click the UltraDMM windows close X
Click "no" to the save prompt
Bug reproduced
At this point the save confirmation dialog disappears but the app does not close.
You can continue to use the application and everything works as normal. (except it wont close unless you click "Yes" to saving)
Side Note:]/b]
I just tried to do the same as above except also show the "raw output" log so i could copy the data out for you however when i try this it always closes fine.
Something about showing the raw log seems to fix the problem
Further investigation shows the bug only occurs when the only window in UltraDMM is that minimized "alert" window bottom left of the app.
-
Side Note:
I just tried to do the same as above except also show the "raw output" log so i could copy the data out for you however when i try this it always closes fine.
Something about showing the raw log seems to fix the problem
Could it be some silent exception (in closing the raw log) is causing the exit procedure to not complete?
-
Could it be some silent exception (in closing the raw log) is causing the exit procedure to not complete?
Its not just the raw output window, showing other windows seem to fix the problem too, like the application log and meter log.
I think it has something to do with that minimized "alert" window bottom left.
I noticed that just after clicking "no" to saving (when the app should close) that "alert" window gets focus back.
With any other windows showing, like the meter log, it gets focus instead and the app closes fine.
I suspect its to do with the alert window because if you try and maximize the alert window and click its close X it doesn't close but instead minimizes back to the bottom left. (its close event is blocked)
So maybe if the alert window gets focus when the app tries to exits the application close event is being blocked by this window (since we know it blocks its own close events).
The reason clicking "yes" works to quit maybe directly because of the 'save confirmation' popup which you don't get for "no". It would add an extra window in the mix which may mean the alert window doesn't handle the app close event.
-
This is gonna drive me nuts. I can't reproduce this at all. Tried it on 4 machines already. I'll add some more code to perhaps fix the issue.
Tom
-
I can make a video of it happening, if that would help?
-
No worries. I think I might have found the problem. Will include in the next update.
Can you send me a raw dump of data for:
Continuity/diode range
2.4 kV displayed when open circuit (meter is showing OL)
0-6.000V jumping around when shorted (meter is showing 0.00)
The alerts window is where Trigger Alerts are being displayed. It is not meant to be closed. But will close when application is exiting.
Tom
Does anyone else get this close bug? or is it just me?
I can make a video of it happening, if that would help?
-
Can you send me a raw dump of data for:
Continuity/diode range
2.4 kV displayed when open circuit (meter is showing OL)
0-6.000V jumping around when shorted (meter is showing 0.00)
Note: On my meter the diode/continuity serial update rate is much faster, it seems like 10hz instead of 1hz
however ultraDMM doesn't seem to mind this and just displays data at the fast rate.
When the meter is showing 0.00V (The ultraDMM whole number jumps around by a few volts eg 0.0000 and 3.0000, decimal data (0000) doesn't change)
30-30-30-30-30-31-3A-30-30-0A
30-30-30-30-31-31-3A-30-30-0A
30-30-30-30-32-31-3A-30-30-0A
When the meter is showing OL (UltraDMM 2.4kV)
30-32-34-30-34-31-39-30-30-0A
30-32-34-30-35-31-39-30-30-0A
30-32-34-30-33-31-39-30-30-0A
30-32-34-30-32-31-39-30-30-0A
When the meter has a diode across it with ~0.51 showing (UltraDMM shows ~510V)
30-30-35-30-38-31-38-30-30-0A
30-30-35-30-37-31-38-30-30-0A
Seems to be out by 1000 on diode range as 2.4kV/1000 = 2.4V which would make sense for a diode range.
I guess 2.4V should be shown as OL
-
New update: http://www.ultradmm.com/release/wip/UltraDMMPatch.7z (http://www.ultradmm.com/release/wip/UltraDMMPatch.7z)
Changed Logic. OL/UL no longer cause updates. Gauges will show Overload/Underload. Graph will stop updating until the condition is cleared.
Diode ranging fixed.
*Sigh* - No-Exit Issue hopefully fixed.
Tom
Any other meter requests?
-
I tried UltraDMM and it works (sort of) ... I cannot connect to the UT61E meter (via Uni-T UT-D04 USB cable), and I get the same shutdown hangs.
So, plugged in the USB cable (with meter turned on and measuring values. USB Input Device drivers installed by Win 7 Pro SP1 64-Bit.
Installed the Uni-T UT61E v 4.01 software that came with the meter and it runs ok. Press 'USB Connection' button and results are shown that agree with the meter. Press 'USB Disconnect' button and results display stops but are not cleared from screen. Press 'Quit' button and get popup 'Are you sure you want to quit this application?'. Press 'Yes' button and application shuts down.
Installed UltraDMM from UltraDMM.7z and applied latest posted UltraDMMPatch.7z.
Started UltraDMM. Application opens...
By the way... in windows registry HKEY_CURRENT_USER a key is created 'UltimateDMM\Program\LastPath' that holds the name of the XML save file when you Save on Exit. (I thought this program was UltraDMM?)
Now, how do I add the USB meter? I can't seem to be able to actually connect to the meter and get any output data... (It's not listed under a COM port but Device manager shows it as a HID USB Input Device.
Meters .. Connect turns round circle with red dot in it to a round circle with a red square in it. Then Meters .. Edit meters .. Add
This does list a number of meters out and specifies COM Ports but no USB option... Pressing 'Test' button returns a 'No Data' popup after about six seconds. Yes it's plugged in and sending data, verified with Uni-T UT61E software.
Sorry, but I must have missed some crucial step but I cannot find mention of it in this thread.
Any chance you could let me see the light?
Thanks
-
Unfortunately. The USB meters that currently present themselves to the computer as a HID device are not currently supported. I need to get my hands on one so I can write a proper interface for it.
I have a few meters coming in the mail that I want to add but I can't justify buying every meter just so I can get it working :) I contacted Uni-T for some test units but got no response so far.
Originally the program was supposed to be called UltimateDMM, but I changed my mind, after I already registered the domain btw. http://www.ultimatedmm.com (http://www.ultimatedmm.com) points to http://www.ultradmm.com (http://www.ultradmm.com)
Tom
-
Yeah, sorry to report the refusal to quit is back with this version in my case.
As for suggestions, is there a way to detect that the meter is discharging a capacitor? Right now it seems it's either detected as overload or there's no data sent by the chip.... I'm not sure if some bits are sent through serial...
To get the meter to discharge, just get a capacitor (i used a 3300uF/6.3v) and measure resistance for a few seconds. Then change to capacitance and the meter should say on it DiSC until capacitor goes below a threshold.
-
Oh for crying-out-loud. What the heck is causing that.....I've tried it on 4 different machines and still can't reproduce it.
-
Oh... Sad for me as your program looked really really good...
Will just have to suck it with the Uni-T supplied software for the UT61E connected via Uni-T UT-D04 USB cable meanwhile.
I understand about the name change.. these things happen, just thought you might like to 'adjust' things when you're next in the neighbourhood...
But still thanks..
-
So far, it looks like it only refuses to close after opening the graph or the digital gauge
It closes fine with raw output open or closed, with just connecting to meter or connecting and disconnecting. I'd say test and make sure those objects are killed when closing the graph and gauge windows.
-
This 'Exit' problem... Windows permissions perhaps?
I seem to be getting it, even without actually getting any data from the meter (USB), when exiting with no gauges showing and 'Alerts' open or minimised. But 'Run as Administrator' did not exhibit the same problem. Now I have UltraDMM installed in 'Program Files (x86)\UltraDMM' just for wickedness...
-
Oh... Sad for me as your program looked really really good...
Will just have to suck it with the Uni-T supplied software for the UT61E connected via Uni-T UT-D04 USB cable meanwhile.
I understand about the name change.. these things happen, just thought you might like to 'adjust' things when you're next in the neighbourhood...
But still thanks..
You got the USB cable by default? Lucky you!
-
So far, it looks like it only refuses to close after opening the graph or the digital gauge
na, not just digital, analog does it too. (at least 1 version ago, ive not tried the latest yet)
Just for testing, add a confirmation box for the "no" button when saving (like the yes button has)
I would be interested to see if this bypasses the bug.
Oh for crying-out-loud. What the heck is causing that.....I've tried it on 4 different machines and still can't reproduce it.
When you test it on another PC. Install the msi from page 1 and then copy the lasted patch files into the folder.
(As this is what we're doing)
If you copy your development folder over you may be getting files newer/extra files to what we have.
-
T4P, no unfortunately not that lucky, I ordered the USB cable as a separate item when I purchased the UT61E knowing it came with a RS232 cable... which my lappy has no interest in. Now I see I am still out in the cold, as they say, at least as far as UltraDMM., and, yes, the Uni-T software does leave something.., well a lot really, to be desired. I will wait in eager antici......pation of UltraDMM's USB support.
-
I'm going to set up a clean VM just to test this. It is driving me nuts.
When you test it on another PC. Install the msi from page 1 and then copy the lasted patch files into the folder.
(As this is what we're doing)
If you copy your development folder over you may be getting files newer/extra files to what we have.
-
I'm going to set up a clean VM just to test this. It is driving me nuts.
Sounds like a good plan!; have you thought adding a bug reporting system onto your site; sometimes it helps keep track of feature requests and bugs etc.
-
yeah. all work in progress.
Tom
I'm going to set up a clean VM just to test this. It is driving me nuts.
Sounds like a good plan!; have you thought adding a bug reporting system onto your site; sometimes it helps keep track of feature requests and bugs etc.
-
Could anyone with the no-exit bug install .Net 4.5 from here: http://go.microsoft.com/?linkid=9810134 (http://go.microsoft.com/?linkid=9810134)
I'm wondering now if they changed something as all my dev boxes have .net 4.5 installed as I'm doing dev in VS2012 which installs as a prerequisite
Tom
-
Hi
I cant run the program, it says missing assembly 'CommonForms'. It's not in the install directory.
I took the latest version installer from your downloads folder just then.
Is this open source by any chance?
-
Download the patch linked here. Just noticed that the file somehow magically got removed from the install package. Advanced Installer my A$$.
Hi
I cant run the program, it says missing assembly 'CommonForms'. It's not in the install directory.
I took the latest version installer from your downloads folder just then.
Is this open source by any chance?
-
Could anyone with the no-exit bug install .Net 4.5 from here: http://go.microsoft.com/?linkid=9810134 (http://go.microsoft.com/?linkid=9810134)
I'm wondering now if they changed something as all my dev boxes have .net 4.5 installed as I'm doing dev in VS2012 which installs as a prerequisite
According to MS, net 4.5 isn't supported by Win XP , only Vista sp2 or later
http://msdn.microsoft.com/en-us/library/8z6watww%28v=vs.110%29.aspx (http://msdn.microsoft.com/en-us/library/8z6watww%28v=vs.110%29.aspx)
-
Just my 2c
I think it's your own bug or in one of the libraries, I doubt that the no exit bug is due to the framework version.
Is your app multithreaded? Probably.
If it is it may be an exception when stopping the threads.
-
Could anyone with the no-exit bug install .Net 4.5 from here: http://go.microsoft.com/?linkid=9810134 (http://go.microsoft.com/?linkid=9810134)
I'm wondering now if they changed something as all my dev boxes have .net 4.5 installed as I'm doing dev in VS2012 which installs as a prerequisite
Just downloaded the .NET 4.5 web bootstrapper from here (http://msdn.microsoft.com/en-us/library/5a4x27ek.aspx) and let it download & install.
I cant seem to trigger the exit bug any more, it closes as it should
So it may very well be a .NET version issue.
We need someone else to confirm.
-
I never said it was a bug in framework. But MS does change how things execute from one framework to another. I have an app that was built on framework 1.1 and even though it runs with framework 4.0 installed it's extremely buggy. When I install framework 1.1 the app works fine.
That's why I suspected that they changed something in 4.5.
Tom
Just my 2c
I think it's your own bug or in one of the libraries, I doubt that the no exit bug is due to the framework version.
Is your app multithreaded? Probably.
If it is it may be an exception when stopping the threads.
-
Just a quick update on the project.
Working on adding in-process update into the app so patches will apply auto-magically and whole bunch of tweaks and bug fixed.
The web server uplink should be fixed, so downloading patches should be much quicker. There were port errors on the uplink switch.
Tom
-
Hi Tom,
Thanks for your great work! I've sent you a PM. Have a look. Thanks.
-
Hi there,
I just tried to submit the following message through the contact form on the ultradmm.com web site, but I got an error with submitting the form: There was an error sending the email. Please try again later.
Just to let you know about a bug - I just tried to do an export from the DMM log and it failed with an error:
Xml type "List of xdt:untypedAtomic" does not support a conversion from Clr type DBNull' to Clr type 'String'.
I suspect that this was because one of the lines in the log showed an overload condition.
If you need any further information or help with reproducing this bug, please let me know!
Thanks for creating this program - it definitely is an improvement over the program that came with my UT61E!
-
Thanks for the heads up. I got a new version coming soon. Just going through some testing. Will have a release soon.
Tom
-
Sounds good!
A few suggestions for consideration:
Is it possible to add some way to reset statistics (e.g. average, minimum, maximum) without having to restart the program?
Also, it would be nice if the graphs could be manually set to a specific minimum and maximum range and to also be able to specify the amount of time that they should display as a maximum - including up to the whole time that the program has been running.
-
Yup. No problem.
Tom
-
A couple more things:
Setting up an alert, I enabled the option for the sound to be looped while the trigger was active. When the trigger became active, the sound played as expected but when the trigger became inactive, the sound continued playing. Editing the alert, I noticed that the option to look wasn't showing as checked - setting it, saving and then going back in showed that it wasn't remembering the setting. Meanwhile, the sound is still playing, so it looks like I'll have to shut down the program to stop it...
-
Thanks for the feedback. Will be fixed in next release.
-
version 1.0.4 Beta
+ Added USB Support
+ Added Support for DigiTek DT-9602R+ (FS9922DMM4)
+ Added Support for Prokit's MT-1802 (FS9922DMM4) - USB/Serial
+ Added Support for Mastech MS8250C (ES51968 Clone) (Currently Testing)
+ Added Clear Meter Log Option
+ Added Reset Meters screen. Reset Min/Max/Avg on Individual or All Meters
+ Added Manual Ranging for Chart Graph
* Fix Export to Excel error
* Fix Edit Meter screen error
* Fix Looping Alert Sound Problem
* Better error handling on dropped USB-COM port
Patch Here: http://www.ultradmm.com/release/wip/UltraDMMPatch.zip (http://www.ultradmm.com/release/wip/UltraDMMPatch.zip)
Just unzip contents into UltraDMM install directory.
Tom
-
Thanks for the update - unfortunately it has broken the program completely for me:
Whenever I now try to start UltraDMM, it comes up with a message:
UltraDMM has stopped working
A problem caused the program to stop working correctly. Please close the program.
The only option is a button to close the program.
Let me know if you need any help with working out what's going wrong. I'm running Windows 7 SP1 64 bit.
-
Can you try again? I suspect I uploaded the wrong, older zip file.
-
OK, thanks for that.
I'll have to wait a few hours before I can try it now - I did a repair with 1.03 and I'm currently running a discharge test on a battery. I'll post back once I've tested it!
-
That works better! Thanks for all of the additions!
A couple more things:
It looks like the delta value has the wrong sign - i.e. it shows a negative value as voltage increases.
Is it possible for the graphs to show all values since monitoring started? I had requested this before, but maybe you missed it, or I've missed how to enable the option. This would be handy to see a whole graph of voltage under load when discharging a battery. Of course, I can export the data and graph it in Excel, but it would be nice to be able to see it in real time.
Sorry to keep asking for so much, and thanks again for creating this program!
-
Unfortunately charting the graph becomes increasingly slower as times goes on. After few minutes it takes several seconds to re-render the chart due to the many data points. Rendering this much data in real time just isn't possible at this time.
I can add a small adjustable range to increase it to but it won't be a much larger improvement than what it is now.
Tom
-
BThunderW, Thank you for providing the software.
I also think markgriffiths' "show all data" ( or on screen zoom/unzoom ) request is a good feature to have. If the display speed is the problem, I think preprocessing the data ("data compression" or other LOD constructs) before sending data for plotting can resolve the problem.
The preprocessing can be done either dynamically (per plot refreshing) or statically (storing LOD). After all, the amount of data points needs to be plotted does not need to be much more than the horizontal resolution of the plot window. Then, I am assuming your code does not have speed problem at, say, plotting 1k or so data points.
A way to do this is: For each horizontal pixel value of the plot window, calc/store/plot only the max and min data points in the original data points that compressed to this location.
-
Part of the problem is the graphing is done by a Third Party library which is somewhat limited. At this point, I can add this request to the wish list but I'm not going to tackle that right now as the bottom slider still allows you to visualize the entire length of the sampled data and you can still export the raw data to Excel for analysis.
I'll look at averaging out the data at some point in the near future though.
Tom
-
OK, no worries - I get where you're coming from - if you can add it to the TODO list, that would still be good!
Yet another thing:
The delta value appears to have a couple of problems: Firstly, I think it's showing the wrong sign - i.e. it shows a negative value when the measure voltage is rising. The other thing is that it's being shown with a heap more decimal places than it should. e.g. a value of 0.001 is often being shown as something like 0.00099999946
Sorry to be picky - this isn't actually something that worries me too much, but it might annoy others more, so might be something to look at when you're not busy...
-
Just a quick update. The UNI-T UD-D04 USB cable came in today so I'll be adding USB support for the USB UNI-T meters soon.
-
Realtime graphing with lots of data points is very hairy.
The trick is to preserve the graph history as an image, rather then as a dataset. That way, each graph update is just an image operation (adding an additional row of pixels to plot too), and an alpha composition (adding the new data).
Adjusting the scaling would either require completely regenerating the image, or a simple image transformation. The former would be pixel-perfect, but extremely CPU intensive. The later would be very cheap, from a CPU perspective, but you wouldn't be able to zoom in on the data, as it's pixel-based, not the raw data.
-
Ugh. Ran into an issue with the cable. Just like the Victor USB cable, the data is scrambled and it'll take some time to reverse engineer. I really have no idea why the do this on the USB cables since the meter transmits the data in plain text and it's non issue on serial cables.
-
Have you looked at the sigrok project ? They have a library that abstracts the interface towards a multitude of test gear including many different dmm. Http://Www.sigrok.org (http://Http://Www.sigrok.org)
There is also qtdmm2 doing something similar to this project http://www.mtoussaint.de/cdmm/doc/index.html (http://www.mtoussaint.de/cdmm/doc/index.html)
-
Ok guys. I'm really stuck with this UT-04 cable. I got the data decoded no problem. The unresolved issue is that in order for the cable to properly send data to UltraDMM, it requires some sort of command sent to it. The official UT61E program sends something to the device to cause it start sending data. My program will only properly receive data AFTER the official program has been ran.
Still trying to figure out what that command is.
-
Ok guys. I'm really stuck with this UT-04 cable. I got the data decoded no problem. The unresolved issue is that in order for the cable to properly send data to UltraDMM, it requires some sort of command sent to it. The official UT61E program sends something to the device to cause it start sending data. My program will only properly receive data AFTER the official program has been ran.
Still trying to figure out what that command is.
Since it's a USB device, why not just use USBPcap with Wireshark to capture everything from a session with the official program and have a look for the mystery packet.
-
Interesting. Didn't occur to me that you can intercept Host to device USB communication. I'll check it out. Thanks.
-
Yep, works a treat... And it's free.
-
Been some while since there was any activity here in this thread...
Is there any news yet on the usb cable and when it will be supported? :)
Thanks for your work so far i like the looks of this far more then uni-t software!
-
Haven't really made much progress on the USB front, will see if I can take another stab at it. In the meantime I got a request to implement another chipset so will be releasing an updated version soon.
-
Cool, you're still around :)
I had the opportunity to use UltraDMM again because the Uni-T software kept crashing after 30 minutes on an old system... an old laptop (ibm t40, single core centrino 1.5 ghz, 2 gb memory, 40gb ide hdd)
It worked fine, at least the part that I used (I don't remember if the graphs worked or if I tested them).
Maybe you can add some options when exporting, for example exporting to csv or tab delimited text.
If you have to stick with just xml, maybe add some option to split log in < 65535 records files (and have those files numbered incrementally).
I recently did some measurements and the xml file wasn't imported correctly by libre office so i had to install an old copy of office 2003 just to convert the file to csv or tab delimited data. But excel in office 2003 crapped out after 65535 records so i had to manually cut the xml in several smaller xml files.
Also, when I was trying to export the data, the export kept aborting with an error message saying the grid view has changed - I think this happens because the laptop hard drive was slow and while writing the large file, enough new records were accumulating to change the gridview on screen.
I had to pull out the optical receiver from the meter to get the export finalized.
If it would help with such situations, it would be nice to be able to choose the columns I want to be exported (in the hope that smaller xml file = faster save to disk = no abort or errors.
Oh yeah. Between measurements I also tried to prevent that problem with the error, by exporting the log once I thought the size would reach around 50 MB.
However, even though the results are cleared from the screen/grid in the meter log using the button, they still remain in memory because after several hours when I tried to do another export, this export had the results in the gridview AND the previous batch of records I cleared.
I guess these issues are not so obvious on modern systems that run fast but who knows, maybe if you have time you can improve on these.
The fail export due to grid change may be worth looking into, especially as people could start to use multiple meters with multiple readings per second gathering in the log, changing the gridview.
-
I will add the option to export to CSV along side exporting to Excel. Will also fix the error when exporting large files.
Additionally, I made some progress getting the USB cable to talk. Should have a working implementation of the USB UT61-E very soon.
-
Depending on how you code the export, regional settings may screw up the csv file (some countries use "," instead of "." for numbers or to group digits for ex 12,345.67) - maybe tab separated would be better, more compatible. They're supported by both Excel and Libre Office and I don't think there's a chance to get a tab accidentally in the column data.
And exporting to Excel (if you mean something different than the current xml).. i won't care but hopefully it won't add dependencies to existing office libraries.
But really anything is better than nothing, and thank you for adding something.
-
Anyone want to take the latest version out for a spin?
+ Added USB support for UT61E (and untested UT71)
+ Tab Delimited File Export
Fixed few minor bugs
http://www.ultradmm.com/release/wip/UltraDMMPatch.zip (http://www.ultradmm.com/release/wip/UltraDMMPatch.zip)
Just unzip over existing installation
Feedback would be greatly appreciated.
Cheers,
Tom
-
Anyone want to take the latest version out for a spin?
+ Added USB support for UT61E (and untested UT71)
...
Feedback would be greatly appreciated.
Awesome - I just got one of these with the USB cable! I'll have a play around with it at the weekend.
Anthony
-
Thanks for your hard work but is it possible to turn usb mode on to the ut-61d too i assume they use same protocol too? because i have the FS9922-DMM4 chip in the voltcraft vc-850 i tried your update and my meter isn't yet supported but don't hurry take your time! :)
Thanks a lot !
-
Assuming it uses the same cable as the UT61E, it'll be very easy to add support. Stay tuned.
-
Yes you are right its the same cable so i thought like it wouldn't be that hard to get the rest of uni-t meters with fs9922-dmm4 mine uses the ut-d04 cable :)
Just wanted to say thanks for your hard work i can't believe that uni-t and all the other rebadged brands dont take the time to do a real software...
-
Anyone want to take the latest version out for a spin?
+ Added USB support for UT61E (and untested UT71)
+ Tab Delimited File Export
Fixed few minor bugs
Feedback would be greatly appreciated.
I tried this out briefly. I found that when I added gauges, only the first one I added (the digital gauge) worked. I had to save the workspace and restart the software for the others to work. Once I did that, it seemed to be fine,. but I didn't play around with it for long.
If you unplug the USB cable while the software is running, it crashes.
Thanks
Anthony
-
I was willing to try it out with a UT71D, but the application doesn't load under windows 7.
Perhaps some missing files.
-
There's no error? Does the previous version load for you?
-
First version worked, the patch corrupts something.
Can you link the full program without a patch?
-
Updated: http://www.ultradmm.com/release/wip/UltraDMMPatch.zip (http://www.ultradmm.com/release/wip/UltraDMMPatch.zip)
This patch includes all binaries.
Fixed Multiple Gauge per meter Bug
Added USB support for UT71 Series (needs testing, don't have this meter)
Fixed USB Disconnect crash
-
The program loads now, but it doesn't see the 71D meter. I checked that the 71D works fine on the Uni-T software.
-
Any chance you can confirm that the UT71D uses ES51922 chip and the cable is the same as UT61E?
You should have this device in your Device Manager / USB Input Device list
(http://i.imgur.com/ANlGdVa.png)
The program loads now, but it doesn't see the 71D meter. I checked that the 71D works fine on the Uni-T software.
-
Tried this latest version on the slow laptop.
Gauges, graphs, digital they all work.
Thanks for the export TDV button, it works. Though if I clear the log and wait a bit and then hit export tdv again, the new file will also have the cleared records. You probably didn't touch this as I didn't see it mention above.
Basically the bug would be "clear log only clears the grid in the meters log but not the records in memory?" I wonder if you clear the memory, it would also affect the graphs display... don't know how you designed the app internally.
question.. say i have two meters added in ultradmm, how do i connect to just one? Right now i use "Meters> Connect" but i suspect if i have two meters it will try to connect to both?
I added a meter on another com port (nothing actually there) and when I hit connect I don't get any alert or timeout message from second meter, how would a user know if the software actually tries to connect/read values from both or not? Am I doing something wrong?
I was about to complain about time in csv exporting to mm/dd/yyyy h:m:s AM/PM ... but then i realized i had regional settings on US. Set them to my country and now it displays dd.mm.yyyy hh:mm:ss so it's all good.
-
No, the 71D has the Cyrustek ES51966.
Tried the software with the 71B also, to no avail.
The 61E didn't come with a USB cable.
The 61E is not seen either, using the 71D USB cable.
-
Looks like I was given incorrect information regarding the chipset. ES51966 is not implemented.
It also looks like the cable that comes with the UT71 is also different. Unfortunately, this will make it impossible for me to implement as I can't justify spending that kind of coin on a meter just for development purposes.
-
You're right about the clear issue, missed that one. Will fix in next patch.
If you just want to use one meter, you need to create a new Workspace. The meters are saved with the workspace so you configure whatever meters your current project requires.
Tried this latest version on the slow laptop.
Gauges, graphs, digital they all work.
Thanks for the export TDV button, it works. Though if I clear the log and wait a bit and then hit export tdv again, the new file will also have the cleared records. You probably didn't touch this as I didn't see it mention above.
Basically the bug would be "clear log only clears the grid in the meters log but not the records in memory?" I wonder if you clear the memory, it would also affect the graphs display... don't know how you designed the app internally.
question.. say i have two meters added in ultradmm, how do i connect to just one? Right now i use "Meters> Connect" but i suspect if i have two meters it will try to connect to both?
I added a meter on another com port (nothing actually there) and when I hit connect I don't get any alert or timeout message from second meter, how would a user know if the software actually tries to connect/read values from both or not? Am I doing something wrong?
I was about to complain about time in csv exporting to mm/dd/yyyy h:m:s AM/PM ... but then i realized i had regional settings on US. Set them to my country and now it displays dd.mm.yyyy hh:mm:ss so it's all good.
-
So tried your last patch with uni-t ut61d i can select usb but when i do i get some errors back...
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at DataReader.FS9922DMM4._OpenPort()
at DataReader.DMMBase.Open()
at Meters.Meter.Start()
at Meters.MeterManager.ToggleOnline()
at Meters.MeterManager.set_Enabled(Boolean value)
at UltraDMM2.frmMDI.ToggleMeters(Boolean enable)
at UltraDMM2.frmMDI.MetersEnableStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.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.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
UltraDMM
Assembly Version: 1.0.4.24575
Win32 Version: 1.0.4.24575
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/UltraDMM.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
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.1 built by: RTMRel
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.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
TriggersUI
Assembly Version: 1.0.4.24574
Win32 Version: 1.0.4.24574
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/TriggersUI.DLL
----------------------------------------
Infragistics4.Win.Misc.v12.1
Assembly Version: 12.1.20121.2082
Win32 Version: 12.1.20121.2082
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Infragistics4.Win.Misc.v12.1.DLL
----------------------------------------
Infragistics4.Win.v12.1
Assembly Version: 12.1.20121.2082
Win32 Version: 12.1.20121.2082
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Infragistics4.Win.v12.1.DLL
----------------------------------------
Infragistics4.Shared.v12.1
Assembly Version: 12.1.20121.2082
Win32 Version: 12.1.20121.2082
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Infragistics4.Shared.v12.1.DLL
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
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.4.28124
Win32 Version: 1.0.4.28124
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Utils.DLL
----------------------------------------
Triggers
Assembly Version: 1.0.4.24574
Win32 Version: 1.0.4.24574
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Triggers.DLL
----------------------------------------
Meters
Assembly Version: 1.0.4.24573
Win32 Version: 1.0.4.24573
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Meters.DLL
----------------------------------------
CommonForms
Assembly Version: 1.0.4.24574
Win32 Version: 1.0.4.24574
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/CommonForms.DLL
----------------------------------------
DataReader
Assembly Version: 1.0.4.24573
Win32 Version: 1.0.4.24573
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/DataReader.DLL
----------------------------------------
THCUtils
Assembly Version: 1.0.5160.28124
Win32 Version: 1.0.*
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/THCUtils.DLL
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
Gauges
Assembly Version: 1.0.4.24574
Win32 Version: 1.0.4.24574
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Gauges.DLL
----------------------------------------
HidSharp
Assembly Version: 1.5.0.0
Win32 Version: 1.5.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/HidSharp.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.
Couldn't see anything happening in the raw output either but thanks for your work so far!
-
I emailed you Tom.
Seems like when you set it to usb under the ut61d but after saving it when you reopen then it is unticked...
-
Yeah, will check it out.
-
First of all, thank you for the software. :-+ It's a great improvement compared to the original Uni-T software.
The software is working well to me except that I cannot exit the software: when I want to quit he prompt me If I want to save the log file, but if I choose "no" the software doesn't quit.
Even saving doesn't solve the issue, since I got an error that tells me that "the registry key didn't have the right write permissions".
My system: genuine Windows XP SP3 with all patches available from Windows Update and the latest .NET and other requirements. UT61E via RS-232 to USB.
Hope this helps to improve your excellent software.
-
If you know what registry key it is you can go into regedit and change permissions on it, should work i had some issues with keys that where locked.
-
I'll be releasing a new version soon. In the meantime, try running the app as an Administrator.
-
I'll be releasing a new version soon. In the meantime, try running the app as an Administrator.
Thank you, I will try asap.
If you know what registry key it is you can go into regedit and change permissions on it, should work i had some issues with keys that where locked.
Unfortunately the error did not specify wich registry key is locked :-//
-
Sorry guys, been busy with work. Will try to release an update this week. hang tight.
-
No problems mate :)
Take your time...
-
I'm not sure if you talked about resolving download issues earlier, but I just downloaded the file in a few (3-4) seconds. I have Verizon FiOS (50/25) and am in the north east US. So, speed here is fine.
Any luck getting this working for a Fluke? a 189 specifically. The FlukeView Form software isn't really a DMM insterface.
-
My USB cable for the UT-61E arrived yesterday so I tried it with UltraDMM last night - very nice, considerably better that UNI-T's software.
I was reminded of Dave's review of the Agilent 34461A (EEVblog #489) specifically the long-term trend analysis it can do. Since the meter is now connected to a PC we have effectively unlimited sample memory so the graph could be used to show long term trends rather than the a moving window.
So my suggestions for enhancements:
- Unlimited (or configurable) sample window
- Option to configure the x-axis labels (the full date/time string is quite long)
- Configurable window colours.
Looking forward to the new release (although I had no problems with the current patched version)
Pete
-
So how are things coming along?
Shall be really nice to use your software as i so hate the uni-t/voltcraft one :)
-
http://www.ultradmm.com/release/wip/UltraDMMPatch.zip (http://www.ultradmm.com/release/wip/UltraDMMPatch.zip)
- Added support for Digitek DT-4000ZC and Tekpower TP4000ZC (Thanks grbolet, first user contributed code!)
- Changed date format on graph to display time only
- Some bug fixes / code clean up
- Fixed USB disconnect crash
Give it a shot and let me know how it works. I still have to set up a test environment to figure out the exit bug. I will have some down time coming from work so I'll get that done.
-
Tried the update and used the uni-t ut61d i can select usb but it still give me the same errors.
When i add the device and tick usb then ill get this:
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at DataReader.FS9922DMM4._OpenPort()
at DataReader.DMMBase.Open()
at Meters.Meter.Start()
at Meters.MeterManager.ToggleOnline()
at Meters.MeterManager.set_Enabled(Boolean value)
at UltraDMM2.frmMDI.ToggleMeters(Boolean enable)
at UltraDMM2.frmMDI.MetersEnableStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.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.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
UltraDMM
Assembly Version: 1.0.4.18373
Win32 Version: 1.0.4.18373
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/UltraDMM.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
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.1 built by: RTMRel
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.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
TriggersUI
Assembly Version: 1.0.4.17847
Win32 Version: 1.0.4.17847
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/TriggersUI.DLL
----------------------------------------
Infragistics4.Win.Misc.v12.1
Assembly Version: 12.1.20121.2082
Win32 Version: 12.1.20121.2082
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Infragistics4.Win.Misc.v12.1.DLL
----------------------------------------
Infragistics4.Win.v12.1
Assembly Version: 12.1.20121.2082
Win32 Version: 12.1.20121.2082
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Infragistics4.Win.v12.1.DLL
----------------------------------------
Infragistics4.Shared.v12.1
Assembly Version: 12.1.20121.2082
Win32 Version: 12.1.20121.2082
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Infragistics4.Shared.v12.1.DLL
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
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.4.17846
Win32 Version: 1.0.4.17846
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Utils.DLL
----------------------------------------
Triggers
Assembly Version: 1.0.4.17846
Win32 Version: 1.0.4.17846
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Triggers.DLL
----------------------------------------
Meters
Assembly Version: 1.0.4.17846
Win32 Version: 1.0.4.17846
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Meters.DLL
----------------------------------------
CommonForms
Assembly Version: 1.0.4.18373
Win32 Version: 1.0.4.18373
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/CommonForms.DLL
----------------------------------------
DataReader
Assembly Version: 1.0.4.17846
Win32 Version: 1.0.4.17846
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/DataReader.DLL
----------------------------------------
THCUtils
Assembly Version: 1.0.5202.17846
Win32 Version: 1.0.*
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/THCUtils.DLL
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
Gauges
Assembly Version: 1.0.4.18373
Win32 Version: 1.0.4.18373
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Gauges.DLL
----------------------------------------
HidSharp
Assembly Version: 1.5.0.0
Win32 Version: 1.5.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/HidSharp.DLL
----------------------------------------
Infragistics4.Win.UltraWinGauge.v12.1
Assembly Version: 12.1.20121.2082
Win32 Version: 12.1.20121.2082
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Infragistics4.Win.UltraWinGauge.v12.1.DLL
----------------------------------------
CommonControls
Assembly Version: 1.0.4.17846
Win32 Version: 1.0.4.17846
CodeBase: file:///C:/Program%20Files%20(x86)/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.
And when i open the settings up the second time the usb is unticked but its ticked?
See included screenshot :)
But thanks for your update!
-
Can you PM me a copy of your workspace file? What operating system are you running? Are you experiencing this with a blank workspace or an existing one?
Tried the update and used the uni-t ut61d i can select usb but it still give me the same errors.
When i add the device and tick usb then ill get this:
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at DataReader.FS9922DMM4._OpenPort()
at DataReader.DMMBase.Open()
at Meters.Meter.Start()
at Meters.MeterManager.ToggleOnline()
at Meters.MeterManager.set_Enabled(Boolean value)
at UltraDMM2.frmMDI.ToggleMeters(Boolean enable)
at UltraDMM2.frmMDI.MetersEnableStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.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.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
UltraDMM
Assembly Version: 1.0.4.18373
Win32 Version: 1.0.4.18373
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/UltraDMM.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
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.1 built by: RTMRel
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.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
TriggersUI
Assembly Version: 1.0.4.17847
Win32 Version: 1.0.4.17847
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/TriggersUI.DLL
----------------------------------------
Infragistics4.Win.Misc.v12.1
Assembly Version: 12.1.20121.2082
Win32 Version: 12.1.20121.2082
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Infragistics4.Win.Misc.v12.1.DLL
----------------------------------------
Infragistics4.Win.v12.1
Assembly Version: 12.1.20121.2082
Win32 Version: 12.1.20121.2082
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Infragistics4.Win.v12.1.DLL
----------------------------------------
Infragistics4.Shared.v12.1
Assembly Version: 12.1.20121.2082
Win32 Version: 12.1.20121.2082
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Infragistics4.Shared.v12.1.DLL
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
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.4.17846
Win32 Version: 1.0.4.17846
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Utils.DLL
----------------------------------------
Triggers
Assembly Version: 1.0.4.17846
Win32 Version: 1.0.4.17846
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Triggers.DLL
----------------------------------------
Meters
Assembly Version: 1.0.4.17846
Win32 Version: 1.0.4.17846
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Meters.DLL
----------------------------------------
CommonForms
Assembly Version: 1.0.4.18373
Win32 Version: 1.0.4.18373
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/CommonForms.DLL
----------------------------------------
DataReader
Assembly Version: 1.0.4.17846
Win32 Version: 1.0.4.17846
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/DataReader.DLL
----------------------------------------
THCUtils
Assembly Version: 1.0.5202.17846
Win32 Version: 1.0.*
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/THCUtils.DLL
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
Gauges
Assembly Version: 1.0.4.18373
Win32 Version: 1.0.4.18373
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Gauges.DLL
----------------------------------------
HidSharp
Assembly Version: 1.5.0.0
Win32 Version: 1.5.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/HidSharp.DLL
----------------------------------------
Infragistics4.Win.UltraWinGauge.v12.1
Assembly Version: 12.1.20121.2082
Win32 Version: 12.1.20121.2082
CodeBase: file:///C:/Program%20Files%20(x86)/UltraDMM/UltraDMM/Infragistics4.Win.UltraWinGauge.v12.1.DLL
----------------------------------------
CommonControls
Assembly Version: 1.0.4.17846
Win32 Version: 1.0.4.17846
CodeBase: file:///C:/Program%20Files%20(x86)/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.
And when i open the settings up the second time the usb is unticked but its ticked?
See included screenshot :)
But thanks for your update!
-
Ill email you some info in a moment shall try it on winxp too
-
trying to use Digitek DT-4000ZC and getting exception when adding meter after click on Save (same for tekpower, others seems to work, so I did something wrong :-))
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ApplicationException: Uknown Model Name
at DataReader.SupportedModel.GetMeter(String Model, String ComPort, Int32 Baud)
at Meters.Meter..ctor(String Model, String ComPort, Int32 Baud, String Name)
at Meters.frmEditMeter.btnSave_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
-
http://www.ultradmm.com/release/wip/UltraDMMPatch.zip (http://www.ultradmm.com/release/wip/UltraDMMPatch.zip)
Patch updated with fixes.
I'm working on adding support for multiple USB Meters from same Manufacturer.
-
That sounds perfect, i had to use the uni-t software and i so dislike it lol feels like it is slapped together by some kids not scalable and the user interface is a joke looking forward to try yours :-+
-
http://www.ultradmm.com (http://www.ultradmm.com) not work.....
-
Site is back up. I'll be doing an new official release soon.
-
On my UT-61E and 61D all works perfectly now! Thank you! :-+ :-+
-
Hi Tom, thanks for your hard work so far!
Tried your last update from april 9th this time UDMM does not give me any error messages and it seems like usb can stay ticked :)
So a bit further in the battle to produce the best open source software for multimeters.
I tried it again and i can select it as following:
<UltraDMM>
<Meters>
<Meter Name="Meter 1" Model="Uni-T UT61D" Baud="0" ComPort="USB" SmoothSamples="1" Key="%jq#tdisir" SampleDelay="0" VID="6790" PID="57352" />
</Meters>
<Windows>
<Timer Left="0" Top="0" Width="475" Height="92" WindowState="Normal" />
<Gauge Type="GRAPH" AutoRange="True" CombineFunction="ADD" CombineMeters="False" MajorTick="0" MaxValue="0" Meter1Key="%jq#tdisir" Meter1ValueType="DELTA" Meter2Key="" Meter2ValueType="VALUE" MinValue="0" MinorTick="0" ShowMax="False" ShowMin="False" Symbol="" TickFrequency="0" Top="328" Left="864" Height="431" Width="564" GraphType="LINE_GRAPH" />
</Windows>
<Triggers />
</UltraDMM>
But still i can not get any raw data from my multimeter, maybe i shouldn't expect it either until you released the final version? :)
But thanks so far Tom for your work im looking forward to get this running instead of the crappy software that comes with the meter.
-
Just Curious if you made any progress yet Tom ? :)
-
After buying a 61E, I found the UltraDMM web site and downloaded the MSI installer. Well, that was pretty buggy and I didn’t see any updates at the site. So searching around brought me here. I installed the April 10 patch files a few posts up and wow what a difference!
I’ve only experimented a few minutes but did note a few things:
The Analog meter doesn’t autorange very well. I had connected the DMM to a potentiometer measuring resistance, and while the analog meter would autorange up well, from Ohms to kOhms, it would not autorange on the way down. It stayed stuck at kOhms until I reset it.
The Excel output file treats numeric values in the raw data columns as text strings. It is possible to convert back to numbers, but importing the text file to Excel is easier. I’m not sure I see the advantage of having the Excel XML format output.
I recommend adding a link to the latest patch file on the web site.
Otherwise, looks like this will be a great tool.
Thanks
--Clay
-
What would it take to add the Fluke 289 to this program?
I have a protocol document, and I am a software engineer.
Can I do it? I noticed that another DMM was listed as contributed.
I have t he meter for testing.
-
So a bit further in the battle to produce the best open source software for multimeters.
open source? I think you meant free and maintained software. Or if this is open source then where is the source? Linux (Gnu/Linux) version with Mono would be nice.
-
So hows things coming a long with this software has the development been put on ice?
Just wonder still interested! ;)
-
Development was put on hold as I was dealing with some personal issues, plus I've received some rude emails regarding the program in the past (demanding changes, complaints, etc) that put me off development for a while. I have some more ideas to implement plus some emails that were sent had some good suggestions, look for a new version soon at http://www.ultradmm.com (http://www.ultradmm.com)
Tom
-
Nice software, quite handy.
PS I wonder how many folks here are in Toronto, and would like to get together in a Meetup?
-
So a bit further in the battle to produce the best open source software for multimeters.
open source? I think you meant free and maintained software. Or if this is open source then where is the source? Linux (Gnu/Linux) version with Mono would be nice.
I think it says somewhere that graphics are based on Infragistics package, which starts at $899... I guess dev can distribute his products.
I'm really grateful for the effort made! Kudos!
-
I understand that Tom keep your head up high this world is full of idiots and we all sometimes run into personal problems and need to deal with that first
so take your time there is a old swedish saying "those who waits for something good, never waits to long!" so take you time and f**k the rude people.
-
've received some rude emails regarding the program in the past
Quite frankly, I don't realize how things like this can even happen. I mean, it's a free software, what the hell some people have in their mind?! :palm:
-
There are a few billion people on-line. Statistically, gotta be some assholes among them.
I made a small technical database once, an overview of a niche technical product. The best of it's kind available on-line, containe about 5000 items. The web site had a few hundred visitors per day, searching on-line. I sent mails out to a dozen software developers, telling them they could download the whole database for free, just making decent acknowledgements. One guy, a professor, answered almost literately "why should I do that when I can make a scrip that rips the data it from your web site?" and got into a long argument that I can not prove if he copies my data. And continued; "in reality I have no legal possibility to sue him anyway". I'm not joking!
-
<<why should I do that when I can make a scrip that rips the data it from your web site?>>
Possible answer:
<<Well, only for courtesy. Keep in mind that only because your personal life is a total fiasco and you're have been a bully's victim for years at school it doesn't mean that you must be an asshole against every person.>>
-
:-) Pretty much what I told him. But he actually sent about 10 mails arguing his cause :palm:
I worked for 15 years at a technical university so I pretty much recognize and acknowledge what you are saying.....
-
Hi there,
First of all, big thanks to Tom for excellent software!
I have minor (but annoying) problem using it: each and every time I'm adding gauge or graph to workspace, I'm getting an Unhandled exception:
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at Infragistics.Win.Misc.UltraButton.OnLostFocus(EventArgs e)
at System.Windows.Forms.Control.WmKillFocus(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
**************
Clicking "Continue" button allows to get the things working, but I'd like to fix the problem, if possible.
Issue is reproducible on UltraDMM v1.0.5.37035 running on Windows XP x86 Professional SP3 / .NET v4.0.30319 with NDP40-KB2600211 update, and on Windows 7 x64 Enterprise SP1 / .NET v4.5.50938.
Googling reveals that such 'Object reference' errors are related to the interactions between Infragistics DLL libraries and Microsoft .NET, but I'm not sure what I can do myself in order to get rid of that exception. Infragistics hotfixes aren't available to general public, as I understand. Any ideas?
BThunderW, are you still reading this forum? :)
-
Hi Tom,
I've just purchased a UNI-T UT71D, excellent device, and I'm very happy with it. However, I have just discovered that the UT71D does not work (yet) with UltraDMM... I sort of assumed that it would as the youtube videos of the 61D showed it working.
After having read this thread, I now understand the ins and outs a bit better. I can see your point of it is not worth investing in a UT71D yourself just for development purposes. Does that mean that the UT7D is on hold? Is there anything that UT71D owners can do/provide in order to assist you and make this happen?
I provide a screen shot of my Device Manager in the hope that it may help. I notice that it has slightly different from the USB Input Device HardwareIds of Wytnucls. Not sure why that is, then again, I am not exactly sure what I am looking at or for...
I hope that you don't give up on the UT71D as it is a cracking little meter, and in conjunction with UltraDMM would make an excellent tool.
Thanks,
Testkins
-
I'm still here. I've started implementing two more chipsets (E51966, E51997F) one of which is used by the UT71D. Bear with me, my time nowadays is very limited.
Tom
-
Great! I've got one of those!
Thanks for the good work!!!
-
Looks like the ES51966 doesn't actually have serial out capability and that's handled by another chip. Does anyone have a UT71 series DMM? Having difficulty finding documentation regarding serial output and I don't have that DMM myself, which makes adding support for it quite difficult.
Tom
-
Here is what I have. These are for Conrad re-brands of the UT71X series.
-
Tom,
Do you have any comments about UltraDMM's unhandled exceptions mentioned above?
-
In what language is the software written?
And what libraries where used for the graphical stuff?
-
Looks like the ES51966 doesn't actually have serial out capability and that's handled by another chip. Does anyone have a UT71 series DMM? Having difficulty finding documentation regarding serial output and I don't have that DMM myself, which makes adding support for it quite difficult.
Tom
I've got an UT71D but no additional docs than the ones posted. Anything I can help with?
-
It's a bug in the third party library. Unfortunately the fix requires the purchase of a newer version for which I currently do not have the funds for. I will see if I can replace the control with something else that's not quite as expensive.
Tom,
Do you have any comments about UltraDMM's unhandled exceptions mentioned above?
-
Thank you! Good to know it's not my particular setup problem then. It just was a bit unclear for me, being not reported by other users nor documented.
Next question is about more DMM models to be supported in the future. Are you interested in implementing the support for Victor protocol? It's somewhat unusual (essentially, information about active LCD elements is transferred via USB link to PC, instead of actual values), but relatively popular model VC86B (FS9721 chip) uses it. The documentation is available, and support is already implemented in several non-commercial packages...
-
I can certainly give it a shot if you're interested in being a test subject. Can you dump some output for me?
Tom
Thank you! Good to know it's not my particular setup problem then. It just was a bit unclear for me, being not reported by other users nor documented.
Next question is about more DMM models to be supported in the future. Are you interested in implementing the support for Victor protocol? It's somewhat unusual (essentially, information about active LCD elements is transferred via USB link to PC, instead of actual values), but relatively popular model VC86B (FS9721 chip) uses it. The documentation is available, and support is already implemented in several non-commercial packages...
-
Great! Sure I'll be glad to provide testing. What namely dump you'd like to see? Intercepted USB traffic?
As for now, I can share some information sources already available for that range of DMMs.
Manufacturer page:
http://china-victor.com/english/en/product_data.aspx?ClassID=168&ID=125 (http://china-victor.com/english/en/product_data.aspx?ClassID=168&ID=125)
Proprietary software:
http://china-victor.com/english/en/download.aspx (http://china-victor.com/english/en/download.aspx)
Future Semiconductor FS9721_LP3 datasheet:
http://www.ic72.com/pdf_file/f/48820.pdf (http://www.ic72.com/pdf_file/f/48820.pdf)
(serial output described on page 13)
USB interface for Victor 86B Digital Multimeter using HIDAPI project:
https://code.google.com/p/victor86b-usb-interface/ (https://code.google.com/p/victor86b-usb-interface/)
(source code available)
Victor 86C multimeter USB encoding for linux:
http://www.daveansell.co.uk/?q=node/44 (http://www.daveansell.co.uk/?q=node/44)
Victor protocol pages on Sigrok project:
http://sigrok.org/wiki/Victor_protocol (http://sigrok.org/wiki/Victor_protocol)
http://sigrok.org/wiki/Victor_86C/Info (http://sigrok.org/wiki/Victor_86C/Info)
Input Devices page on RoastLogger software:
http://homepage.ntlworld.com/green_bean/coffee/roastlogger/dmmdetails.html (http://homepage.ntlworld.com/green_bean/coffee/roastlogger/dmmdetails.html)
-
Just a quick update on the project. I'm ripping out Infragistics dependency and switching to free gauge controls. Infragistics wants too much money for upgrades and I'm strapped for cash right now.
-
IMO, right way to go. Even MS charting will do! Better to get it moving even if digits only.
-
Well, some update on Victor 86B support. To my surprise, it seems that UltraDMM is already capable to handle it! I've accidentally found Russian article dated 30-05-2013 where owner of Victor 70C (http://www.china-victor.com/english/en/product_data.aspx?ClassID=168&ID=121) model reported successful experience with patched UltraDMM version:
http://mysku.ru/blog/aliexpress/16310.html (http://mysku.ru/blog/aliexpress/16310.html)
As I understand, the patch was required for previous UltraDMM version (1.0.4?) to suppor USB HID device, and now (for current 1.0.5) isn't needed anymore. For data source, Pro's Kit MT-1820 (USB) (Victor) was selected. Obvously, MT-1820 is based on the same Fortune FS9922-DMM4 chip as Victor 70C, and supplied with the same optical USB cable. Moreover, MT-1820 looks absolutely identical to the Victor 86E model, except for the colors of outer shell:
http://www.prokits.com.tw/en/product/product_detail.asp?catid=1&itemid=MT-1820 (http://www.prokits.com.tw/en/product/product_detail.asp?catid=1&itemid=MT-1820)
(http://ib4.keep4u.ru/b/2015/04/22/8a/8a4021607a44256f021db2af3c12e0d6.jpg) (http://www.china-victor.com/Files/Product/86E.jpg)
Clearly the same product from the same factory, just relabeled per customer requests.
I've tried using my Victor 86B with UltraDMM's MT-1820 driver. It "almost works": the "Test" buttom report "Success!", but measured value is always zero. Meter gauges display various modes if DMM's rotary switch is operated, and the graphs are moving/live: so, data carrier or clock from DMM is received just fine.
It seems that full support for Victor 86B requires just minor modifications of data interpretation algorithm, while most of the job (hardware support, data parsing, etc) is already done.
Hope the author will do that sometime...
-
This is a really great project!
Although reading through half the messages here, i have a question. I need to record two UT 61-E (USB). I can connect one and then receive the message, that it is not possbile to connect two devices from the same manufaturer.
- I´ve read here that this support is worked on (which is so great). Should that be working already (and i simply didn´t get it running)?
- if not, is there a workaround in using two different UNI-T models? I can still return one of them for an exchange?
I downloaded the current version 1.0.5.37035 from ultradmm.com
-
Hi Tom!
So any updates on this software and maybe the possibility to be able to use it on my Voltcraft VC 850?
It is kind of strange as i can not get any data in raw monitor?
I am using the Uni-T serial to USB cable and it shows up in the dev mgr as: "USB\VID_1A86&PID_E008&REV_1200" it was a long time ago i asked you about this i think you said something like
there is already one instance that uses the same vid/pid is there any way to get around this or do you need to rewrite the software think you did mention it before as the crappy software
from voltcraft can communicate with it then maybe soon in the future udmm could replace it? it feels 100000 times better with your layout and work.
Looking forward to being able to use udmm instead of voltcrafts own crappy version :)
-
it might be possible for you to support fluke 287/289's its a simple serial port that you send commands to the meter to get values in reply.
ID would return the meter id :)
-
(http://i.imgur.com/8mNJE9t.png)
Gauge progress...not as good looking as the Infragistics but can't argue with free.
-
Look at that https://www.devexpress.com/ (https://www.devexpress.com/) it's better like Infragistics I think :box:
-
The whole reason why I'm ripping out Infragistics is because I don't have the funds to update to the latest version in order to fix some bugs in the release that's being currently used. DevExpress is awesome but not free.
Look at that https://www.devexpress.com/ (https://www.devexpress.com/) it's better like Infragistics I think :box:
-
Keep up the good job Tom!
That last screenshot looks really nice!!
So hows things coming along with the newer version of UDMM? think you talked about that you might re-code the software to be able to support more devices and so?
Was just thinking of why can i not get a raw data output thru the vc-850 and the uni-t data cable never really understood why lol but will it help if i capture the data packets
thru the orginal software so you can see if it communicates like the uni-t ut61d right? if i remember correctly.
Anyway take your time no rush, you are doing a great job on the software :)
I really like the layout and design way more then the voltcraft shit they supplied with the meter ;)
-
Once I strip the proprietary libraries I will start working on a plug in system so that meters can be added by third parties.
Keep up the good job Tom!
That last screenshot looks really nice!!
So hows things coming along with the newer version of UDMM? think you talked about that you might re-code the software to be able to support more devices and so?
Was just thinking of why can i not get a raw data output thru the vc-850 and the uni-t data cable never really understood why lol but will it help if i capture the data packets
thru the orginal software so you can see if it communicates like the uni-t ut61d right? if i remember correctly.
Anyway take your time no rush, you are doing a great job on the software :)
I really like the layout and design way more then the voltcraft shit they supplied with the meter ;)
-
Sounds great Tom! :)
For those who waits for something awesome they can never wait to long! keep up the great work.
-
Infragistics is gone!
(http://i.imgur.com/BSHttSw.png)
Few new features are coming. Any volunteer beta testers? :)
-
I am willing when I get back home in a week but why not just post the beta and let everyone try?
-
v2.0 is a big rewrite of the core engine, needs good testing, didn't really want to post a build that could be broken.
One major feature of v2 is support for multiple USB meters of the same type. I don't have two exact meters to test it with so this is "experimental".
-
Well I am still offering. I won't be able to do anything until the 15th of May though.
-
Anyone want to give this a try?
http://www.ultradmm.com/release/wip/UltraDMM2.zip (http://www.ultradmm.com/release/wip/UltraDMM2.zip)
Specifically I need someone with two identical USB meters to test this. Just unzip and run, there's no install necessary. Also, if you have UltraDMM 1.X installed, unzip into a different folder, there will be no conflict. Once this goes live the installer will not uninstall UltraDMM 1.x and will run both concurrently.
Change List:
- Removed commercial library dependency
+ File Writer gauge
+ Custom gauge/chart colors
+ Gauges can now be resized
+ Multiple USB Meters of the same type
* Bug fixes
I will also no longer be doing over-the-email support of custom meters. If you want to have your meter supported you will have to either loan me one or chip in $$ for one. I've tried working with several people on adding support but the email turn-around time is just way too long and doesn't work with my schedule.
I've received some rude emails from people telling me to support their meters and they expect me to shell out the money for it. Unfortunately, since I don't make a penny off of this program, buying a meter for development out of my pocket is no longer an option.
Tom
-
Does this means that plans to add VC86B meter/Victor protocol support using external/volunteer testing are gone?
-
Yes. I can add support to a meter in a couple of hours when it's in my hand, takes weeks to do it over email since response time is typically very slow. I just do not have that kind of time.
V2.1 will include plugin support so that other meters can be added by other developers.
Tom
Does this means that plans to add VC86B meter/Victor protocol support using external/volunteer testing are gone?
-
I just downloaded it and attempted to run it but it doesn't start, no errors, crashes, etc - nothing. I'm at work so I don't have the meter connected (is that the problem?). This is on a new install of Windows 7 SP1 64bit fully patched, unpacked to my user directory.
Pete
-
Can you go to Event Viewer -> Windows Logs -> Application and see if there's any errors?
I just downloaded it and attempted to run it but it doesn't start, no errors, crashes, etc - nothing. I'm at work so I don't have the meter connected (is that the problem?). This is on a new install of Windows 7 SP1 64bit fully patched, unpacked to my user directory.
Pete
-
Hello.
The same here...
Win7Pro 64-bit full updated.
At first run there was an error displayed.
(See appended txt-file: Errors after first run)
Since then: UltraDMM.exe simply doesn´t start after permitting installation.
The eventvwr shows two errors.
(See appended txt-file: Errors since first run)
My eventvwr-log is unfortunatly in some parts in german.
Perhaps it is anyhow useful for you. At least I hope so.
Hartmut
-
It runs on my Win7 x64 no problems. I cannot connect to anything because all my multimeters are at home and I won't be able to really test until the 15th at least.
-
Got it. Looks like I missed one more Infragistics reference. Will post update shortly.
Hello.
The same here...
Win7Pro 64-bit full updated.
At first run there was an error displayed.
(See appended txt-file: Errors after first run)
Since then: UltraDMM.exe simply doesn´t start after permitting installation.
The eventvwr shows two errors.
(See appended txt-file: Errors since first run)
My eventvwr-log is unfortunatly in some parts in german.
Perhaps it is anyhow useful for you. At least I hope so.
Hartmut
-
Sorry for the delay, been away on a short vacay. New update available.
http://www.ultradmm.com/release/wip/UltraDMM2.zip (http://www.ultradmm.com/release/wip/UltraDMM2.zip)
Cheers,
Tom
-
Success! :clap: :clap:
The downloaded file starts without any problems direct from the unzipped folder.
Only a request for permission for executing the file appears (as expected).
No entry occured in the eventviewer.
Capturing data from an UT61E via USB works as good as in the "older" version. :-+
Two little quirks (both in the Graph Gauge):
- The time-stamps at the bottom of the graph are automatically synchronized with the PC-time.
But not in the 24h format. It´s converted to the 12h format, without indicating "am" or "pm".
- Setting the background color to black makes the measurement values (printed along the graph) invisible.
Is there anything I can do for you?
Hartmut
-
Thanks very much for the update.
I have two UT61E (USB) running and encounter the following problem:
The first one is detected and can be saved. The second one can be found ("Test function") delivers the correct value, but cannot be saved - ths usual error message appears ("two usb devices from the same.... cannot be ....").
does that help?
-
Hello.
Is this thread still of interest?
If yes: I´m now able to test with two meters.
Two UT-61E´s connected. Both with USB.
Meter1 set to show mV AC (some random stuff).
Works as expected.
Meter2 set to show Voltage of a 10V DC source.
In the "Add Meter" window it can be succesful tested.
The program can differ between the two meters and
displays the correct value.
(Look at the attached file "UDMM_testing_meter_2_Succes")
But Meter2 can´t be saved in the "Manage Meters"-part.
Suddenly can´t be differed between the two meters.
An error-message pops up.
(Look at the attached file "UDMM_saving_meter_2_Failure")
Pretty much the same as posted from zerobrain.
I´m curious if there is a solution.
Perhaps an identification with the Port# and Hub# ?
BTW: Simultanious measuring is possible.
First start the Uni-T-Software, then the UltraDMM.
(or vice versa, it doesn´t really matter.)
The first connected program will freeze the gauge and graph.
Re-connect it (the program, not the meter), that´s it.
BTW: This way it works with UltraDMM V1, too.
(Look at the attached file "UDMM_Uni-T_V4-01")
If there is more information needed, then feel free to ask.
I will answer asap.
Greetings,
Hartmut
-
I´d like to followup on the last post.
I deel very sad, that the project seems to have stopped. The "two multimeter" thing would be so great for measuring batteries!!!
There is an additional bug - maybe due to localization. The comma is not displayed in the german setup, but saved correctly to the logfile. That´s a minor issue....
If the project is abondomed - maybe the sourceocde could be released to the community?
-
Just saw this thread for the first time. Does anyone know if it runs okay on Wine on Linux?
-
Just saw this thread for the first time. Does anyone know if it runs okay on Wine on Linux?
I would prefer if the author merges airtight and push all his talent into a team of a multiplatform suite for data acquisition of Testing/Measuring/Lab equipment. It would be amazing!
-
In case someone is still reading this tread... :)
Victor VC86B meter could be used with UltraDMM even without code changes: you'll just have to use another data cable. In my case, I've replaced default USB HID cable with spare COM-port UNI-T one (type UT-D02) temporarily duct-taped to the output window. In UltraDMM settings, select "UNI-T UT-60E" and appropriate COM port: that's all.
Probably, I'll make separate DIY-cable to connect it via USB later.
-
Hi there Tom long time since this thread been active...
How is the progress on this software do you plan on some release later on that
will work with my Voltcraft VC850 same as UniT Ut61e with the same cable.
/Peter
-
Next time, avoid that .net crap and use Qt: https://www.qt.io/ (https://www.qt.io/)
-
Is this still being developed? I have some exceptions on my Windows 7 64 installation. I can click on continue and it still works, but wondered if anyone is still maintaining the code?
Cheers
Steve
-
Does anybody know weither my Victor 86E is ever going to work on my Windows 10 / Ubuntu 16.10 system?
Is the meter supported? Does anybody have a URL for the supported version.
-
The Victor 86E uses the same chip as the Uni-T UT61E.
Perhaps it is worth a try... :-//
Be aware: The first UltraDMM version needs an add-on
(somewhere hidden in this thread, not on the website)
for the data transfer via USB. Or try the "new" version
(hidden in this thread, too).
-
Sorry for necroposting
But what is actual state of UltraDMM project?
-
Next time, avoid that .net crap and use Qt: https://www.qt.io/ (https://www.qt.io/)
Show us how it's done!
-
UltraDMM 2.0.0.17498 runs on Windows 10 (x64). Virtual returns 0.000V. Have an old Metex DMM (M3850), won't respond on availables. M3850 runs on an older (9th Feb 2014) program called MScope (V1.08 build 146) via a Prolific USB to serial cable COM3 (ProlificSerial0) at 1200 bps.(single frames)
-
Interesting!
Websites states: "Update: 2020-02-14 - Project is getting revived. Expect an update in the coming weeks"
I was hopeful, but couldnt find an update download. I consider this is really dead now.
-
It's not dead. We're working on the new version, but dev pace is slow due to covid related funding issues. We're still committed to it and will have an all new version out sooner rather than later.
-
That would be great news!
As i wrote some years ago, i had serious issues with USB when using 2 UNI-Ts.