I have a project that was working fine when I left work on Friday. Alll windows were saved and the machine was shutdown cleanly.
When I tried to rung the project when I logged in on Monday strange things were afoot.
It manifested itself as having no data from the controller for my tags.
It was only when I opened the para module that I discovered that for some reason, all the tags have lost their S7 periphery address config (I was using the native S7 driver) and have been replaced with a _dstrib entry and a driver type of SSI. I resolved myself to having to add the periphery address again from scratch. If this wan't bad enough, when I tried to add a S7 periphery config to the tag, the configuration window appears, which I fill in, but when I hit apply or OK I get a system error (see attached image).
https://www.winccoa.com/fileadmin/image ... _Crash.jpg
Help! I don't want to lose my project.
Para periphery address config crash
- Smiffy
- Posts:45
- Joined: Thu May 18, 2017 4:21 pm
Para periphery address config crash
- Attachments
-
- Smiffy
- Posts:45
- Joined: Thu May 18, 2017 4:21 pm
Re: Para periphery address config crash
Some more information.
It seems that the crash / dialogue message may be related to the driver not running.
I have started the driver. However, this leads to another issue. I cannot expand the tags in the Para module pas their top level config (i.e. I cannot access the _peripheral_address etc.). When checking the console, the driver shows a megenta 3 as its status. I have never seen this before. I must be related to my issue.
It seems that the crash / dialogue message may be related to the driver not running.
I have started the driver. However, this leads to another issue. I cannot expand the tags in the Para module pas their top level config (i.e. I cannot access the _peripheral_address etc.). When checking the console, the driver shows a megenta 3 as its status. I have never seen this before. I must be related to my issue.
- Smiffy
- Posts:45
- Joined: Thu May 18, 2017 4:21 pm
Re: Para periphery address config crash
Found the issue, but it has IMHO identified a fatal flaw in OA.
What happened is that I had a script that changed the periphery address on the fly.
Due to a coding error, I set one address reference to something invalid (DB2.DB120 as opposed to DB2.DBD120).
This prevented the S7 driver from starting (and stopping too).
The trouble is that you cannot edit the periphery address in the para unless the driver is running. However, the driver would not run because of an invalid setting in the para periphery address. So you have a deadly embrace type situation.
So as an attempt to escape this, I exported the database and changed the invalid addresses in the database to valid ones. I then imported the database. This somehow changed the root password (it was blank in my original project). So now I can't access the project at all.
Not happy.
What happened is that I had a script that changed the periphery address on the fly.
Due to a coding error, I set one address reference to something invalid (DB2.DB120 as opposed to DB2.DBD120).
This prevented the S7 driver from starting (and stopping too).
The trouble is that you cannot edit the periphery address in the para unless the driver is running. However, the driver would not run because of an invalid setting in the para periphery address. So you have a deadly embrace type situation.
So as an attempt to escape this, I exported the database and changed the invalid addresses in the database to valid ones. I then imported the database. This somehow changed the root password (it was blank in my original project). So now I can't access the project at all.
Not happy.
- dbindernagel
- Posts:161
- Joined: Mon Feb 23, 2015 1:34 pm
Re: Para periphery address config crash
You can use the simulation driver instead of the S7 driver.
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Para periphery address config crash
Normally when doing a complete ASCII export and importing the same file into a new database the information will still be the same.
There is no functionality which changes the passwords.
Which tool have you been using to modiy the ASCII file?
In case of Excel maybe the content was modified by formatting options in Excel, e.g. masking text with quotation marks, and therefore the passwords are different.
If you want to change only specific parts of the project with an ASCII file you can use the filter settings for the export, e.g. a DP/DPE filter, the "P" option (parametrization) + a config to export only specific configs (_address, _archive, ....).
As mentioned by Dennis Bindernagel you can use the simulation driver instead of the real driver if you want to change the _address settings.
The driver with the desired number must run, otherwise the configuration of driver related configs (_address, _smooth, _cmd_conv, _msg_conv) is not possible.
Best Regards
Leopold Knipp
Senior Support Specialist
There is no functionality which changes the passwords.
Which tool have you been using to modiy the ASCII file?
In case of Excel maybe the content was modified by formatting options in Excel, e.g. masking text with quotation marks, and therefore the passwords are different.
If you want to change only specific parts of the project with an ASCII file you can use the filter settings for the export, e.g. a DP/DPE filter, the "P" option (parametrization) + a config to export only specific configs (_address, _archive, ....).
As mentioned by Dennis Bindernagel you can use the simulation driver instead of the real driver if you want to change the _address settings.
The driver with the desired number must run, otherwise the configuration of driver related configs (_address, _smooth, _cmd_conv, _msg_conv) is not possible.
Best Regards
Leopold Knipp
Senior Support Specialist