Open FreddieChopin opened 5 years ago
BastitNi
commented
5 years ago We are currently working on a new way of scripting, that will be way better that the actual decoders scripts and builders scripts . So, the next update of ScanaStudio should solve this bug.
FreddieChopin
commented
5 years ago So, the next update of ScanaStudio should solve this bug.
Can you share some timeline for the next release of ScanaStudio? (; Will Modbus protocol decoder be available with this new release too?
ikalogic
commented
5 years ago Hello @FreddieChopin
We estimate that we need 3~4 weeks to release this new version.
The documentation for the new script system is also almost finished, here is preliminary version: http://cdn.ikalogic.com/docs/man/ScanaStudio-scripting-manual.pdf
Scripts are currently being ported to the new "V3 API" and are hosted in this new repository: https://github.com/ikalogic/ScanaStudio-scripts-v3/ (You can follow the evolution of new scripts are they are being ported every day or two).
This is not official information yet, but i am providing it to reassure you that things are moving a lot on our end :)
As @BastitNi said, the new scripting system is much better. It's really worth the wait!
Thank you for your patience,
When using Modbus decoder (RTU mode) in the most recent ScanaStudio on Linux, the decoding frequently "hangs", even though decoded frames are displayed in the graphs and can be viewed in PacketView or RawView. The problem is that the decoder's progress bar stops before ~50% and just stays there, while usage of one of CPUs is constantly at 100%. This happens even with the shortest possible number of samples (1 second in my case).
On the screenshot you can see the very last Modbus frame that was captured, properly decoded, and the stuck progress bar of the decoder.
Please let me know how can I provide you some more details to help you fix this issue.