Excel and OpenOffice Calc choke on just two data channels of 130K data points- and that doesn't even include generating the x-axis data (time of each sample). Handling a file of 20 or 30, or more such traces would be, well, unthinkable. I know what a macro is - at one time I wrote quite a few of them in Excel VBA, but that required a "functioning" application... The Excel VBA macro recorder helped a lot with my weaknesses at scripting. As yet, I'm unfamiliar with the Open Office VBA equivalent.
Hello Rick,
I can see a desire for "deep data" in order to catch high speed transients, glitches, and the like; ... My desire is to do repetitive data captures of side by side data in a single file in performing a series of tests for later analysis ... Excel and OpenOffice Calc choke on just two data channels of 130K data points- and that doesn't even include generating the x-axis data (time of each sample) ...
Thanks again,
Plummerman
7. Function declaration:
HTMARCH_API unsigned short dsoSetCalLevel(unsigned short DeviceIndex,short* level,short
nLen);
Return value: return zero (0) for success and non-zero for failure.
//Calibration error state
bool CalibrateError=false;
//Attempt to calibrate device
if(!Scope->Calibrate())
{
//Attempt to Store Calibration Data to device
if(Scope->SetCalLevel())
{
//Set Error Flag
CalibrateError = true;
}
}
//Otherwise there was an error
else
{
//Reset Calibration Data
Scope->GetCalLevel();
//Set Error Flag
CalibrateError = true;
}
__int16 __usercall sub_41AE50<ax>(int a1<esi>)
{
__int16 v1; // bx@1
__int16 result; // ax@2
__int16 *v3; // [sp-1Ch] [bp-24h]@1
//Calibrate, set v1 to success/fail
v1 = dsoCalibrate(
*(_WORD *)(a1 + 48), // DeviceIndex
*(_WORD *)(a1 + 56), // nTimeDIV
*(_WORD *)(a1 +, // CH1VoltDIV
*(_WORD *)(a1 + 32), // CH2VoltDIV
(__int16 *)(a1 + 110)); // pCalLevel
v3 = (__int16 *)(a1 + 110);
//Failure
if ( v1 )
{
dsoGetCalLevel(*(_WORD *)(a1 + 48), v3, 32);
result = v1;
}
//Success
else
{
dsoSetCalLevel(*(_WORD *)(a1 + 48), v3, 32);
result = 0;
}
//Return status
return result;
}
Hello everyone, I think I figured out the Calibration problem...
The calibration utility is running correctly now, but if one runs it while erroneously connected to the internal reference output, the amplitude of the waveform doubles and then it fails and gives an error. I would expect it to fail, but not affect any settings?
If one loads a reference waveform from the R menu, there is no way to disable it again, except closing and restarting the program. Maybe a Close option would be helpful.
The full screen option with the Esc button works well, but the small icon on the left, using restore, removes the full screen, but then its without the menus.
Are you planning to include the "AUTOSET" feature that is used when probe compensation is done?
Probe Compensation
Perform this function to match the characteristics of the probe and the channel input. This should be performed whenever attaching a probe to any input channel at the first time.
? From the “Probe” menu, select attenuation to 1:10. Set the switch to “X10” on the probe and connect it to CH1 of the oscilloscope. When using the probe hook-tip, insert the tip onto the probe firmly to ensure a proper connection.
? Attach the probe tip to the Probe Compensator and the reference lead to the ground connector, select CH1, and then press the “AUTOSET“ button into the menu or the toolbar.
? Check the shape of the displayed waveform.
The Esc key and the Right click menu takes me back to the window mode correctly, but the small icon definitely takes me back to a window mode, but with the difference that only the graticule with grid and wave form shows, no upper toolbar or right hand knobs etc. are displayed then.
Autoset feature: The Hantek software has an Auto setup blue button in the toolbar, 4th from the right.
Latest Binary: http://jmp.sh/v/QN9DEKEgv4YQEW056ASq
....
Issue 1:
I have problem getting either Math or Reference to scale. Can you share with us how it is suppose to be scaling? I am seeing very inconsistent scaling and even with many experiments, I can't even determine what might be the scaling logic with math. (Follow Ch1? Follow Ch2? Average Ch1+CH2? Follow Ch1 by a multiplier factor? etc...)
Suggestion 1 - why not make it manually scalable? A lot more flexible if user can select scaling base on what is being investigated. At the wave-position pointer, the right-mouse click drop down to hide the Ref/Math trace could have another entry to open a pop-up to get scaling info.
Issue 2:
Detaching toolbar causes display to be erratic. It is certainly not a big issue unless it points to a larger problem (since trace-drawing seem to slow down after a few times of doing that). It was hard to reproduce, but I mapped out a sure way to see it:
1. Reboot (if not rebooted, it may not show after a while but seem to slow down trace drawing)
2. Hook up to scope's reference wave
3. Start Open6022BE
4. Set trigger to get stable trace (I set it to ~500mv)
5. Resize window to a bit longer than the tool bar and a bit wider (It may not happen unless both width and height are changed)
6. Drag toolbar outside the window you will see the traces for both channel blinking.
7. Resizing the window again, the traces now draws normal - you can move toolbar anywhere without blink except the default position (below main window's drop down menus). If you move it back to the default position it will blink again.
8. It will repeat: Resize window again and blink stop, move toolbar out and it starts... It seems to plot slower after a while, but it may just seem to do that instead of for real. Mind may play trick after looking at the same thing for a long time.
Issue 3:
Interestingly, when I Remote Desk Top into the machine running the scope with both Ch1 and Ch2, only Ch2 is showing. The grid and Ch1 do not show at all. When I have both Math and Reference wave on, grid,Ch1,Ch2,Math are absent but Reference wave is visible.
Suggestion 2:
Would it be feasible to implement scroll bar in the control area? I use a small machine with 1024x768 resolution to fit my work area. When measurement windows are open, Ch2 controls are no longer visible.
Suggestion 3:
For measurement window, would it be feasible to split the screen horizontal instead of vertical? Displaying Ch2 data below Ch1 takes too much screen real-estate and the measurement data display is not wide. If Ch1 and Ch2 are split horizontally, it will not take up so much screen.
One additional bug:
The V/Div setting for both channels have a glitch (regardless of other settings as far as i have tested it):
V/Div (set) V/Div (active)
10/V 10V
5V 5V
2V 2V
1V 1V
500mV 1V
200mV 1V
100mV 1V
50mV 500mV
20mv 200mV
Issue 3:
Interestingly, when I Remote Desk Top into the machine running the scope with both Ch1 and Ch2, only Ch2 is showing. The grid and Ch1 do not show at all. When I have both Math and Reference wave on, grid,Ch1,Ch2,Math are absent but Reference wave is visible.
I have no idea what would be causing that... I have tested with VNC Viewer and it appears fine, so it's probably an issue with the software you are using... Perhaps some kind of setting for reducing unnecessary traffic?
Suggestion 2:
Would it be feasible to implement scroll bar in the control area? I use a small machine with 1024x768 resolution to fit my work area. When measurement windows are open, Ch2 controls are no longer visible.
I'll see what I can do, but at the moment it looks like it might be a more complicated feat than one would imagine...
Suggestion 3:
For measurement window, would it be feasible to split the screen horizontal instead of vertical? Displaying Ch2 data below Ch1 takes too much screen real-estate and the measurement data display is not wide. If Ch1 and Ch2 are split horizontally, it will not take up so much screen.
I was thinking the same thing and I have already implemented for the next release a segmented view (see attachment) using four TreeView controls (one for each measure source) side by side. The way the stock software does it is a massive waste of space, and it just looks wrong.
Btw, if anyone was wondering, if you double click the measurement list it will invert the current selections, so if nothing is selected, it will select all items.
Arrgh, not critical, but would be nice.