Archive Error in ArSim

Hello
we are trying to install and test a project in AR Sim, but at every installation we find in the logger these entries:

AR is E4.92. The software is compiled with AS 4.11.6.26 - GCC 6.30
image

We recreated completely the AR Sim, deleting from TEMP the Simulation folder and repeated the Initial Installation, but the problem remain the same.

Windows Firewall is completely disabled and we do not start understand what it is the software module that it is causing the boot failure.

I appreciate your help!

Marco

Hi Marco,
I would have a look at the ArExceptions…
Hopefully, in the backtrace or the details of the error(s) you can see which task, or at least taskclass the error occurs. Start by deactivating the task and check if it works then.

Also inserting the IEC-Check Library could help you find the error.

Looks like a wrong memoryaccess…

Thank you for the answer Stefan

The problem is it happens at the boot up and the exception is related to the system.

The project already includes IEC Check Libraries, so I expect to have some more information if it is caused by User Program.

Thank you again

Marco

Do you have a task called “RtlClearBits” in your project? Try expanding the backtrace information from your first screenshot:

No Marcus,
It is why I am thinking it’s system related.

I had a similar problem caused by Mapp Motion that I solved updating to the last version of that library.

Marco

Hello Marco,

I agree with you, what I can see in the logger’s screenshot looks like that they’re happening some strange things in a early boot phase of Automation Runtime.

It’s hard to say what’s the root cause and what are follow-up errors / warnings, but I have some general questions to get a better idea of the environment:

  • Does ArSim boots cyclic / “endless”, or does it stop booting in diagnosis mode?
  • From your first screenshot and the 30030 warnings I assume that the target is APC910 with at least 2 fieldbus master cards inside (or even more), is that right?
  • is it a very big project (many hardware - big hardware tree, many tasks and variables, hugh number of OPCUA datapoints, and so on)?
  • Do you have the project already running on the real hardware?
  • Does the behavior of ArSim changes if you deactivate all tasks so that they’re not transferred, and perform again a initial installation?

Especially the last point could be interesting to give us a hint, if it’s a problem of the hardware configuration to be simulated, or if the root cause is somewhere in the tasks / ressources needed for the tasks.

Best regards, Alex

  • Does ArSim boots cyclic / “endless”, or does it stop booting in diagnosis mode?
  • Boot Endless - generating a lot of entries in ArSim Log

  • From your first screenshot and the 30030 warnings I assume that the target is APC910 with at least 2 fieldbus master cards inside (or even more), is that right?

→ I confirm. APC 910 5PC910.SX02-00 + 5PC910.SX02-00 + 5AC901.BX02-00 + 5AC901.IPLK-00

  • is it a very big project (many hardware - big hardware tree, many tasks and variables, hugh number of OPCUA datapoints, and so on)?

→ More or less 17 Programs, allocated in 5 Cyclics. 10+ Acopos P3. A lot of CanOpen Slaves.
We are using a lot of OPC UA datapoints.

  • Do you have the project already running on the real hardware?

→ Yes. This is very strange. In the real Hardware it is working correctly

  • Does the behavior of ArSim changes if you deactivate all tasks so that they’re not transferred, and perform again a initial installation?

→ I will have a try tomorrow!

If is it system bug, you will need anyway to contact support of the local B&R office and provide him project and ask for investigation and bug fix. But lets see what will be result if you deactivate all application tasks.

Hello @alexander.hefner

This is the output of Simulator with all tasks disabled.
The simulator folder has been deleted and then a initial installation has been forced.

Currently, Simulator is looping appending these lines:

*$arlogsys:EventID -2147474438 (WARNING, 0, 9210), lpBin=0x02abfe88, “ROOT”, “Boot”
*$arlogsys:EventID -2147453618 (WARNING, 0, 30030), lpBin=0x0b2afd1c, “PnPManager”, “SL1.IF1.ST1.SS1.IF1”
*$arlogsys:EventID -2147453618 (WARNING, 0, 30030), lpBin=0x0b2afd44, “PnPManager”, “SS2.IF1.ST16.SS1.IF1”
*$fieldbus:EventID -1073708774 (ERROR, 0, 33050), lpBin=0x00000000, “PnPManager”, “MODBUS InternalStartup failed!”
*$arlogsys:EventID -2147453618 (WARNING, 0, 30030), lpBin=0x0b2afe0c, “PnPManager”, “IF3.MODBUS.BUS”
*$arlogconn:EventID 1076899302 (INFO, 48, 11750), lpBin=0x00000000, “tOpcUaComm”, “Begin startup sequence”
*$arlogconn:EventID 1076899306 (INFO, 48, 11754), lpBin=0x00000000, “tOpcUaComm”, “NodeSet ./ADDONS/DATA/OPCUA/NodeSet/Vendor/plc.uanodeset loaded”
*$arlogsys:EventID -2147453228 (WARNING, 0, 30420), lpBin=0x00000000, “ROOT”, “”
*$arlogconn:EventID 1076899306 (INFO, 48, 11754), lpBin=0x00000000, “tOpcUaComm”, “NodeSet ./ADDONS/DATA/OPCUA/NodeSet/Generated/OpcUaMap.uar.gz loaded”
*$arlogconn:EventID 3157478 (SUCCESS, 48, 11750), lpBin=0x00000000, “tOpcUaComm”, “”
*$arlogsys:EventID -1073716510 (ERROR, 0, 25314), lpBin=0x00a82e00, “ArException”, “”
*$arlogsys:EventID -1073735021 (ERROR, 0, 6803), lpBin=0x00000000, “ArException”, “”
*$arlogsys:EventID -2147474423 (WARNING, 0, 9225), lpBin=0x02b1fe88, “ROOT”, “Boot”
*$arlogsys:EventID -2147453618 (WARNING, 0, 30030), lpBin=0x0b32fd1c, “PnPManager”, “SL1.IF1.ST1.SS1.IF1”
*$arlogsys:EventID -2147453618 (WARNING, 0, 30030), lpBin=0x0b32fd44, “PnPManager”, “SS2.IF1.ST16.SS1.IF1”
*$fieldbus:EventID -1073708774 (ERROR, 0, 33050), lpBin=0x00000000, “PnPManager”, “MODBUS InternalStartup failed!”
*$arlogsys:EventID -2147453618 (WARNING, 0, 30030), lpBin=0x0b32fe0c, “PnPManager”, “IF3.MODBUS.BUS”
*$arlogconn:EventID 1076899302 (INFO, 48, 11750), lpBin=0x00000000, “tOpcUaComm”, “Begin startup sequence”
*$arlogconn:EventID 1076899306 (INFO, 48, 11754), lpBin=0x00000000, “tOpcUaComm”, “NodeSet ./ADDONS/DATA/OPCUA/NodeSet/Vendor/plc.uanodeset loaded”
*$arlogsys:EventID -2147453228 (WARNING, 0, 30420), lpBin=0x00000000, “ROOT”, “”

Many Thanks

Marco Sartori

Hello @mSartoriOptrel,

thanks for the try.
Since tasks aren’t activated but the boot behavior is still the same, I think the root cause lies somewhere in the system or the system’s configuration.

In that case, like @kovarj mentioned, the best next step would be contacting your local support team (if you don’t have already contact, please start here to find a local office in your region) and provide them the project for reproduction and deeper analysis of the issue.

After the investigation, if possible please let us know the cause for the behavior, I would appreciate that!
Thanks in advance, and best regards!