Cannot Copy Configuration from RT Target

[TurboPhil]

I am running LV2009 on a Host PC/PXI RT controller system, and I would like to set up a way to programmatically backup the full DAQmx system calibration of the RT Target. I have tried using the MAX Copy Configuration.vi but I keep getting the following error:

Here is the full snippet of code I am trying to run:

I have verified that I can connect to the RT Target at 192.168.1.2 from MAX, and I can even successfully export a MAX Report (HTML/XML) from the remote system, but I keep getting this "network error" when I try to copy the configuration.

Any suggestions?

[muks]

****Message deleted***

Message Edited by muks on 01-06-2010 01:51 PM

[Smootastic]

Hi TurboPhil,

The documentation doesn't seem to imply whether or not this will work for an RT controller, for now just use the manual export process. 

[Smootastic]

Hi TurboPhil,

What version of MAX are you using?  You can get it from Help»About in MAX. 

[TurboPhil]

I'm running MAX version 4.6

The documentation for MAX Copy Configuration.vi specifies that either the Source or Destination inputs can be a machine name or IP address, so I would assume that would be applicable in this case. But you're right, it makes no mention of compatibility with Pharlap RTOS.

I would really like to find a way to programmatically export the configuration from an RT controller because I want to automate the process. I'd really like to put a system in place to back up the configuration (especially for calibration information, or for when new channels are added) in case of a system failure (our older FAT32 PXI controllers are prone to MAX database corruption, among other things). Ideally, anytime anyone modifies the MAX configuration, he/she will manually export the config. The programmatic solution would just be a redundant backup for those non-deal situations.

[Wayne.C]

TurboPhil,

Pretty sure you need to use Real-Time Target System Replication.  Info found here . 

[TurboPhil]

Wayne,

I appreciate the tip. However, I do already use RT System Replication tools to create regular backups of the full RT Target image. I would just like to supplement that with an additional program to backup only the MAX configuration for those situations when I might not want to redeploy the entire system image. For example, I recently replaced one of my PXI controllers and updated from LV8.6 to 2009, but didn't realize that some of the channel information had been changed and not backed up beforehand. I had a full system image from the old controller that I could have deployed to the new one, but I did not want to mix 8.6/2009 RT versions. It would have been nice to have a separate backup just of the MAX configuration in that instance. There have been other circumstances where I needed this functionality as well.

[Wayne.C]

TurboPhil,

Fog is lifting.  Try wiring up the 'product' terminal on MAX Copy Config.vi  .  When this terminal is left unwired, MAX attempts to export everything.  In your case 'daqmx' is the product.  You might also try running your vi on the target as a test to see what happens.  Just replace the IP address with 'localhost'.  I also seem to remember that the target file can't already exist.

[Smootastic]

Hi TurboPhil,

I was able to replicate this error and the information has been placed with Corrective Action Request #110099.  Thanks so much for your feedback!