Issue with NI-Switch Driver (Error – 1074135030)

[Matt.M]

Hey Greg,

Can you try using the switch card in a real-time project?

1. Create a new project.

2. Add the PXI as a real-time target and connect to it. (You need to be connected to it for the next steps)

3. Add a vi under the PXI target and add a NI-Swith Initialize and Close, and connect them correctly.

4. Create a constant for the resource name, you should be able to use the dropdown box to select the correct slot.  (If this isn't available then this is definitely some kind of driver issue.

5. Run the VI and verify you don't get any errors.

If you receive any errors or run into trouble please screenshot the issue and include it with your post.

Regards,

Matt M.

[Greg_Campeau]

After I created and saved the vi, I clicked on the resource name constant.  Only the Refresh choice appeared in its drop-down menu. 

(See TestNIswitchInitializeAndClose_ver1a_NothingInResourceConstantDropDown.jpg)

Then, I manually typed-in the name of the first PXI-2586 relay card in the PXI chassis (PXI1Slot9) into the resource constant's field and clicked the Run button.  A dialog box appeared, saying it successfully deployed.

(See TestNIswitch_ver1a_deployedAfterPXI1Slot9isManuallyEntered.jpg)

After closing the deployment dialog box, I typed an erroneous word into the resource name's field (the word 'blah'), then I clicked the field's drop-down arrow.  Its drop-down menu appeared with all of the PXI-2586 cards in the chassis, I then erased the word 'blah'.

(See  Test_ver1a_ResourceConstantDropDownNowPopulatedAfterDeployment.jpg)

I then selected the 'PXI1Slot9' choice from the drop-down menu, then clicked the run button again.  Once again, a dialog box appeared, saying it successfully deployed.

[Josh_B1]

Hi Greg,

Matt and I were able to run your code on a real time system with the same switch. So your code is good. We suspect that there may be a driver mismatch between the real time target and host computer. Could you send us a MAX technical report from your host computer. The steps to create the report are as follows: 

1. Open Measurement and Automation Explorer
2. Go to File » Create Report...
3. Select Technical support for the report type and click Next.  Some older versions of MAX only have the Simple and Custom report types.  Use the Custom report with all boxes checked to get the same information as the "Technical Support" report with an older version of MAX.
4. You do not need to add any additional files, but you can attach VIs, a LabVIEW project, or screenshots if desired.  To add a file to the report, click on Add... and use the file dialog to browse to the file you want to add.  When you are done attaching files, click Next.
5. Edit the location that you save and the file name to something that clearly labels which computer the report is for, then click Next.

After you do this you can post back with the report and we can take a look.

Regards,

Josh Brown

[Greg_Campeau]

Josh or Matt,

Could one of you email me, so I can get your address? 

I need to email the MAX Tech Report to you, instead of posting it, because one of its files (ni_reg_report.txt) contains SerialNo, RegisteredOwner, and RegisteredOrganization info and I am not certain that the other files do not also contain similar info.

In the interim, I posted a zip file that contains the project and vi files, which pertain to my previous post on 01-23-2012 07:55 PM.

[Greg_Campeau]

Update:

I learned from my employer's IT department that I am permitted to bring my personal netbook into work, as long as I do not connect it to our corporate intranet.  Given this, I did the following:

Before bringing my netbook to work, I performed the following actions in the order as listed:

1. Installed LabVIEW 2011 Base Development System (I personally own a license)
2. Installed NI-Switch 4.4.0
3. Installed the evaluation version of VeriStand 2011
4. Installed the NI VeriStand Add-on - NI-Switch Relay, according to the procedure in its Readme file.
5. Ran NI Update Service

With my netbook at work, I performed the following actions in the order as listed:

1. Under the Windows Firewall section of its Control Panel, I unchecked [Don't allow exceptions]
2. I matched its TCP/IP network settings with the settings of the 2nd network card in my Work PC (Under the General Tab:  [Obtain an IP address automatically] [Obtain DNS server address automatically])  (Under the Alternate Configuration Tab:  [Automatic private IP address])
3. Connected an ethernet cable from the PXI-8110 to the netbook.
4. Rebooted the netbook
5. Powered-on the PXI-chassis
6. After the network icon on the windows toolbar appeared with an Exclamation point and said 'Limited or no connectivity', I opened MAX.
7. Confirmed in MAX that the PXI-Chassis' cards and software could be seen under 'Remote Systems'
8. Closed MAX.
9.  Opened VeriStand.
10.  When the Windows Firewall Dialog box appeared, while VeriStand was opening, I clicked on the 'Unblock' button.
11.  Once VeriStand was open, I opened the 'Sinewave Delay' demo project.
12.  From the Project Explorer, I opened the Sinewave Delay.nivssdf system definition file.
13.  Right-clicked on 'Custom Devices' under 'Controller' in the selection tree, then selected 'NI-Switch Relay'.
14.  Entered 'PXI1Slot9' in the 'Resource Name' field.
15.  Selected '2586/10-SPST' from the 'Topology Name' field's drop-down menu.  [After about 10 seconds, the 'Available Relay' array-field automatically populated.  No error message appeared!  :-)]

See the attached screenshot.

Josh and Matt, when I get your email address, I will also send a MAX Tech Report that I generated on my personal netbook.

My personal netbook's specs are: 

Hardware:  HP mini 311-1000NR with 3GB of Ram

OS: Windows XP Home, ServPk 3

[Josh_B1]

Hi Greg,

I understand why you want to share the report only through email. We do not typically give our emails out on forums. There are really two ways to proceed. Do you have a service contract with us? If so you can create an email service request and note this forum and that you are working with me. You could then attach the report to that email. If you let us know on the forum ahead of time we can be looking for the email and will make sure to get it when it comes trough our system. The second option would be for you to give me permission to look up your email from our Web Support Organization. If you gave me permission to do that I could send you a support email which you could then reply to. Let me know what would work best for you.

Regards,

Josh Brown

[Greg_Campeau]

Oops!  I thought the second option was the default and you did not need my permission. 🙂  I definitely want to avoid having either of our emails floating around in the forums.

I hereby give you (Josh Brown) and all other active National Instrument employees, who have corresponded with me on any of National Instrument's forums, permission to look up my email from National Instrument's Web Support Organization.  Greg Campeau

[Greg_Campeau]

Just following-up Josh.

Have you had an opportunity to review the MAX tech reports?

[Josh_B1]

Hi Greg,

Could you right click on the Real Time PXI chassis and create a report for it. You can send that report to the same email as before. Do you have any real time code that uses the switch? If so we would like you to deploy it on the system and try running it. Do you have a Windows PXI system?

Regards,

Josh B

[Greg_Campeau]

I just sent the MAX tech report for the remote system (Real Time PXI chassis) to the same email as before.

I'll list my answers below your original questions.

Do you have any real time code that uses the switch?

Just the NI-Switch Add-on for VeriStand.

Do you have a Windows PXI system?

The system has two hard-drive partitions.  One with Win7 Embedded OS. The other with the Pharlap Real-Time OS.  It has been booting from the Pharlap OS.  However, when I first received and powered-up the PXI system (October 2011).  It was booting from the Win7 embedded OS.  While it was booting from the Win7 OS, NI tech support helped me resolve an ethernet communication problem, which turned-out to be caused by my IT dept's McAffee security permission settings.  Those permissions were since elevated by my IT dept to resolve that issue.  NI tech support then walked me through a procedure to change the PXI-systems boot-up partition from the Win7 embedded to the Pharlap.