-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sept 2019 Improvements #18
Comments
Martin, the version on my phone and tablet is 136. (I do not see it being marked beta.) |
Google Tests in progress, it should be available soon... |
Test findings Hscope version 2.2.1 (137) Only mentioning issues that are not (completely) solved / changed Single trigger & Unlock: looks at level in stead of edge. Single trigger dirty samples at the beginning --> Issue found when Experimental Mode is ON. Should be fixed in V.138 Pan & zoom --> Cannot be replicated, provide sequence of buttons used to arrive to this condition. Probably the Y screen is already zoomed to maximum. Correct, when started at minimal zoom, scale -6 <> +6V, vertical positioning is 'locked'. With any other scale zoom can start immediately. Scale on the voltage meter is misaligned. --> Info Panel report screen size and Density, please take a screenshot from V.138 Settings page. If for example I want to change 'Samples interpolation', I can't click that word, I need to click 'Linear' at the far right. With a thick finger I can easily click the line above or below. Also the drop downs are still small and therefore error prone. For both, a larger font or more space between the lines can help. Or ... since the number of choices in the drop down table is never more than 4, maybe it could be radio buttons or tick boxes which are always in view? --> Enlarged text in drop down menu in V.138. Need to test 'Zoom to Fit' icon only zooms vertical --> In most of cases you want to navigate on a custom zoom in X and enlarge to fit just along Y. Fit according X has no sense since you can have 2 signals at difference frequency, so which one you would like to fit automatically? 'Auto' button. --> This is a cool feature to consider... |
Has anything been done on 'Auto' button feature? On IDSO1070A stock app delivered by hantek, this is included and I am heavily using this. It is not pleasant to switch between 2 apps, just to use AUTO at stock one and the goto back to Hscope. |
Zero Level Calibration
The pop up window says:
2) Sconnect the probe or shortcut to GND. This should probably read 'Disconnect'. Maybe it is even better to leave disconnect out and always advise to connect to GND.
--> Updated in V.137
Positioning channel 2: green arrow is hidden
When activating channel 2, the green arrow to change position is hidden behind the sidebar tab. It is hard to get hold of it. See image ‘Channel2_Positioning_1’.
Possible solution:
Move the sidebar tab further to the top.
Or, don’t have a sidebar tab at all, sidebar is opened and closed by swiping.
--> Channel 2 arrow moved on left side.
Positioning channel 2: can’t grab the green arrow when it is at the bottom
I somehow managed to get the situation like in image ‘Channel2_Positioning_2’.
I was not able to grab the green arrow to move the signal … adding a purple cursor has priority.
--> New priority: Trigger, Channel 2, Cursors
Single trigger & Unlock: looks at level in stead of edge
See images ‘Trigger1’ and ‘Trigger2’. Single trigger is activated, channel2, upward edge. I hoped that pressing 'Unlock' would start display when the signal has its first upward edge. What happens however is when the signal already is higher than the trigger level, display starts immediately … rendering only part of the first pulse.
Possible solution:
Looks like acquisition is activated by: IF sample > trigger THEN start.
Better would be: IF previous_sample <= trigger AND current_sample > trigger THEN start.
It also leads to the display of signal values that were not there … which is even worse when Phosphor mode is switched on … see next point.
--> Problem of dirty samples at the beginning in 6022 devices should have been fixed from V.136 BETA. Still exist in Experimental Mode.
Trigger Unlock > scale changes, strange phosphor effects
If Single trigger & Unlock is used, then initially the scale changes and shortly after the scale goes to the set values. This leads to a short screen flicker after Unlock. Moreover … when Phosphor effect is active, sometimes an artifact stays visible in this situation. See image Phosphor_Unlock_Scale.
--> Updated in V.137. Scale Y now change just on input voltage change.
Pan & zoom
When the 'Scope' button is switched off and acquisition stops, initially the display can not be dragged vertically, only horizontally. Only after a two finger pinch, or after tapping the 'Zoom to Fit' icon, the screen can be dragged vertically.
--> Cannot be replicated, provide sequence of buttons used to arrive to this condition. Probably the Y screen is already zoomed to maximum.
Scale on the voltage meter is misaligned.
See image ‘Voltage_Scale_Misaligned’.
--> Need to test again.
Demo signals are not static
The demo signals change when time scale or amplitude scale is changed. This is rather unexpected and trying out the effects of scale changes in demo mode is rather impossible.
--> Implemented in V.137. Sample signal frequency switch to lower value in Roll Mode.
NICE TO HAVE
Horizontal (voltage) cursors.
Channel1 arrow
Only channel2 has an arrow cursor. It would be nice if channel1 also has an arrow.
Trigger adjustment to a specific value
The red trigger cursor arrow is hard to position at an exact value. Say I want to set it at exactly 2.0V, or later back to 0.0V … it is very hard to do.
Possible solutions:
The same holds for the time scale cursors … it is difficult to position them at an exact sample.
Display of the sample ranges / frequencies
The character used for kilo is k … non capital.
A space between the number and the units will improve readability: 10 kHz in stead of 10KHz.
--> Updated in V.137 for all units
Mearurement results display position fluctuations
When the Measurements button is pressed the measurement results show in the neighborhood of the actual signal. While this can be handy to distinguish them with 2 channels displayed, the backside is that their position fluctuates when the signal fluctuates. An alternative cold be to have two boxes, one yellowish, one greenish, stable positioned, with the measurement results displayed in them.
Settings page.
When tapping settings, why not by default start in the General Settings in stead of Info?
The number of chapters is short enough to all be on the top level, in stead of having paragraphs under the Settings chapter.
The font could be larger ... I have a hard time to tap the correct item on my tablet.
--> Updated in V.137
Zoom resets after tapping 'Scope' button.
Starting and stopping acquisition by tapping the 'Scope' button changes the display back to 'no zoom', also after the user has just zoomed in manually, or has tapped the 'Zoom to Fit' icon. Can it stay at the current zoom setting when tapping 'Scope'?
--> Updated in V.137, Y Zoom do not change any more, just X axis is adjusted to center the trigger point, and to show WIDTH/4.
'Zoom to Fit' icon only zooms vertical
When tapping the 'Zoom to Fit' icon, only the vertical, voltage, zoom is applied. Why not also change the horizontal zoom such that, at least for a repetitious signal where a frequency can be measured, 3 periods are in view and T0 is in the middle?
Actually ... why not always automatically zoom to fit? Unless the user has zoomed by hand to his liking, then keep that zoom setting.
--> In most of cases you want to navigate on a custom zoom in X and enlarge to fit just along Y. Fit according X has no sense since you can have 2 signals at difference frequency, so which one you would like to fit automatically?
'Auto' button.
The 2 channels have an auto scale button. Could there also be an overall 'Auto' button, after which Hscope analyzes the incoming signal and automatically selects the best time scale and voltage scale?
--> This is a cool feature to consider...
The text was updated successfully, but these errors were encountered: