reflective memory setup in Veristand

[StephenB]

Are you very sure you're installing the 433x custom device correctly? The error code being thrown is literally not possible at all with version 6.3.1 posted online.

[pmac]

I deleted the old 433x custom device files and directories from the Timing and Sync Folder. Then, I followed the installation instructions in the Readme file.

I copied the contents of the newly downloaded Built folder into ...\Public Documents\National Instruments\NI Veristand 2011\Timing and Sync I then deleted the current PXI-433x Devices from the Timing and Sync node of the SDF. To be sure, I then saved the SDF and closed out of Veristand completely, restarted VeriStand, and added PXI-433x Devices back into the Timing and Sync node that I had just cleared.

I then deployed the SDF and saw the same error in the console viewer.

[StephenB]

can you do me a favor and FTP into the target and delete the 433x custom device from the target?

[Jarrod_S.]

... And possibly reboot the target. I've seen custom devices not update before the target reboots, even though the file on disk changed.

[pmac]

I FTP'd into both targets, deleted the 433x Custom Device from each one, and then rebooted both targets. When I deploy the SDF I still get the same error on Controller 2.

PatM

[StephenB]

You must have some sort of software install issue. Can you make sure the contents of the NI VS 2011 Custom Devices Directory and the Timing and Sync directory do not contain multiple duplicates of the 433x device files (XML or LLBs)?

[pmac]

I checked and there are no duplicates in Custom Devices and the only PXIe-433x directory in Timing and Sync has Friday's timestamp (10/18/2013) on the LLB's and today's date on the XML file. There is one file "Custom Devices.xsd" in the Timing and Sync folder dated 3/16/2012.

PatM

[StephenB]

Can you FTP in to your target and get the custom device LLBs and attach them here so I can inspect them?

[pmac]

Here ya go.

[StephenB]

Thanks.

Can you try these attached files (backup or replace the ones on your host computer then redeploy). I'm still expecting the error but hopefully I get more information