NI System Configuration API

[viScience]

Well the problem is that after you do the System Configuration 5.0 Install then your ability do use MAX to do a software install on a formated cRIO is totally hosed up and requires either LVRT2011 or some delicate subinstallation surgery that I could not fathom.  Can't we just have a new syscfg.lvlib to fix the problem?

[JoshuaP]

The lvlib is just a simple wrapper that calls in to a collection of DLL's that do all of the actual work.  So, a new syscfg.lvlib wouldn't fix the issue and you can't just copy DLL's around since their dependencies would most likly not be met.

[viScience]

I am trying to deploy a cRIO image using the API and am getting the following console out error after deployment and reboot.

If I use the RTAD utility everything work fine.  In the boot sequence it appears that the line:

* Loading nidp_target_end.out: nidp_target_end

appears out of sequence to where it is located on the 'good' RTAD deployment reboot.  I am wondering if the startup script? has become lost or mangled.

Loading LVRT...

* Loading nirtdm.out: nirtdm

* Loading nimdnsResponder.out: nimdnsResponder

* Loading vxfpsup.out: vxfpsup

* Loading tsengine.out: tsengine

Time sync source: ptp now active

* Loading nisvcloc.out: nisvcloc

* Loading RTWebServer.out: RTWebServer

System Web Server started

* Loading mxssvr.out: mxssvr

* Loading /tmp/webservices/NI/nisysapi/nisysapisvc.out: nisysapisvc

* Loading nisysapirpc.out: nisysapirpc

* Loading NiViSrvr.out: NiViSrvr

* Loading NiRioRpc.out: NiRioRpc

* Loading nivissvc.out: nivissvc

* Loading nivision.out: nivision

NI-RIO Server 3.6 started successfully.

* Loading niserial.out: niserial

* Loading taggerrt.out: taggerrt

NI-VISA Server 5.0 started successfully.

* Loading nidp_target_end.out: nidp_target_end

NI-Industrial Communications for EtherCAT 2.0 started successfully.

Assertion failed: px != 0, file d:/P4/Perforce/ThirdPartyExports/boost/export/1.

3/1.3.5f1/includes/boost/shared_ptr.hpp, line 375

[viScience]

It appears that the System Configuration API is bent on damaging certain XML files when creating an image from a cRIO target. For example the ECATMaster__0.xml and ECATSlave__0__0.xml files are present but most or all of the content is not there.  So I am curious...Is this another one of those 'known' issues that only NI knows about?

[Justin_E]

Hi sachsm,

Can you send us the image you're trying to deploy to your cRIO that's giving you errors with System Configuration API? You can upload it to our FTP here:

ftp://ftp.ni.com/incoming

Post here with the name of the file and we'll see if we can reproduce the issue. Thanks!

[DaBenny]

Hi,

Can anybody tell me where I find the changelog of Ni System Configuration 1.2?

What are the improvements of this relase?

[viScience]

Ok, I have uploaded the file:

cRIO-SVU 1_0_0.lvappimg to the incoming directory.

You can use the standard RTAD utility to load this file to a cRIO (9074) + 9144 etherCAT.  The problem I am seeing with the API occurs when I retrieve

the image from the cRIO.  It appears to damage the previously mentioned xml files.

[viScience]

Any luck yet reproducing the image corruption problem?

[Justin_E]

sachsm,

Yep I've been able to reproduce the issue. We'll look into why this is happening.

DaBenny,

We post a Known Issues List and a Bug Fix List for System Configuration. I will provide links to these once they're available.

[Justin_E]

Links to Known Issues Lists and Bug Fix Lists:

MAX/SysCfg 5.0 Known Issues:

http://zone.ni.com/devzone/cda/tut/p/id/13303

MAX Bug Fixes:

http://digital.ni.com/public.nsf/allkb/4DA2BCEF4200FF1B862573A600741AF9?OpenDocument

SysCfg Bug Fixes:

http://digital.ni.com/public.nsf/allkb/98D42543957D9758862577DD005B6785?OpenDocument