05-19-2012 03:18 PM
Hi,
I was wondering if there were any documentations/tutorial/guide lines about how create an instrument (not a virtual one) that would be VISA compliant. So this instrument could be connected to a computer and detected by visa as an INSTR resource.
Thank you to anyone who will give some help.
05-19-2012 03:28 PM
05-22-2012 04:55 AM
As for RS232 (Serial), GPIB, and TCP socket interfaces, any instruments equipping them are all VISA compatible, because VISA does not implement higher logical protoccols on them. But recommend to implement at least *IDN? command so that your instrument can be identified by NI-MAX etc.
As for other higher protocol such as VXI-11 (LAN), HiSLIP (LAN), USBTMC (USB2.0), your instrument must be compliant with each specification as Dennis mentioned.
As for command languages, SCPI or IEEE488.2 command systems are recommended but not mandatory for VISA.
Makoto
05-22-2012 04:57 AM
Oh, sorry but, TCP socket interface is not an INSTR resource.
(RS232 and GPIB are still INSTR resources though...)
05-22-2012 05:45 AM
Hi guys,
Thank you for your comments.
I was missing was the LXI and USBTMC words in my googling. Now I can find quite a lot of information. At some point I will post here some links for anyone who is interested.
Thank you again.
05-22-2012 10:35 PM
One important point is, LXI itself is not an I/O protocol. Instead, LXI is a design standard for LAN-based instruments including requirements for hardware, form-factor, front & rear panels, logo licensing, and network operations (DHCP, DNS, WEB, VXI-11, IEEE1588 etc...).
As for programming I/O interfaces that will be concerned to VISA, important protocols are VXI-11 (LAN), HiSLIP (LAN), and USBTMC (USB2.0). Plus if you want implement defacto-standard SCPI language, refer to SCPI & IEEE488.2 standards too.