Re: R&S CMU200 requires both primary and secondary addresses

dave penkler <[email protected]> Mon, 2 Oct 2023 14:08:19 +0200
Newsgroups gmane.linux.hardware.gpib.general
Message-ID <CAL=kjP1Mw_bmwenXaG+MFHcuhbSEzkjFhtLUVk013=3pXeyeHA@mail.gmail.com>
Hi Michael,
According to the standard if a device implements the extended listener
function LE, as does the CMU200, it must be sent a primary and a secondary
address in order to go into the Listener Addressed State (LADS) and
Listener Active State (LACS) in which it can receive data bytes. The CMU200
base system is configured at secondary address 0, other functional units
can be assigned further secondary addresses.
So according to the standard a device implementing the extended listener
function can not respond when it has only been addressed with the PID.
In ibdev when sad==0 then no secondary address is sent, when sad==96+N it
sends the secondary address 0+N when addressing the device.
/d

On Sun, 1 Oct 2023 at 23:44, Michael K via Linux-gpib-general <
[email protected]> wrote:

> I have been trying to talk to a Rhode and Schwarz CMU200 Communication
> test set.
> After several hours of grief, I found that the device does respond if I
> address it with both the primary AND secondary addresses but not if I use
> the PID alone (with ibtest)
>
> $ ibterm -p 22 -s 96
>
> (ibtest doesn't seem to have a way of setting the secondary address.)
>
> Is it normal (allowed) for a GPIB (IEEE 488.2) device to not respond to a
> command when only addressed with the PID?
> I can't find any reference to this in the manual for the CMU200.
>
> Michael
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

_______________________________________________
Linux-gpib-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-gpib-general