I would say yes, but the values you posted are so far off that one suspect there is more to it. Keep in mind that each V/Div needs to be calibrated separately for both offset and gain and also they will be back to defaults after a power cycle unless you explicitly save the calibration.
I too would welcome the possibility to stretch a captured waveform both in the x and y direction. As it is now however it is a trade off for faster refresh rate. The fact that it reappears after a change of T/Div however was new to me and it is not intentional (the waveform will not reflect the new time base).
the waveform does not reappears with the new time and voltage scales . it goes back to the original time/voltage scales (those that the signal was captured with) .
so i think there’s nothing wrong with this .
Closer inspection will reveal that the waveform maintains it’s same physical dimensions on the screen but the changed parameter T/Div and/or V/Div indicators do change. All the measurement and cursor functions (another form of measurement) are incorrect because of the changed scales (for example changing T/Div from 200us to 50us results in an erroneous frequency measurement of 4Khz vice the correct 1Khz. You can change the scales back to the original values and all is normal once again. So bottom line, nothing was gained by this maneuver at this time except potential confusion.
BenF: Thank you for your input on this. I played with it a bit more this morning, and I think I figured it out. The offset and gain seem to be interacting with each other. If I set offset to 0uV, cal gain (near full scale for the range) then check the offset again, it is off by 400mV or so. I adjusted it to half of the offset, re-cal gain, check offset and it is off by less this time. I wash, rinse and repeat until it is very close. Now, my 1V/div range is close enough for what this will be used for.
Thanks again.
Tim
EDIT: I have been going through the ranges and the 10V range will not cal. I have a two to three volt disparity between what is going in and what the DSO reads. The ranges from 0.1V to 5V all cal’d quite nicely.
It would be a nice feature if it was displaying correct again once you have the same time,volt/div so the buffer is not lost because of clumsiness with the buttons. My friends fluke industrial scopemeter even maintains the buffer when powered off so it can be turned on and looked at again as long as you don’t start to measure again.
The Nano supports export of capture data to XML files, but not streaming of live data. Doing so would require development of a custom firmware to replace the current USB file system interface with a USB serial interface as well as a PC application to process the live data.
For those interested in pursuing such development, here are some high level constraints to consider:
Ahhh, OK. I assume that is a limitation of the chip and/or phy that is being used rather than that of the software? If so, perhaps the DSO Quad should have a High-Speed (480Mbps) capable phy and chip.
As to the custom firmware, while I have only ever been involved with USB storage at that level, I think you can support multiple end-points if you set things up correctly.
I agree that it would involve a PC application to support the live data, but there are already some to choose from, like XOScope and others, although their code might not be capable enough or in good enough shape to work from. However, having been involved in Ethereal/Wireshark I have seen how something can start from humble beginnings and take over the world.
Will I be able to use the DSO Nano V2 to analyse 100kbps I2C?
I imagine that 400kbps I2C would be beyond the DSO Nano’s capabilities (I seem to recall an HP document suggesting that you need something like 5 times the sample rate as the bit rate you are trying to measure to get reasonable fidelity on the wave forms).
I have an answer for you, but since this thread is discussing future DSO capability and your question relates to existing capability I have posted it in a separate topic.
I recently received my DSO Nano v1.
I have updated to DSO firmware version 3.43.
I have tried to use it during my lab exam in the college and compared the results to the Tektronix oscilloscope that we have in the lab.
I have found that for some strange reason when I measure 2 outputs in the circuit and overlap them on the DSO the time line doesn’t match.
for example, I had this circuit:
I have measured the two outputs with my DSO and got:
After that I have measured the same circuit with Tektronix and got:
The following info would be required to best analyze your question: Trig. Level and Trig. Sens. for each original Nano waveform capture, and the sampling rate, trigger level and trigger sensitivity (if it has this feature) that the Tek Scope was using for the the Tek capture(s).
I can explain the reason, but finding a solution to this is more of a challenge.
A limitation with a single channel (and single trigger) scope is that you can not synchronize two waveforms in time. You can do two separate captures and compare the shape (amplitude, frequency etc.), but you can not determine relative timing between them. On the Tektronix, both waveforms are synchronized to the rising edge of the square wave. The DSO triangle waveform however will trigger on its own rising edge independent of the square wave. If you repeat measurements and move trigger level up towards the triangle peek, the DSO triangle waveform will move left and so approximate what you’re after. The only way you can determine that this is how they relate timing wise however is if you already know.
The upside would be that as a lab exercise, you probably learn more from this than any of your fellow students without access to a Nano.
Edit: I didn’t see your post lygra, but assume he is referring to the time displacement between the two waveforms.
If you are unsure if the two signals are in phase or not, then as BenF states, you can’t compare the phases with the current Nano. If you already know that the two signals are in phase, then this is a different colored horse.
I just completed another video explaining Gnd Pos issues and how to align a displayed signal to a REF wave with known zero phase shift between them. If this is your issue, then go see that video for the solution.
Basically, I am suggesting that if the two signals should have zero phase shift, then your Tr. Sens. setting is the most likely culprit to take them out of sync.
First X L ent firmware!! I notice that Scan mode is enabled only when the time/Div goes bigger than certain value automatically.
My recuest is this. Im working in my thesis taking lightnig data with an antena and I have to watch the oscope every time that I see a lightning to capture the data.
Is there any way to put the DSOnano in a mode (scan mode like) to automatically empty the buffer every time it gets full and append that data to the end of a certain FILExxx.XML? it would be helpfull if the file auto001.xml have a fixed size and once it reach that size automatically the software creates auto002.xml and it start to append the data to that file. maybe 10Mb. Thanks bro for that work youve done.
