Change sample rate, to increase the visible bits of the DS3231 i2c bus. The original firmware cannot do that.
Autoset works as it should!!!
This is very good. Perhaps the working area of the signal along “Y” can also be increased? Since with 8 screen cells the signal only works on 4 cells, which is not very good.
The same signal AC+DC on different firmware:
PECOs v0022FFNIRSI
Can you please tell me if the calibration should be done after each firmware update through the menu-usb connection?
By uploading the firmware, the calibration of the input divider DOES NOT CHANGE.
If it is necessary, there will be a warning about it in the firmware.
v0022F, upgraded from v0014C, which worked well.
No waweform displayed at all, on both channels, 1x or 10x, DC or AC. (used internal & external generator)
Trigger icon flashes red (i presume that means trigger events?), but still straight yellow line. patient is dead
PS. RTC module is installed and works fine.
Calibration done? Picture calibration value? Video?
Calibration done? Picture calibration value? Video?
calibration is missing in the main menu. that seemed strange to me on the first run (i have watched your video on how to do calibration), but i thought you have removed it from v0022
What is this for? What do the values mean?
#define SETTING_SECTOR_VERSION_HIGH 0x0100
#define SETTING_SECTOR_VERSION_LOW 0x0002 //0x0003
try this
it works. waveform displayed, P-P amplitude is correct, but it's shifted down of channel baseline.
calibration option still missing in the main menu
Did you turn on the USB connection and click as accurately as possible in the center of the screen? And there he reset the values by clicking OK.
P.S. 7 file downloads intended for one person only not working V+ and V- for CH2 channel(By uploading the special version, set default settings of the oscilloscope. If you upload 0.022j, the default settings will be uploaded again.) reset calibration dataReload the latest version 0.022f.
What does the original software do? didn't you make a short circuit?
Baseline calibration always works, and its task is to set zero. PLS VIDEO!!
What is this for? What do the values mean?
#define SETTING_SECTOR_VERSION_HIGH 0x0100
#define SETTING_SECTOR_VERSION_LOW 0x0002 //0x0003
That is something added to allow checking on the version of the settings. When this is changed the system will know the settings on the card belong to a different version of the software, and an error can be generated.
Used in the function void scope_save_config_data(void) when writing settings to the SD card and void scope_restore_config_data(void) when reading them back. These functions can be found in scope_functions.c
Can I set the 2 constants to any value? So that default values are loaded with a new firmware release?
Did you turn on the USB connection and click as accurately as possible in the center of the screen? And there he reset the values by clicking OK.
Reload the latest version 0.022f.
What does the original software do? didn't you make a short circuit?
Baseline calibration always works, and its task is to set zero. PLS VIDEO!!
reloaded your test fw (not 0.0022f release), and somehow this helped, let me perform succesful levels calibration. re-taping blue screen confrims that new values are saved.
i connect to internal gen, then to external (DSO203 Wildcat 6.5). looks weird (see attached pics), but result is identical on both devices (fnirsi gen connected to DSO and vice versa). so let's assume it works correct.
then, i have changed test fw to 0.0022f and wow - it now works here also.
i will continue testing further.
I think I know where the problem is.
Can I set the 2 constants to any value? So that default values are loaded with a new firmware release?
Yes that is what it does in the scope_restore_config_data function. It checks if these values match what is read from the SD card and loads a default set if not.
Only changing for instance the low one will do this too.
Ok, thank you.
I added some texts at the start of the new software. A text about uploading default values will be displayed, if necessary also a text about calibrating the input divider.
The new version has moved the location of the saved values on the SD card.
The result will be loading the default data and deleting the input calibration data. Calibration of input dividers will be required.
I have to make a board with reference voltages.
Long time mode. A million code edits.
Every time I look at the pcb, how the power supply and bus lines are solved, I want to cry. It is not possible that in the era of simulators and Altium Designer and high-quality oscilloscopes, something like this could be created.
I would like to try to install some ferrites to reduce interference. Yes, they can be given somewhere. But where they could make the most difference with the AD converter, it is impossible there.
Every time I look at the pcb, how the power supply and bus lines are solved, I want to cry. It is not possible that in the era of simulators and Altium Designer and high-quality oscilloscopes, something like this could be created.
I would like to try to install some ferrites to reduce interference. Yes, they can be given somewhere. But where they could make the most difference with the AD converter, it is impossible there.
I doubt that would help. It's about diff pairs length tuning, which is obviously failed in our device.
I was also looking at the nice lines from AD to FPGA, each of a different length
Long time base
I was also looking at the nice lines from AD to FPGA, each of a different length
Long time base
Can this kind of feature, FNIRSI-1014D, be done?
TOKAR: Test it.
Test channel 1 for signals with DC offset. Your favorite activity.
channel 2 is not modified. Menu to the right do not use V2+ and V2-
v0.022o version only for testing the autosetup function
Can this kind of feature, FNIRSI-1014D, be done?
No, the 1014D has to much differences for just using this firmware. There has been some work done on the 1014D, about which you can read
here.
Do you want a battery indicator in percentages? 95...90 ...85 But the value will fluctuate.
Only if it could be smoothed. The jitteriness of the current one is noticeable in the corner of your eye sometimes.
I can't recall -- does it change color when < 5/10/15% ? If not, that would be a good add at least. Don't think I've pushed it that low before. Would be nice as long as it didn't flicker (go green>yellow once 15% is hit, but not turn back green until 20% is hit, etc.. assuming you can track state easily enough if not just looking directly at the current pixel color)
Do you want a battery indicator in percentages? 95...90 ...85 But the value will fluctuate.
Add a slow averaging filter on it.
In the original code they do something with the time base setting to compensate the reading. The FPGA plus ADC's will draw more current when the sampling rate is higher, but I don't think it is needed when properly filtered.