-
Is there a plan to add oscilloscopes to the list of supported devices?
-
Is there a plan to add oscilloscopes to the list of supported devices?
I do not see the point in oscilloscope support for this program.
The program is designed for "slow" logging of values, oscilloscopes are designed for sampling in the MHz range (More or less).
This program will be able to log a couple of devices for weeks (At lower sampling rates or there will be memory problems). -
A update was uploaded (V0.15), it fixes the issue with spaces in column names and a few other minor details.
-
You can still do slow logging from an oscilloscope. I think there are more oscilloscopes on hobbyist benches than benchtop multimetersIs there a plan to add oscilloscopes to the list of supported devices?
I do not see the point in oscilloscope support for this program.
The program is designed for "slow" logging of values, oscilloscopes are designed for sampling in the MHz range (More or less).
This program will be able to log a couple of devices for weeks (At lower sampling rates or there will be memory problems). -
You can still do slow logging from an oscilloscope. I think there are more oscilloscopes on hobbyist benches than benchtop multimeters
I do also support some handheld multimeters.
Next point is that I do not have that many scopes to work with, but if some people want to make configurations for logging with scopes, they are welcome. -
Got it, replaced the space with an underscore(odd limitation, usually for CSV's I pull the entire string between delimiters).
This is because the column names are variable names when you do math. I have modified it to accept spaces and then automatic replace them with _ when creating variables (New version will be uploaded later today).Still can't use the plotting for readings however. When I range limit to the min/max of real readings I get no plot just the scale, and obviously when I let it auto it's just a straight line at the top of the graph. Alternatively I'm not sure auto min. range and auto bottom step are meant to do. I feel the results I'm getting are a bit random.
When Auto is checked Minimum/Maximum is ignored.
These 3 setting is only active when auto is checked:
Auto includes zero means that auto scales will include a 0 value, this will block for seeing small changes in a large value.
Auto min. range defines the minium span that can be used on a chart (in auto), this is used to avoid amplifying noise to fill a full chart height.
Auto bottom step is the step size for the bottom of the scale (0 is legal), this can be used to make scales align.
I assumed when Auto was checked min/max did nothing. I'm not sure what changed but I was able to get it to plot the readings even setting full scale to 10uV. This wasn't the case yesterday. I'd still prefer values not be truncated though. For data sets I'd like to see every decimal point I type or that is recorded. When trying to set min/max I have to recall what the old value was when it rounds to 7.157 and I actually typed 7.15664 and need to change it to 7.15665. I'd also recommend adding a UI scale slider in config, or wherever you think is best, so that you don't have to worry about the DPI issues. Or do the math and have it scale at startup(my preferred method). Mostly looks good though. Perhaps add some hover tooltips for things which may not be obvious to those that didn't write the program. -
I assumed when Auto was checked min/max did nothing. I'm not sure what changed but I was able to get it to plot the readings even setting full scale to 10uV. This wasn't the case yesterday. I'd still prefer values not be truncated though. For data sets I'd like to see every decimal point I type or that is recorded. When trying to set min/max I have to recall what the old value was when it rounds to 7.157 and I actually typed 7.15664 and need to change it to 7.15665.
In the "scales for chart" page I used a Java default, I have changed that now to use between 0 and 8 decimals as necessary.
In table I have added a right click menu that can adjust number of decimals for each column, this will also affect range page
The new version (0.16) will probably be uploaded tomorrow.I'd also recommend adding a UI scale slider in config, or wherever you think is best, so that you don't have to worry about the DPI issues. Or do the math and have it scale at startup(my preferred method). Mostly looks good though. Perhaps add some hover tooltips for things which may not be obvious to those that didn't write the program.
I am missing some scaling depending on font size, I believe everything else scales fairly well.
-
On my 17" 4k monitor scaling is good. On my 28" 4k monitor... Not so much.
-
On my 17" 4k monitor scaling is good. On my 28" 4k monitor... Not so much.
At first glance I would say scaling looks fairly on the posted image (Command line could be better). -
Well if that's what you were going for then I guess it's not a problem.
-
Well if that's what you were going for then I guess it's not a problem.
I would prefer font size is adjusted depending on DPI and that the useful areas get larger when possible.
But for now the software cannot handle changing font size very well.
-
HKJ,
You mention that you added Siglent SDM3045X but I do not see it in the device list. I have a SDM3065X and I was going to see if it works for it.
Thanks
Mike -
HKJ,
You mention that you added Siglent SDM3045X but I do not see it in the device list. I have a SDM3065X and I was going to see if it works for it.
I forgot to copy the file to the zip file, it will be included in the next update. -
Logging stalled twice after 18 minutes and after 26 minutes. Had to use the task manager to exit the prog. loosing all (test)data. Now changed to a laptop. Same prob. there stalling after 16 minutes. When stalled, changing from chart to histogram and back is slow as molasses. Needing some 30 s or so each time. Hitting save a takes ages until the "Save chart" windows appears. In the mean time the chart was actually updated after 4 further minutes while waiting for the program allowing me to enter file name. When stalled, Java task is running at some 30 % processor capacity.
Computers: AMDFX-4100 running W10 32 bit and AMD A10-7300 running W10 64 bit with all the latest updates Java at Version 8 Update 241. -
What devices where you logging from, a lost connection to a device could stall it.
-
Logging a 34465A via LAN. Other logging progs including my own one based on Profilab, work without any problems with the 34465A. Seems to be a Java specific problem.
Windows logs the following error message upon stalling:
Protokollname: Application
Quelle: Application Hang
Datum: 31.03.2020 08:48:08
Ereignis-ID: 1002
Aufgabenkategorie:(101)
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: PC52
Beschreibung:
Das Programm javaw.exe Version 8.0.2410.7 hat die Interaktion mit Windows beendet und wurde geschlossen. Überprüfen Sie den Problemverlauf in der Systemsteuerung "Sicherheit und Wartung", um nach weiteren Informationen zum Problem zu suchen.
Prozess-ID: ab8
Startzeit: 01d60720f5ecd6aa
Beendigungszeit: 4294967295
Anwendungspfad: C:\Program Files\Common Files\Oracle\Java\javapath_target_11213328\javaw.exe
Bericht-ID: 4ae8df29-68f3-4fd9-8113-e739342920fc
Vollständiger Name des fehlerhaften Pakets:
Relative Anwendungs-ID des fehlerhaften Pakets:
Absturztyp: Top level window is idle
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Hang" />
<EventID Qualifiers="0">1002</EventID>
<Level>2</Level>
<Task>101</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-03-31T06:48:08.544016500Z" />
<EventRecordID>14354</EventRecordID>
<Channel>Application</Channel>
<Computer>PC52</Computer>
<Security />
</System>
<EventData>
<Data>javaw.exe</Data>
<Data>8.0.2410.7</Data>
<Data>ab8</Data>
<Data>01d60720f5ecd6aa</Data>
<Data>4294967295</Data>
<Data>C:\Program Files\Common Files\Oracle\Java\javapath_target_11213328\javaw.exe</Data>
<Data>4ae8df29-68f3-4fd9-8113-e739342920fc</Data>
<Data>
</Data>
<Data>
</Data>
<Data>Top level window is idle</Data>
<Binary>54006F00700020006C006500760065006C002000770069006E0064006F0077002000690073002000690064006C00650000000000</Binary>
</EventData>
</Event>
-
I have not seen any problems with the 34465A, I need to do some testing.
-
One way to force the problem is to start a second instance of the program, it will steal the meter from the first instance and the first instance will lockup like you describe.
Because all instances uses the same configuration and will connect when starting, it will happen when starting a second instance. -
Running one instance on both puters. Loading the list on No.1 takes a bit. Pressing "reconnect" seems to nudge the search socket message. Anyway must leave things as they are for the moment, but will be watching this space. Thanks for your effort.
-
Running one instance on both puters. Loading the list on No.1 takes a bit. Pressing "reconnect" seems to nudge the search socket message. Anyway must leave things as they are for the moment, but will be watching this space. Thanks for your effort.
Any device that tries to connect to the 34465A while logging will freeze the program, this will not happen from the next update. -
Still at it.
Relaxed the logging interval a bit
from 1 s to 10 s. Now at 40 minutes and still going strong.
-
Just tried the program on my OSX system, with a Keysight 34465 and so far looks good
-
Still at it.
Relaxed the logging interval a bit
from 1 s to 10 s. Now at 40 minutes and still going strong.
With another Java program I have been logging from Keysight meters (Mostly 34461A) for weeks and never seen a problem, always with about 1 second logging interval. -
Next version is up (V0.16), changes are:
Logging will add a entry at 0 seconds
On "Scales for chart" page the auto checkbox will change visible settings and they can show many more decimals now.
In the table page it is possible to right click and adjust decimals for a column, this will also affect the range page.
Missing data 5 times in a row from a socket device will close the connection, not hang the program.
Scalable fonts, this still has a few issues, slider on configuration page.
The /h slope option now work. -
Last version had a serious problem, it locked up and could use a lot of memory and CPU.
This is hopefully fixed now, I did a trial run with the 3 virtual generators and 0.01 second logging interval with the chart page visible, my CPU usage was 3% (This include everything running on the computer).
I have also fixed a lot of details that occurred due to the scaleable fonts.
The version is 0.17.
If this version works without serious problems it will be some time before I upload a new version again.
If people make definition for some other SCPI equipment I am very interested in a copy of the file to include with the software, use the #author" tag to add credit to the about page.