NI MAX 4.1.0.3001 looses trigger mapping settings for my VXI / MXI2 multi mainframe configuration

[Rikh-VXI]

I have NI VXI 3.3.1 and NI VISA 4.0 installed on the system and I am attempting to use a MXI 2 multi mainframe configuration.

NI MAX sees all the hardware correctly but when I set the MXI-2 Signal Mappings for the TTL Triggers then re-run resman these settings are not retained.  This worked flawlessly in VISA 2.6 (my prior version).

Specfic config information..

frame 1 -

slot 0 MXI2 LA1

slot 2 1432A LA 66

Frame 2

Slot 0 MXI2 LA 129

Slot 2 1432 LA 133

NI-VXI version 3.3.1 installed.

Thank you for any help you can provide!

Message Edited by Rikh-VXI on 06-12-2008 03:43 PM

[TobyHex]

Hello Rikh-VXI,
Looking into your issue a bit more I was able to find a KnowledgeBase [link removed; article no longer available] that explains the differences in TTL mapping in NI-VXI versions 2.x and 3.x. Please let me know if this information proves to be useful and have a great day!
Regards,

Nicholas K

[Rikh-VXI]

Nicholas_K,

I understand how to map the trig lines in MAX, and was able to successfully configure these mappings.  The issue is that once configured, I re-run resman and the mappings are then lost, returned to "NONE".  I'm not sure but it appears to be a bug.

Thank you,

Rikh

[TobyHex]

Hey Rikh-VXI,
I have tried to re-create this your setup on our test machine and so far I am unable to get it to reproduce the same problem you are experiencing. Just to get some more background information from you, was there a specific reason for the upgrade to the newer version of NI-VXI and NI-VISA.
Regards,

Nicholas K