Hello Frank
Thanks for coming back to me about this issue. I have one bad and one
good news:
The bad one is that my radio test set exploded this morning releasing a
bunch of magic smoke... it was probably too stressed this long and rainy
weekend :-)
Anyway, it's going to be repaired sooner or later (probably later).
The good one is that I picked up another test equipment and I did the
test you asked...and this time it worked. There are a couple of things I
learned from that: I need to clear the instrument buffer. I have created
a python script that showed me this behavior.
Still, I don't know why ibtest did not work with the other device. I
never managed to get anything from it using the PCI board. Maybe it does
need some "special" termination strings or some different timings. Once
repaired, I will try to hook a logic analyzer. If interesting, will
publish some results here
https://github.com/daturach/Documentation/wiki/GPIB-interface-(Marconi-2955)
Thanks
Walter
Test, see below
$ ibtest
Do you wish to open a (d)evice or an interface (b)oard?
(you probably want to open a device): d
enter primary gpib address for device you wish to open [0-30]: 6
trying to open pad = 6 on /dev/gpib0 ...
You can:
w(a)it for an event
write (c)ommand bytes to bus (system controller only)
send (d)evice clear (device only)
change remote (e)nable line (system controller only)
(g)o to standby (release ATN line, system controller only)
send (i)nterface clear (system controller only)
ta(k)e control (assert ATN line, system controller only)
get bus (l)ine status (board only)
go to local (m)ode
change end (o)f transmission configuration
(q)uit
(r)ead string
perform (s)erial poll (device only)
change (t)imeout on io operations
request ser(v)ice (board only)
(w)rite data string
send group e(x)ecute trigger (device only)
: w
enter a string to send to your device: id?
sending string: id?
gpib status is:
ibsta = 0x2100 < END CMPL >
iberr= 0
ibcntl = 4
You can:
w(a)it for an event
write (c)ommand bytes to bus (system controller only)
send (d)evice clear (device only)
change remote (e)nable line (system controller only)
(g)o to standby (release ATN line, system controller only)
send (i)nterface clear (system controller only)
ta(k)e control (assert ATN line, system controller only)
get bus (l)ine status (board only)
go to local (m)ode
change end (o)f transmission configuration
(q)uit
(r)ead string
perform (s)erial poll (device only)
change (t)imeout on io operations
request ser(v)ice (board only)
(w)rite data string
send group e(x)ecute trigger (device only)
: r
enter maximum number of bytes to read [1024]: 23
trying to read 23 bytes from device...
received string: 'PM6666/016/32
VMAX 00'
Number of bytes read: 23
gpib status is:
ibsta = 0x100 < CMPL >
iberr= 0
ibcntl = 23
You can:
w(a)it for an event
write (c)ommand bytes to bus (system controller only)
send (d)evice clear (device only)
change remote (e)nable line (system controller only)
(g)o to standby (release ATN line, system controller only)
send (i)nterface clear (system controller only)
ta(k)e control (assert ATN line, system controller only)
get bus (l)ine status (board only)
go to local (m)ode
change end (o)f transmission configuration
(q)uit
(r)ead string
perform (s)erial poll (device only)
change (t)imeout on io operations
request ser(v)ice (board only)
(w)rite data string
send group e(x)ecute trigger (device only)
: q
demo@antix1:~/gpib
On 10.06.2019 21:38, Frank Mori Hess wrote:
> On Mon, Jun 10, 2019 at 10:08 AM W <[email protected]> wrote:
>> Still no luck...some more tests/info: basically there is no communication between PC and device. The PCI board is recognized and communication seems to work between PC and board. I can confirm the device works but not via this board.
>>
>> Anything else I can check?
> Would you send the full console output of ibtest from when you first
> start it until the timeout?
_______________________________________________
Linux-gpib-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.