FNIRSI-1013D "100MHz" tablet oscilloscope

[Atlan]

Putting the menu below itself would take up 3x as much screen space, so it's better to put it next to itself.

[Russell2024UK]

Atlan  Concerning the trigger type being relocated on the 1013D oscilloscope, having it placed next to itself would be ideal for me—though I'm unsure how others might feel about it 

[Russell2024UK]

Hi Atlan  Apologies if I've overlooked anything in this forum thread. ( with Firmware v0.26n) Will the "Hold On" icon  within the trigger area on the 1013D function the same way as the "Hold Off" feature on my other oscilloscopes ?

As for the External Trigger (Ext) within the trigger area , how will this operate ? As you know, an external trigger allows an oscilloscope, like other scopes to synchronize its display with an external signal source. How would this be implemented on our 1013D?  Thanks

[ECJ]

Hi Atlan  regards my last post looking again could they line up horizontaly For Auto,Single,Normal  What do others think about this idea?

First of all, thanks to Atlan for all the features he's added recently. I haven't been interacting, but I've been checking them out sporadically.

Russell2024UK, I prefer the buttons to be aligned horizontally.

[Atlan]

Theoretically, the plan is to modify the code for the FPGA to be able to add functions: ext trigger via pin 1khz (if a hole is drilled and a bnc is installed, then the wire can be soldered) of course, the maximum 3.3V logic must be respected (mainly used when working with uP, Possibility of selecting the frequency of the rectangular signal on pin 1khz. Hold off? Yes. There is still a problem with the FPGA that the signals do not have time to reach where they should. (This is the case when someone thinks that they can connect the AD converter to any FPGA pins and the CLK signal for the AD converter, but they can't....) Another problem is that I have not yet found out whether the FPGA EF2 is password protected. So it will not be possible to return the firmware of the fnirsi to the FPGA EF2. Those who have AL3 FPGAs are better off, because the mod for the FPGA is in flash, and it can be easily deleted. But I have already managed to upload the code to flash twice that caused  that the oscilloscope was totally dead. Unplugging the flash and uploading again solved the problem.
It is necessary to compile the entire code for the FPGA again. Due to the nature of the fpga function, it must be clear in advance what the FPGA is supposed to do. Changing the FPGA program code is not easy.

[pcprogrammer]

Yes, implementing a design for a FPGA is a whole other field that writing some code for a microprocessor. That is why I failed in getting the original reverse engineered FPGA implementation to work properly. You need to setup timing constraints to force the place and route tools to adhere to strict limits, otherwise the signals can be delayed to much and things don't work.

One also has to take care of proper synchronous design and avoid different clock domains as much as possible. Another issue is metastabillity that needs to be assured. Input signals can need synchronizing to the clock signals to avoid problems.

It is fun though, when things start to work.

[Russell2024UK]

Hi Atlan  Thank you for your clear and detailed response. Incorporating an external trigger would be a fantastic addition to the 1013D oscilloscope. I'd be open to finding a way to fit another BNC connector (soldered) for the external trigger functionality. I must admit, though, that I find the FPGA aspect quite complex and challenging to grasp—it doesn’t seem straightforward.

[Atlan]

0.26o

[Russell2024UK]

Atlan  Wow, the firmware V0.26o  with its newly upgraded trigger menu looks fantastic—excellent work once again! 

[ECJ]

Atlan, the menu layout is great! Thanks!
But, changing the subject, something I sometimes miss is, in the "ACQ Long" mode, being able to pause the scan (run/stop button) after capturing a signal and use the cursors to measure time and voltage without the signal disappearing from the screen. Because every time the cursors are moved, the signal disappears. Is there any limitation that prevents this?

[Russell2024UK]

Hi Atlan I wanted to share an observation about the 1013D Oscilloscope. If you capture a SAVE WAVE of a Ref (Channel Icon) capture, you can measure both Voltage and Time using the cursors. if you keep CH1 or CH2 active (live), it provides voltage measurement for the cursors while retaining the time functionality—this setup works quite well! 

[Russell2024UK]

ECJ well spotted    Just checked i have the same too

[Atlan]

Acq long, draws directly to the display and stores in memory. Moving the cursor means erasing the cursor and redrawing everything there. That means calling some function that will do it.

[Russell2024UK]

I captured two signals from my Arduino UNO board—TX 1 and RX 0—using channel 1 and channel 2 of the 1013D oscilloscope, respectively. Both signals were captured as REF (within the channel area), which made positioning straightforward and prepared them for measurements using the cursors. I plan to test this setup again soon using my Rigol Oscilloscope to compare the results. Thanks once again! 

[madori]

Hi, just wanna ask, I dont know how to move rulers when stop scope to not lose graphing and get some mesurments..
Tray to save waveform but this either cant in slow mode 200ms 500ms, 1 sec... tray to calculate some automotive stuf rpm etc
Also my scope newer work good using normal trigger, only auto mode. and sometime go crazy hard to explain..
low cost low quality
Thanks

[TA4DIL]

Hi Atlan, V0.26o looks great with the new menu layout and updated trigger menu - I'm following your excellent work, thank you very much for your efforts.

[Atlan]

Tray to save waveform but this either cant in slow mode 200ms 500ms, 1 sec... tray to calculate some automotive stuf rpm etc

Save the waveform, and later it is possible to perform measurements in waveform viewing mode.

[ECJ]

Here, if I try to save any waveform in acq long, only a straight line is saved. This in any firmware version.

[PerLi]

If you drag the waveform to the right, you will see it.

[Atlan]

How I hate making menus on this oscilloscope......

[Atlan]

I wanted to separate the individual menus with lines, but it seems very yellow to me now. Any ideas? For the Math menu, AxB is enough or better Ch1xCh2 since I don't see the point in assigning individual inputs to the letters A and B. Should I reduce the font or keep it?

[Russell2024UK]

Hi Atlan  Having reviewed the menus on the 1013D oscilloscope, I’m happy with your new current layout ( Picture) , including the yellow lines—they work well for me. Using * to represent A*B for math calculations is ideal too. I’m confident others on the forum will share their feedback with you soon. Thanks once again for your efforts! 

[pcprogrammer]

My personal preference would be more like the attached image, where the bottom section is stretched across the whole menu and the probe magnification settings are some what centered.

Also maybe make the voltage per division buttons less high so that they all fit in a single column, and the menu becomes less wide.

What is the 50% button for by the way? When it is needed maybe you can move it to the lower part of the menu with a separate section.

[mehdifat]

from the pic you sent yellow is good .
what about giving users some predefined colors and let them choose if possible?

[engineer.r152]

it seems to me that it should be done in the same style as the rest of the menu.