09-29-2005 04:27 AM
09-29-2005 06:57 AM
09-29-2005 05:42 PM - edited 09-29-2005 05:42 PM
What I _think_ is that it might work this way, but you have to program that explicitely. Both controllers have to swith the controller in charge in order to gain control on the bus cable.
If communication between controllers are possible, this setup will likely stay as the app on the PC is written long time ago and GPIB based. Actually, I prefer LAN as I am familiar with Winsock programming.
But I'd suggest re-thinking that setup. It is probably much easier to establish another connection (LAN would be easieset) between the two computers. Than you could utilize one of the established mechanisms to communicate and/or control the other app.
Thanks, I will try installing the NI-488.2 ver 2.3 driver that comes with the card. The current driver is 2.4 which I downloaded from NI after reading about the performance issue in 2.3.
To your 2nd Q: Try to find the GPIB IF in MAX (measurement and automation explorer). Try to communicate with it from within MAX before trying anything from LabVIEW.
Message Edited by ccchin on 09-29-2005 05:48 PM
09-30-2005 01:48 AM
09-30-2005
06:01 AM
- last edited on
11-15-2025
04:13 PM
by
Content Cleaner
Hi Lul,
Thanks for your help. I manage to get my GPIB-USB-HS card working by simply reinstalling the 2.4 driver. Previously, I chose "custom" install but this time round "typical" install did the job.
After reading the article at https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x2XtCAI&l=en-US and playing with the Interactive Control uitlity, I managed to get the two controllers to talk to each other.
As mentioned by you, the article also said that one of the two controllers must be set as CIC. However, I managed to get both talking to each other with both controllers set as CIC. For those interested, the following is what I did with my setup as described in my original post:
PCI-GPIB setup: Interface name=GPIB0, PAD=1 , SAD=0, System Controller check, rest default.
GPIB-USB-HS setup: Interface name=GPIB0, PAD=2, SAD=0, System Controller check, rest default.
09-30-2005 11:08 AM
10-02-2005 01:09 AM
Hi Scott,
I had thought the terms SC and CIC are synonymous. It is really perceptive of you to detect and correct my misconception. Thanks to you, I understand better now. Please assist me with some questions that pops into my head while reading your reply.
Q1: In my PC-to-PC setup (both are SC), if PC1 is first configured as CIC by an app when it execute, sometime later another app on PC2 execute and attempts to configure PC2 as CIC using command "ibsic". What will happen? Will CIC on PC1 prevent PC2 from taking over as CIC (since PC1 did not relinquish CIC with "ibpct")? Who will become the CIC?
Q2: Can PC2 (non CIC) open a communication channel to PC1 (CIC) using the "ibdev" command as follows?
: ibfind gpib0 (note that ibsic is not called, so non CIC)
gpib0: ibdev 0, PADPC1, 0, 13, 1, 0 (where PADPC1 is the primary address of gpib card on PC1, the CIC)
ud0: ibwrt "HELLO CIC"
If not, what is the proper way to do it?
Looking forward to your reply to clarify my muddled thoughts. And I can't wait till Monday to test it out back in office. Thanks Scott.
Regards,
Chin
10-02-2005 01:29 AM - edited 10-02-2005 01:29 AM
Message Edited by ccchin on 10-02-2005 01:35 AM