Hej Fredrik,
-I could send you a station file, but it’s 85 MB big. In this station I have no problem reproducing the error with the missing configs as I described above. If you don`t need more than the station file then gimme ftp and I’ll up it.
-The problems with the IOs happened again and I also found a workaround, which I will describe exactly now:
In RSO I created a bunch of signals. Then I created some System Inputs and System Outputs with some of these signals. I did a (warm) restart (in RSO) of the controller and everything was fine. Then I created even more signals, and stepped over some signals which names I misspelled, and changed them. After a new restart the controller halted because of a system error, because the signals I changed were linked to some of the system signals, and of course they didn’t work anymore and caused the system error. From RS I got into FlexPendant (I got no connection with RSO anymore) to change this now wrong system signals, but when doing this with one system signal, the controller forces me to do an immediate restart, what I did. It restarted again with a system error, because there have been more than one changed signals and corresponding system signals. This second time I didn’t got into FP anymore, nor into RSO.
The workaround was that I removed the system from the station, connected to the controller again with a cold start, which of course erased all of my signals.
I had this again the last days, but now I do a backup before doing restarts after signal changes or additions. After the cold start the restore of this backup works flawless and I can change the signals that caused the system error.
So it seems that the signal parser doesn’t look at maybe linked system signals when changing signal names.
-I know that I can import that IO.cfg (here it is EIO.CFG in SYSPAR), but only from a backup that I did first. So there is no direct import option in RSO or anywhere else, which I miss. And the format of the cfg is not really conformant to something I can get out of e.g. a database, where I preferrably like to maintain my signals for different projects. So here I think an open format to explicitly import into the controller like XML would be fine. I didn’t tried to remove blank lines in the EIO.CFG while directly editing signals there or other reformatting to make it better editable, because I simply don’t have the time to test stuff like that right now.
It works with backup, editing and restoring, but this is a way which is not obvious and might not be automated. An explicit import option for config files, be it only for signals, would be obvious.
Thanks for all your help and responsiveness, I try to do my best to tell you what problems I face here and how to reproduce them, but right now this particular project I do here does not give me too much time for it right now. I am of course also interested in getting better versions of your all-in-all great and from all robot manufacturers most advanced controller-, offline- and simulation software, but our customers are interested in results, and not programmers problems nor -dreams. And right now it’s of no use for me when you know this problems, but I have to stick for months with the current versions and have to develop workarounds for every problem in this case of tough time pressure. So please understand my frustration sometimes and don’t understand me wrong - RS+ is a really cool piece of software.
Hej da,
Lohengrin