Home > Forum > LogicLab development environment information > Bug on interactive debug mode
- This topic has 3 replies, 2 participants and was last updated 4 years, 4 months ago da Sergio Bertana.
-
AuthorPost
-
February 19, 2019 at 7: 09 am #46675StefanoParticipant
I found a bug on “Interactive Debug Mode” in LogicLab 5.8.0.17. I have a project with a task written in FBD and a task written in SFC with actions written in FBD.
If I go into interactive debug mode with the target connected (Mps054_XTarget_12_0 on ARMv7M. System runtime: 1.18.7) and I double click on a variable in the task written in FBD, the “Force Value” mask appears and I can act on the variable. Same thing done on an FBD action of the task in SFC and the “Variable Properties” mask opens as if you were editing.
At this point I disconnect the target, go into simulation and live debug mode without closing the previously opened windows. By double clicking on the variable in the action in FBD, “Force Value” appears rightly.
I exit the simulation, reconnect the target, reopen the interactive debug mode and click again on the previous variable and the “Force Value” mask appears again.
Staying with the connected target and in interactive debug mode, I close all the windows, reopen the previous action and click again on the same variable and the “Variable Properties” mask opens again.
February 25, 2019 at 9: 05 am #46699Sergio BertanaAdministrator ForumHere is Axel's answer
But summing up, the problem is that on FBD action it is not possible to force the value of a variable in live debug because the property window incorrectly appears?
I don't understand what the simulator has to do with it ...
Do open windows mean editors? Even this, however, seems to me an irrelevant thing, correct?I think that to get to the top of your problems is better that you contact Axel's support directly, avoiding triangulations in this way you can directly indicate the problems to them.
October 31, 2019 at 1: 10 pm #50603StefanoParticipantAt the time Axel had reproduced the anomaly and opened a ticket for the matter, saying he would then contact Elsist for fixes. Are there more developments?
October 31, 2019 at 1: 13 pm #50668Sergio BertanaAdministrator ForumWe should be coming out soon with a new version of LogicLab which also includes the Raspberry-based product MPS055.
According to Axel they should have solved this problem along with many other minor BUGs. we wait for the release so you can try directly and check if actually solved.
-
AuthorPost
- You must be logged in to reply to this topic.