NWT.Stuff
Hi,

I do some have some minor bugs to report for this software.  Just a general question for now; how do you want bugs reporting e.g. bug by bug or all wrapped up in a word file ?

If I could know your preference then I can log my issues according and post them later.

Many Thanks in Advance

Kevin     
Quote 0 0
thiagoralves
The best way to report a big is to raise an issue on the GitHub repository of the project:  https://github.com/thiagoralves/OpenPLC_Editor
Quote 1 0
NWT.Stuff
Ok Thiago will do.
Quote 0 0
adriano.mele

I raised an issue as well, hope github is the right place for this.

Details are also reported below:

 

In some cases, when something goes wrong during the compiling procedure, the editor crashes and the compiler gets stuck in the middle of something.

This behaviour occurs, for instance, when you have typos in SFC transitions (e.g. a ANDb instead of a AND b). The returned windows error is "file \xe8 is already used by another process".

Not sure this report helps, but it may be something worth checking (the only fix I find is to reboot the system, which may be very annoying when you are trying to track down the bug).

 

 

 

 

Quote 1 0
NWT.Stuff
Working my way through a project and 2 or 3 minor bugs to report.  I already have my work arounds so no issue for me but it's the sort of stuff that could put stop a budding home enthusiast willing to learn in their tracks.  There's a lot to take in and consider when having a go ! It's certainly not universal plug and play but then it shouldn't be because it's quite high level stuff and that what attracts us to stuff like this. 

Enough ranting; simple question as I don't know how you guys work.  What's the best for you ?
- 1 bug = 1 issue
- 1 issue = all the bugs in 1 project 
- spilt by function e.g. beremiz, editor, runtime html.

P.S. If i could have back all the time I spent on Hardware with apparently compliant UPnP integrated I would have chilled a lot 🙂
   
Quote 0 0
thiagoralves
I've seen these lockups, and they are quite annoying really. Unfortunately they are on MatIEC code, not on the Editor. I'll try to update to the latest version of MatIEC compiler to see if they go away, but fixing MatIEC is a totally different universe that I wouldn't like to dig in to. It would be very good to have a specific code that breaks the compiler, and then check it against the latest version of MatIEC in here: https://bitbucket.org/mjsousa/matiec/commits/
If it also hangs on the latest MatIEC, it would be good to open a ticket in there explaining the problem.

As a work around, you don't have to reboot your computer. Just open the task list (ctrl + shift + esc on Windows) and kill all the processes related to the editor (matiec, python, beremiz, and openplc editor). Then you can open the editor again and continue your work.
Quote 0 0
adriano.mele

Hi thiago,

thanks for the reply. I had tried killing some processes but I was unsure which ones I had to pick.

I do not have a simple code that replicates the error right now, but it should be as easy as putting some ST error in a inline transition (as I told you, something like "a ANDb" instead of "a AND b" should already be enough). Maybe later I'll try to put together an example.

Quote 1 0
NWT.Stuff
If you had a choice between the windows or linux versions which one would you use ?
Quote 0 0
thiagoralves
They are the same. I would chose Windows just because it is a lot easier to setup
Quote 0 0