Trigger routing error with LabVIEW DSA example

[Chris_12345]

I've run into a problem when using the LabVIEW example "Multi Device Sync-AI-Shared Timebase & Trig-DSA.vi" that ships with LabVIEW.  I have a PXI-1006 chassis loaded with PXI-4474 cards, and a MXI-3 link to a host computer.  I am looking to acquire data continuously and synchronously from my set of PXI-4472 cards.  I am using NI-DAQ 7.4.  I have written working software that does the synchronization in Traditional DAQ, but I am trying to switch over to DAQmx.

I am getting Error -89136 ("Specified route cannot be satisfied, because the hardware does not support it").  I am aware that the master device must be in Slot 2, and I checked to make sure that Dev2 is in Slot 2, and Dev3 is in Slot 3.  As Pic1.jpg shows, the master is Dev2, and the slave is Dev3.

Pic3.jpg shows that the PXI Bridge is all configured.  Interestingly, the Device Location information is all Unknown.

Any thoughts on what could be causing this Errror -89136?

Thanks,
Chris

[lrallen]

Chris,

Thank you for contacting National Instruments.  The first thing we need to do is get your system configured correctly.  It will not be possible to synchronize these boards until that is done.  This appears to be the source of your error also.  So lets try this.  In MAX, delete ALL of your DAQmx devices and your PXI Chassis.  Next, uninstall all of your devices in the Windows device manager.  Finally reboot your PC and let windows configure the hardware automatically.  When this is done, reconfigure your chassis in MAX.  Hopefully, now the devices will show up correctly in MAX and you can try running your application again.  If either of these still do not work correctly, please let me know.  For more information on PXI chassis configuration, see the link below.  Thanks and have a great day!

http://ae.natinst.com/operations/ae/public.nsf/web/searchinternal/5367fb4224b3ddf586256ed30051b75e?O...

Regards,

Lon A.

[reddog]

Once you have your PXI configuration problems worked out, you might also be interested to know that with DSA boards, you can create tasks with channels that span multiple devices.  The driver will automatically take care of synchronizing the timing and triggering for you.  This will greatly reduce the number of tasks that you need to create and simplify your programming in general.  To play around with this, just open any of the standard shipping examples for a single device and create channels from two separate devices (e.g. Dev1/ai0,Dev2/ai0).  This feature in effect allows you to treat N physical devices as one virtual device.

[MES]

I have this same error when my code reaches the starttask command.  "route cannot be satisfied, because the hardward does not support it."  However, I only have one board (6534), which is currently being simulated in MAX.  Would this be a configuration issue of some sort as well?  If so, I can't just let windows set it up like was mentioned before, as it is a simulated device.

Thanks,  MES

Can you not start a task programmatically on a simulated device?  I assumed you could because you can create and start tasks in MAX. 

Message Edited by MES on 03-29-2006 01:00 PM

[MES]

Please excuse my prior post.  I think I'm starting to understand all of this device routes tab business.  I think I can work it out.