Ori, thank you very much for your fruitful coments. I accept them according
to my experience and think I've found a solution.
Just another question, if you don't mind. The devices attached to the board
(gsm simulators) have their own keyboard which is disabled when in gpib
mode, interacting with the computer.
When the application exits, I close the gpib mode (ibonl(device, 0), but
still, the control does not return to the device's keyboard and a user needs
to make a manual reset to gain control again.
Can you think what should I do more to achhieve this goal? is this a
linux-gpib driver function that I have to call or do I have to "write" a
command to gsm simulator that should do this prior to closing the gpib
connection.
I know you probably did not work with this specific device, but may be you
encountered a similar problem with other devices with the same feature of
keyboard.
Thanks, Rafi.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Ori Idan
Sent: Sunday, December 24, 2006 9:22 AM
To: Rafi Cohen
Cc: [EMAIL PROTECTED] Org. Il
Subject: Re: FW: primary address of devices
1. When issuing an ibfind (or ibdev) command, no hardware access is done
so no error will be returned. however if you write or read to/from the
device, the results are unpredictable.
2. IEEE4888.2 provides a way to enumerate the devices, I do not recall how
it is done. However not all devices support it.
3. The name is not related to the device itself so you can call it any
name you want.
4. Your other mail contained a question about select and gpib library, I
think you can use select like you use on any other file or socket, however I
have never tried it myself.
In GPIB usually you do not need asynchronous transfer since devices never
talk on their own will but allways as a result of the master issuing a query
command.
Disclaimer: All the above is written from my knowledge of GPIB (I have
used GPIB for more then 10 years) not with knowledge about this specific
library.
--
Ori Idan
On 12/24/06, Rafi Cohen <[EMAIL PROTECTED]> wrote:
Hi list, I hope the following is not too offtopic and if it is, feel
free to answer privately.
Does anybody happen to know or work with linux-gpib driver? you may find
details on http://linux-gpib.sourceforge.net.
Ive sent the following 2 messages to the linux-gpib-general mailing
list, but nobody answered me up to now.
I hope somebody on this list may help me.
I forward this message and another one, relating to 2 different
subjects.
Thanks, Rafi.
-Original Message-
From: Rafi Cohen [mailto:[EMAIL PROTECTED]
Sent: Monday, December 18, 2006 1:08 PM
To: [EMAIL PROTECTED] Sourceforge. Net
Subject: primary address of devices
Hi, sorry in advance if some of my questions are too basic and even
not logic.
My application needs to support connecting up to 30 devices (actually
gsm simulators) to the gpib board in the computer.
All those devices have the same primary address (pad) of 14 and no
secondary addrss.
They have a way to modify in advance their pad. However:
1. If I did not modify the pad of those devices and left all of them
with 14, what would happen if I issue an ibdev() in my application?
will it return an error or there will be an attempt to open one of the
devices?
The second option would be excelent as immediately after openning any
device with this pad, I could issue an ibpad() to change it's pad to any
other address except 14, but logically I believe the first option will
happen.
2. Is there a way for the application to obtain the pad of any device
connected to the gpib board _before_ openning this device thru ibdev() or
ibfind()?
Is there any function that does this or should I manually input this
pad either to the application or to the gpib.conf file?
3. If I want to open a device using ibfind() thru it's name as entered
in the gpib.conf file,
am I free to give whatever name to each device or is there a
limitation for this name to match something related to the device?
I hope my questions are clear, thanks, Rafi.
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.15.26/600 - Release Date: 12/23/2006
4:47 PM
