The saved format of waw files does not have the correct display scale. Moreover, it does not fit with time per div with short time base. I will fix it. It will take a while. Still removing some bugs found.
fixed errors, and added some new errors
v0.023m
Long time base 100ms/div to 50s/div. In the waveform view mode, the range is from 20ms to 50s/div (multiple zoom options)
Long time base uses a memory of 3000 samples per channel.
Trigger options: Normal and single with the option of setting the trigger level and type of edge. Auto free run mode, no triggered.
In the long mode, the menu of measured values is not displayed.
write notes on errors.
ok fix it 3 error. erasing the display when turning on or off the time or voltage cursor. Correction of the cursor scale time-wrong value in short base, it no longer shows GHz, Bad sampling value for 500ms 5s and 50s
v0.023n
Yesterday when I decided to use an oscilloscope to measure the switched power and I discovered the 3 errors that are removed in the 0.023n version.
Today I wanted to check the multiplexing speed of the display, and I found out that it is in the red range when set to 1V.
It will be necessary to solve the problem with the shift of the signal in DC mode.
Nothing can replace real tests
It seems that RMS measurement implemented in the version v0.006 requires some changes for the saved WAVE files. Currently it doesn't show correct value.
Possible solutions could be: save calculated RMS value with the other WAVE file settings or recalculate RMS value from the file samples after loading.
only 1 year and 1 day
fix in v0.023o
The value was not saved in the wav file, added. (rms value)
Fixed screen clearing after exiting waveview mode.
FIxed wrong frequency in autoset mode
Good afternoon! Atlan, thank you for your hard work. A bug has been found in version v0.023o. When the stopped pulse is stretched or compressed, it is reset to 0 value.
Fixed. V0.023p
The correct switching of the sampling frequency when switching from stop to run also works.
If you reduce or expand the signal in the stop, the run will be displayed in the current setting during the transition.
Another problem has been discovered, the displacement of the zero level of the beam during the transition to the ACQ long period.
Make video.
Now I am modifying the program so that it does not wait for the end of the transfer. Quite a lot of interventions in the program.
PC:
I would say that a field[730] was created for the displayed data on the display. But is it not used anywhere? Channel1pointsbuffer and 2
PC:
I would say that a field[730] was created for the displayed data on the display. But is it not used anywhere? Channel1pointsbuffer and 2
I think it was intended to be used for the wave file storage. The buffer is being filled when a channel trace is displayed on the screen. See "void scope_display_channel_trace(PCHANNELSETTINGS settings)" function in scope_functions.c, but by the looks of it that is it.
In next version firmware will is bug fixed.
hi, when i try to change the time and date, it shows ? you can't change it.
hi, when i try to change the time and date, it shows ? you can't change it.
Touch the buttons to set the time and date
The work has progressed, so hopefully there will be a new firmware release soon.
it's not working for me, when i change it, it sets hours 45 minutes 85 day 45 month 25 year 20165
when i change it, it shows 3?:7?:7?
see pictures it doesn't work.
i try with version 0.023p and its the same problem, even with version 0.019 it's not working. it keeps showing the 3?:7?:7?
the unit is new, i bought it, 3 days ago?
the unit is new, i bought it, 3 days ago?
Read the post linked above. It doesn't come with real time clock. It's a mod you have to do if you want it by adding an extra circuit and soldering it in. It doesn't work on base hardware without the mod.
okey thanks, now i understand. i will install it. thanks for the response.
It is interesting that no one complained that it still deletes the calibration data, even when it is announced that only the default data will be uploaded. FIXED
It should already work, that is, unless there are changes regarding the calibration or the location of the values on the SD card. It will not be necessary to recalibrate the input divider. You can perform the baseline calibration whenever you need.
v0.023s allows the code to run without waiting for the conversion to finish in the FPGA. This means that the time on the display is not frozen, and the T cursor and V cursor buttons work as they should.
Again, the bigger the changes in the code, the more likely it is that there will be more errors. So test it.
P.S. I did not notice a signal shift when switching from short to long mode.
I have a working manual for the firmware, but it is not finished or translated, and I don't even want to deal with it. Maybe when there is free time for that.
Another problem has been discovered, the displacement of the zero level of the beam during the transition to the ACQ long period.
Take a photo of the calibration data
Strangely, two oscilloscopes have the same level problem.
It's interesting that it doesn't make me 2 pieces. We'll see if anyone else can be found
v0.023t