I'm sorry to say that CAN_H-CAN_L did not work on the SDS800X HD with V1.1.3.3 firmware.
I'm sorry to say that CAN_H-CAN_L did not work on the SDS800X HD with V1.1.3.3 firmware.
That's a shame, but not a problem. It's why I own an active differential probe.
I don't suppose you know if it's any different on the 2000X-HD series?
It would be really cool if you could acknowledge, every now and then, that what you considered a bug is not one [...]
I did not say the B-Wort
You missed my point, I'm afraid. It was not about whether you called this a bug report or an improvement suggestion.
Point is, your suggestion to let Auto-trigger always re-capture a new waveform immediately, without waiting for another trigger event at all, did not make sense. I tried to explain why. And it would have been nice of you -- in this and similar instances before -- to acknowledge that you understood and appreciated the explanation. But all we get is another "But what I want should be possible!".
That has gotten under other several readers' skin a while ago, and it is beginning to get under mine. Hence this friendly suggestion for your future communication in this thread.
Isnt the auto trigger supposed to trigger "all the time" even when there are no changes in the level, when there is no holdoff set up?
My auto trigger does not even trigger when there are pulses... It does for a few moments, then freezes. The frequency reading is reading something.
Just realized, that the normal trigger does this too!
Short pulses every 2.5us and some longer in between.
When i move the trigger, it starts to work again for a few seconds.
WTF? This scope starts to get annoying! Only started to use it this morning.
Edit:
Issue confirmed on pulse trigger mode too!Does happen with 3ms holdoff.The thresshold when it happens is about 885us holdoff.
It seems that there is a general holdoff bug, that is not only related to edge trigger???
I'm sorry to say that CAN_H-CAN_L did not work on the SDS800X HD with V1.1.3.3 firmware.
That's a shame, but not a problem. It's why I own an active differential probe.
I don't suppose you know if it's any different on the 2000X-HD series?
It seems like everyone has already forgotten that there is indeed a general bug with trigger holdoff: [...]
This will be fixed with the next firmware, which shall be distributed to beta testers this week.
It seems like everyone has already forgotten that there is indeed a general bug with trigger holdoff:
I'm sorry to say that CAN_H-CAN_L did not work on the SDS800X HD with V1.1.3.3 firmware.
Among other things, this bug will be fixed with the next firmware release, yet unfortunatley the fix might not be what you expect: the CAN_H-CAN_L setting will just be deleted from the UI.
Some background information:
Serial decoders are closely related to serial triggers. We can copy settings from one to the other. Triggers are working in hardware on the trigger data stream, which is completely seperate to the record data. This should explain why a digital trigger can only work on physical input channels and not math results, and for some reasons we don't get the subtraction done in hardware on the basic SDS800X HD. And because of the before mentioned close relationship with the decoders, they also cannot accept any other data sources as the input channels.
I'm sorry to say that CAN_H-CAN_L did not work on the SDS800X HD with V1.1.3.3 firmware.
Among other things, this bug will be fixed with the next firmware release, yet unfortunatley the fix might not be what you expect: the CAN_H-CAN_L setting will just be deleted from the UI.
Some background information:
Serial decoders are closely related to serial triggers. We can copy settings from one to the other. Triggers are working in hardware on the trigger data stream, which is completely seperate to the record data. This should explain why a digital trigger can only work on physical input channels and not math results, and for some reasons we don't get the subtraction done in hardware on the basic SDS800X HD. And because of the before mentioned close relationship with the decoders, they also cannot accept any other data sources as the input channels.
Sorry if I'm being dense, but I don't understand the relationship between CAN_H or CAN_L not working using a single-ended probe and the background information you provided. Is this a triggering issue? Do you have to use a serial trigger (which, presumably, is protocol-aware, so to speak) to decode serial signals?
It seems like everyone has already forgotten that there is indeed a general bug with trigger holdoff: [...]
This will be fixed with the next firmware, which shall be distributed to beta testers this week.
My perception so far was that the bug essentially has the effect of the trigger holdoff time being ignored (under certain circumstances?). If there are other known side effects, it would be good if they can be published -- to bridge the time until a new firmware can be released, and avoid duplicate reports on already known issues.
I had a presentation of this instrument scheduled tomorrow and trigger holdoff is mandatory for the purpose.
I had a presentation of this instrument scheduled tomorrow and trigger holdoff is mandatory for the purpose.
Do you really need holdoff there? To my mind it is mainly a legacy trigger option, dating back to CRO days where edge trigger and holdoff was all we got. Pulse trigger allows you to trigger at the end of defined quiet periods in the signal, and is a more flexible and robust choice in most situations. Or the various advanced triggers for more specialized situations, of course.
Hi folks,
I received an SDS814HD a couples of hours ago, after FW update and Self calibration I connected an UART line to channel 1 and It tooks few seconds that trigger Holdoff is not working at all ...
Jumped here and discovered that is a known bug, damn I should have checked before, I had a presentation of this instrument scheduled tomorrow and trigger holdoff is mandatory for the purpose.
Quick question : there is a way to obtain the beta FW that fix the problem today ?
Otherwise I have to cancel the presentation, causing some loss of credibility in my person and / or the instrument itself
My auto trigger does not even trigger when there are pulses... It does for a few moments, then freezes. The frequency reading is reading something.
Improvement suggestion:
Placing the zoom window with a double tap on the upper window does not work, if there is a cursor at the same spot.
Edit:
Improvement suggestion 2:
After having captured a few traces on persistance, moving the traces to measure with cursors is not possible, since all traces except one dissappear.
My auto trigger does not even trigger when there are pulses... It does for a few moments, then freezes. The frequency reading is reading something.
I have been able to reproduce this bug. I only got it when trigger holdoff is enabled, but it is clearly a different symptom from the "holdoff not working" that was described before. Maybe it is already fixed with the new beta firmware nevertheless? It would be great if the beta testers could check:
My auto trigger does not even trigger when there are pulses... It does for a few moments, then freezes. The frequency reading is reading something.I have been able to reproduce this bug. I only got it when trigger holdoff is enabled, but it is clearly a different symptom from the "holdoff not working" that was described before. Maybe it is already fixed with the new beta firmware nevertheless? It would be great if the beta testers could check: