scpi/usbtmc: fix remote locking according to USBTMC spec
According to USBTMC usb488 subclass spec, wValue hast to be 0 for both LOCAL_LOCKOUT and GO_TO_LOCAL. At least required for R&S HMO1002, the bad request results in a STALL. Fixes bug #783.
This commit is contained in:
parent
3db03efa4a
commit
66836720f7
|
@ -238,7 +238,7 @@ static int scpi_usbtmc_remote(struct scpi_usbtmc_libusb *uscpi)
|
|||
LIBUSB_ENDPOINT_IN |
|
||||
LIBUSB_REQUEST_TYPE_CLASS |
|
||||
LIBUSB_RECIPIENT_INTERFACE,
|
||||
LOCAL_LOCKOUT, 1,
|
||||
LOCAL_LOCKOUT, 0,
|
||||
uscpi->interface,
|
||||
&status, 1,
|
||||
TRANSFER_TIMEOUT);
|
||||
|
@ -276,7 +276,7 @@ static void scpi_usbtmc_local(struct scpi_usbtmc_libusb *uscpi)
|
|||
LIBUSB_ENDPOINT_IN |
|
||||
LIBUSB_REQUEST_TYPE_CLASS |
|
||||
LIBUSB_RECIPIENT_INTERFACE,
|
||||
GO_TO_LOCAL, 1,
|
||||
GO_TO_LOCAL, 0,
|
||||
uscpi->interface,
|
||||
&status, 1,
|
||||
TRANSFER_TIMEOUT);
|
||||
|
|
Loading…
Reference in New Issue