This must be an outdated information then.
Quite obviously, there ia a request for wildcards in the equality condition for serial ID and/or Data triggers, like it is already implemented for SPI (see attachment).
Quite obviously, there ia a request for wildcards in the equality condition for serial ID and/or Data triggers, like it is already implemented for SPI (see attachment).It should be quite obvious, that on the CAN bus, there are not only three ID´s. So i would call a filter a *requirement*. I already worked many hours on a problem, and trying to figure out (learning) how to use this scope for that. Its a challenge with these limitations!
Your ambiguous usage of terminology was primary reason why I had to ask 5 follow up questions to understand what you are talking about.
Your ambiguous usage of terminology was primary reason why I had to ask 5 follow up questions to understand what you are talking about.
I said: "filter for a range of IDs"
You asked: "Filter in decoded list or in trigger?"
I said: "Its the trigger"
From then on, i would say that it was pretty clear what my intentions were even though my terminology may not have been right.
I would call a "range" not exactly a mask. Try to mask the range of 1-2 !
Could you please provide a link to Rigol document where it can be seen how it works there? I'm curious how it was implemented
https://int.rigol.com/file/DHO800%20User%20Manual.pdf
Chapter 8.7.16 describes the CAN trigger. For details regarding the mask entry (page 106), it refers to the description in section 8.7.14 (I²C trigger, data entry, page 99).
Wildcard entry is implemented just like for SPI data in the Siglent 800X HD: You get a keypad which has the digits for binary, decimal or hex entry enabled, plus a pseudo-digit "X" for don't-care digits.
I just had the two "little ones" in operation, decoding.
I don't know which visual list display I would prefer.
Rigol used a X for a wildcard on binary and hex.
I think there is no documentation. It seems to just have been chucked into the 800 from the 900 recently.
If there is no range possible, it would be nice to be able to extract the decoded CAN (with frame time) and then beeing able to filter it via spreadsheet. Or even "filter" those in the CAN list that is below.
I tried to do it with sequence, but with that i only can capture like 2265 frames. If i would be able to set a 5K max memory depth, then i could fit all my frames in there, and then get it out via stepping through the sequences with SCPI, which is all in all quite a task, that could otherwise easily be implemented into the scope (and webinterface!).
To bad that it is not open source. I would have loved to program that in!
Hi Rob,
Just tried it out, yes, no problems, I could get used to the mouse control.
Oh yes, it's not in the data sheet, but just tested, maximum frames (CAN) are 2000.
I have now exported the list of 115 decoded frames(csv), if that is what you meant, it was no big deal.
I have now exported the list of 115 decoded frames(csv), if that is what you meant, it was no big deal.
I have to laugh about myself. That task i gave you was too easy.
Working a bit to much, i guess.
My problem is, that when i use 500k CAN speed, with 1s/div (max timebase to capture for that rate), i can only export 2000 entries, which are also corrupted (the shown data only), if you set the timebase above 100ms/div. Only 2000 frames is quite poor in my opinion, since we are talking here about ~ 20kb. And it should decode properly, what ever the zoom is, because one might think that this data is corrupted in reallity! That sends you far on the wrong track. A device for over 500 bucks should not show complete wrong data.
In other words:
I need to be able to capture and export 20.000 CAN frames (in 10s) with a range of IDs (they can be filtered out on export in this case, additionally to the trigger mask).
Another thing:
After a crash, i was was trying (thinking) to reload a waveform, thinking "ah no problem, i can just reload the waveform and decode it again". I was dissapointed.
This would be a really nice feature, since sometimes you also hit the wrong button, and loose that waveform.
Now it is clear to me that you are complete beginner in this whole oscilloscope thing.
Now it is clear to me that you are complete beginner in this whole oscilloscope thing.
You should have though about this already when you said i had some bad terminology. But in fact this is not true.
I do not ask about things that are not implemented, im talking about a tiny bit more effort to have the funktionality perfectly useable.
About my specs:
If i havent misscalculated, those would mean a frame every 500us. In fact, i can capture and decode frames that come every 220us until the list is full with 2000 entries (~32kb is not so much memory nowadays). You may have misscalculated?
I haven't got miscalculated anything.
Let me guess.. You are software developer? Right?
I haven't got miscalculated anything.
Let me guess.. You are software developer? Right?
Review my edited post.
Yes i do develop software.
Now it is clear to me that you are complete beginner in this whole oscilloscope thing.
You should have though about this already when you said i had some bad terminology. But in fact this is not true.
I do not ask about things that are not implemented, im talking about a tiny bit more effort to have the funktionality perfectly useable.
About my specs:
If i havent misscalculated, those would mean a frame every 500us. In fact, i can capture and decode frames that come every 220us until the list is full with 2000 entries (~32kb is not so much memory nowadays). You may have misscalculated?
See the pictures: 1s/div looks good, 2s/div is the limit, or even a bit above. 10s with 250us frames would mean 40000 CAN frames. Even if it may not be possible to have 40000 in that list. It should be easily possible to export those!
I have to laugh about myself. That task i gave you was too easy.