Don A couple of comments. I have the old ethernet 100 also. As I recall it would only work up until windows 98 or 2000.. But to your point my speculation is thats coding at the application level. And that the driver should understand that. To me it makes sense that it appears as 2 gpib masters and separate segments. I would believe that there is an explicit address on the PC side of the system that you would need to direct queries to either master. Regards Paul WB8TSL
On Tue, Nov 19, 2013 at 11:00 AM, Don@True-Cal <[email protected]>wrote: > Hello All, > > I recently added a second NI GPIB-ENET/100 to my instrumentation lab. This > addition was a better approach than extending a single GPIB bus into two > separate lab areas separated by ~30-feet. This new setup is working well > but > however gives me two GPIB bus "segments" named GPIB0::xx and GPIB1::xx. I > have always just been able to address the simple GPIB device address xx in > EZGPIB code like: > const HP3458=24; > SR620=16; > > Now these two devices are on different segments and have the names > GPIB0::16 > and GPIB1::24. I can talk to any device on the GPIB0 segment by just using > the simple device address as always, but what code syntax do I have to add > to address devices on the GPIB1 segment. I have not been successful finding > any reference to this GPIB addressing issue. > > Thanks... > Don > > > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
