开云体育

Steve and all,
Thank you for elaborating on the topic. It's really useful to put some good
detail and get a better understanding of the general rules and mechanisms
of the protocol. Steve - thank you very much for pointing me to your
excellent manual.

I am aware of setting a certain "GPIB address" (I've set it myself on a few
instruments, and that was in order to avoid conflicting same addresses on
multiple units in my environment). I decided as a matter of "intake" to set
a unique address to each instrument that lands at my bench and may stay.

For the connected TDS754D, here's what my list of devices looks like (see
below). Please note though, that the GPIB address set for the scope is
"14," and not "4" (which is the reason why I interpreted it as "landing" on
#4, as opposed to a deliberate process). I believe some GPIB addresses for
different instruments previously connected to the computer would be "07,"
"08," "29" below (I'm not sure why there's two GPIB_07...). The TDS754D
seems to not report its own GPIB #(?)... It does state its firmware version
though.

(visa) list
( 0) USB0::0x03EB::0x2065::GPIB_07_55137323934351C07071::0::INSTR
( 1) USB0::0x03EB::0x2065::GPIB_07_75935323239351A0F1F0::0::INSTR
( 2) USB0::0x03EB::0x2065::GPIB_08_55137323934351C07071::0::INSTR
( 3) USB0::0x03EB::0x2065::GPIB_29_55137323934351C07071::0::INSTR
( 4) USB0::0x03EB::0x2065::TEKTRONIX_TDS_754D_0_CF_91.1CT_FV_v6.3e::0::INSTR
(visa)

My initial question was meant to ask a slightly different thing though (I
did a bad job explaining). Is it customary to just plug GPIB into a running
instrument while making sure the address is different than any other
(previously) connected instrument, and then start to talk to the
instrument through it? Or doing it while the instrument is off is a safer,
"best practice" procedure?

I probably am overthinking this, but I typically try to learn a process
correctly, rather than trial and error, if I can. Also, hopefully my
question is better phrased this time around.
Radu.

<>
Virus-free.www.avg.com
<>
<#m_-1007817960827559090_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, Mar 23, 2025 at 4:27?AM Steve Hendrix via groups.io <SteveHx=
[email protected]> wrote:

On 2025-03-22 10:11 PM, Radu Bogdan Dicher via groups.io wrote:

If I understand correctly, you're saying that the # GPIB connection may
"port" another, "hot swapped" instrument to the same # GPIB?

GPIB doesn't have the concept of a "connection". Each device sets its
own address, sometimes via DIP switches, sometimes, via front panel
commands, etc., but that instrument "knows" its own address. It's up to
the user to ensure there are no collisions. There are 31 available
addresses - often set by 5 DIP switches. The 32nd address is reserved as
described below. The whole concept is quite different from either USB or
Ethernet addressing.

To start a data transfer (which may be a command, or some sort of data),
the Controller (usually a PC adapter of some sort these days; could be
an internal board with special drivers, or external like my KISS-488)
issues a command to one address (maybe even itself) to become the
Talker, and to one or more devices (instruments) to become a Listener.
The talker then proceeds to send bytes, ending with a specified
termination condition. The Controller usually then turns the bus around,
addressing e.g. the instrument to become Talker, and e.g. itself as
Listener, and data flows the other way. at the end, it issues Untalk and
Unlisten commands (that 32nd address).

I include a fairly detailed discussion of GPIB concepts in the beginning
of the manual for my KISS-488, which you can download freely at



Steve Hendrix