ScanaStudio 5.1.29 crashes when I’m setting a marker or measure in the signal area.
This happens every time I’m using one of the marked actions in the right click menue.
Hi @Olaf ,
I tried many times but I was never able to reproduce the issue.
Can you please tell me if this also happens if you use Scanastudio in demo mode? Or only with a device connected?
With 5.1.30 the markers seem to work now. But the measures are still crashing.
An SP1018G is connected in real mode.
Here is a memory access violation of ScanaStudio 5.1.30 I could capture. It happened when adding a custom measure.
Also still setting simple markers sometimes crashes the program.
Hello @Olaf
Okay, thanks for all that info.
Can you please send us a *.scana workspace before adding a marker so that we can reproduce that on our end? you can either send it here or by mail to contact@ikalogic.com.
Thanks you very much
I will send you the config file by email.
I now discovered that it also crashes when I’m using the NORMAL trigger instead of SINGLE. When I start the capturing with NORMAL it takes one signal snapshot and then it’s gone. Seems that a somehow general problem exists, not only related to markers and measures.
My environment:
- HP ZBook 15 G6
- 32G RAM
- Intel64 Family 6 Model 158 Stepping 13 GenuineIntel ~2592 MHz
- Microsoft Windows 10 Enterprise, 10.0.19045 Build 19045
Hello @Olaf ,
Thank you very much, we were able to reproduce the problem with your *.scana file, we will fix this ASAP.
Thanks!
1 Like
Hi,
Just letting you know my colleague has fixed the bug.
We’re adding some minor features, then we’ll issue an update in the next 24/48 hours.
1 Like
Great. This is what what I’m calling support.
Thanks a lot.
1 Like
ScanaStudio 5.1.31 is still crashing when I’m adding a standard measure.
I didn’t try markers or the custom measure this time.
I am not even able to send the crash report because the tool also doesn’t save the port of the proxy configuration and has no WWW connection when the report is ready !
NORMAL trigger does not work.
After some captures it hangs up with the “Triggered - Collecting samples” message or it crashes directly.
Hello @Olaf
I have reported this to our @Nicolas_ikalogic - he indeed fixed the “add marker crash” but i can see that with your workspace it still crashes when adding a measurement. Very sorry for that. It will be fixed quickly since we’re able to reproduce.
Regarding the trigger: i’ll run some tests in an hour when i’m at the office and get back to you.
Thank you for your patience and understanding.
Sorry for the stupid question, but are you sure the logic change is just not far away from the trigger marker?
Please find animation below: depending on the zoom level, the logic change that caused the trigger may be out of the screen
The trigger marker position offset is a known issue that will be be fixed in the next FPGA firmware update.
I’m just expecting (!) the trigger marker points to the trigger event. Obviously it’s another defect of the GUI.
Hi @Olaf,
just to give you some context: I know it may seem straight forward, but it’s a bit more complex than that. SP1000G integrates 4 trigger engines, 2 Flextrig engines, and 2 Fast Trig engine.
Fast trig always run at 1GSPS, they are used for simple edge based trigger, and Flextrig always run at 250MSPS, they are used for more sophisticated trigger sequence, like decoder based trigger, pulse width, etc.
So the result is that trigger engines are all totally dissociated from the sampling clock, and the exact offset can be variable.
We’re working on a firmware update that should get the trigger marker very close to the actual trigger even (less than 4 samples).
1 Like
@Olaf Just letting you know i have just finalized a firmware update that makes the trigger position much much more precise.
This along with some GUI fixes @Nicolas_ikalogic is working on shall be included in the next release, in the next few days.
Again, thank you for helping us with you feedback and constructive comments.
1 Like
With logic change trigger active the device always triggers although no signal is moving at all. Even when I pick only one single signal as trigger source.
Until we release the next update, could you try using the “sequence trigger” instead ?
