In most cases such devices come with list_devices or get_devices_number functions, which give the necessary information.Īfter communication is done, the connection needs to be closed, since in most cases it can only be opened in one program or part of the script at a time. More complicated devices using custom DLLs (usually cameras or some translation stages) will have more unique methods of addressing individual devices: serial number, device index, device ID, etc. VegaPowerMeter (( "COM3", 38400 )) # explicitly specifying the correct baud rate > meter. close () # need to close the connection before reopening > meter = Ophir. OphirBackendError : backend exception : 'timeout during read' > meter. get_power () # let us assume that the devices is currently set up with 38400 baud. VegaPowerMeter ( "COM3" ) # for this power meter 9600 baud are used by default > meter. > from vices import Ophir > meter = Ophir.
If it is provided incorrectly, then no communication can be done, and requests will typically return a timeout error: By default, the devices would use the baud rate which is most common for them, but in some cases (e.g., if the device baud rate can be changed), you might need to provide it explicitly. The baud rates are, similarly, provided as a tuple: ("COM1", 19200). The most common situations are ports for the network connection and baud rates for the serial connections. However, sometimes the connection might require some additional information.
In most cases, the connection address is all you need. Usually, it is set on the device front panel or using some kind of configuration tool and a different connection, such as serial or USB. Network devices do not easily provide such functionality (and there are, in principle, many unrelated devices connected to the network), so you might need to learn the device IP elsewhere. list_backend_resources ( "serial" ) # list serial port resources > pll.
0 kommentar(er)
