Hi Sarah,
Thanks for taking a look at this, but I don't think there is anything wrong on the NI side.
Here is a list of behaviours I have observed using LabView / NI Instrument Communicator and the RS232 echo terminal. The echo is supposed to just echo everything the unit receives via GPIB over the serial connection, so if I send 'X6', I expect to see 'X6' appear in my serial session:
- GPIB-USB-HS attached directly to the back of the SRS530, no other instruments attached
- The first character of command is consistently not received by the unit, if you want to work around this, you can prepend any single character to the desired command
- GPIB-USB-HS attached to a 1m GPIB cable and to the SR530, no other instruments attached
- All commands work perfectly, no characters are dropped
- GPIB-USB-HS attached to the SRS530 and another instrument with 1m GPIB cable
- As soon as the other instrument's power is connected, the commands to the SR530 are no longer received properly. For instance I will try to write the command 'X6' multiple times, and each time I send it I see a (seemingly random,) different result: '<blank>', 'X', '<double quotes>', 'P&', 'X','6','&' and so on...
- Commands to the other unit are received and executed successfully.
- I have tried an XL3120 frequency counter, and an Agilent 34401A multimeter as the second intrument -- same results.
I didn't really encounter any errors per se, but if I tried to read the result after one of the truncated or garbled commands, there would be a timeout since the unit never understood the command.
Some other observations
- I tried to solder the 270 pF cap to the GPIB chip, as suggested by this and other threads, only to find that the cap was already there, so they must be doing that at the factory now!
- I have also tried to get some help from SRS, they informed me that their units are calibrated through GPIB so there can't be anything wrong with it.
So I am basically wondering if anyone else has tried this and got it working?