Got a bit of an issue and would like to ask for debugging help. I tried using TestController over a Nano based AR488 with an HP 34410A DMM connected to a laptop and it doesn't work.
Using the AR488 Utility it is possible to talk with the nano and to identify the DMM configured at address 1 on the GPIB.
Date,COM #,Status,Message
9:33:02 pm,COM7,Send,++ver
9:33:02 pm,COM7,Recieved,"AR488 GPIB controller, ver. 0.51.18, 26/02/2023"
9:33:11 pm,COM7,Send,*idn?
9:33:12 pm,COM7,Send,++read
9:33:12 pm,COM7,Recieved,"HEWLETT-PACKARD,34401A,0,9-5-2"
However using TestController (latest verion) it cannot identify the DMM
;; AR488 B:1 Device HEWLETT-PACKARD,34401A, do not match: null
Tried a second nano on the same PCB and same issue. The PCB seems ok, no shorts, solder joints are fine and connections from arduino to the GPIB connector measure ok.
I've been using a Pro Micro based AR488 with the same HP 34410A DMM on the same laptop and that just works fine. Therefor I think my software is configured correctly. AR488 Utility gives exactly the same reply and TC configured according to the different virtual COM port van identify the DMM and return measurements fine:
;; Found Agilent 34401A on AR488 A:1
For what it's worth 1: With the Nano the first ++ver message sent always fails. Subsequent messages all work. With the Pro Micro the first message never fails.
For what it's worth 2: The Nano is new old stock and having the 'old' arduino bootloader.
For what it's worth 3: On the Pro Micro the send and receive LED's seem on all the time. Not with the nano.