gpt4 book ai didi

linux - pyUSB read() 总是返回相同的值

转载 作者:太空宇宙 更新时间:2023-11-04 11:49:28 27 4
gpt4 key购买 nike

我在 python 中使用 USB 库。我可以看到设备,我可以配置它。但是当我读出它时,我总是得到相同的东西数组('B',[17、96])。请注意,即使我不写入端点输出,我在读取时仍然会得到相同的结果;我也可以阅读任意多次,但仍会得到相同的结果(请参阅下面的完整代码)

lsusb 命令显示它是一个 FTDI USB 设备总线 009 设备 008:ID 0403:faf0 Future Technology Devices International, Ltd

过去,我可以与其他 USB 设备通信吗?我不明白这个是怎么回事。有人能指出正确的方向吗?我调查了pylibftdi但我什至看不到带有 pylibftdi 库的这个 USB 设备。

>>> import usb
serial_number = '83836244'
dev = None
devices = list(usb.core.find(idVendor=0x0403, idProduct=0xFAF0, find_all = True))
for dev in devices:
if dev.serial_number == serial_number:
break
dev = dev


reattach = False
if self.dev.is_kernel_driver_active(0):
reattach = True
self.dev.detach_kernel_driver(0)
# set the active configuration. With no arguments, the first
# configuration will be the active one
self.dev.set_configuration()
# get an endpoint instance
cfg = self.dev.get_active_configuration()
intf = cfg[(1,1)]
epo = usb.util.find_descriptor(
intf,
# match the first OUT endpoint
custom_match = \
lambda e: \
usb.util.endpoint_direction(e.bEndpointAddress) == \
usb.util.ENDPOINT_OUT)

epi = usb.util.find_descriptor(
intf,
# match the first IN endpoint
custom_match = \
lambda e: \
usb.util.endpoint_direction(e.bEndpointAddress) == \
usb.util.ENDPOINT_IN)

assert self.epo is not None
assert self.epi is not None
epi.wMaxPacketSize = 72000
epo.wMaxPacketSize = 72000
epi.bmAttributes = 1
epi.bInterval = 100
usb_buff = int(self.epi.wMaxPacketSize/100)

dev.read(epi,100,1000)

array('B', [17, 96])

后端:

In [10]: motor.dev.backend
Out[10]: <usb.backend.libusb1._LibUSB at 0x7fc2da558190>

端点:

In [13]: motor.epi
Out[13]: <ENDPOINT 0x81: Bulk IN>

In [14]: motor.epo
Out[14]: <ENDPOINT 0x2: Bulk OUT>

可能与this question有关

我需要在我的电脑上安装合适的驱动程序吗 the FTDI website

我知道通信协议(protocol),将此 USB 设备切换到 VCP(虚拟 COM 端口)后,我能够在 Windows 上与其通信。通过这样做,我丢失了存储在 USB 芯片上并且在设备处于 VCP 模式时无法访问的序列号等信息。我也想从 Windows 切换到 Linux。

我调查了目前哪些驱动程序绑定(bind)到我的 USB 电机 Controller ,结果是空的。

lsusb -t
/: Bus 10.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M
/: Bus 09.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 2: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 3: Dev 5, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 4: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 5: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 6: Dev 8, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 2: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 3: Dev 5, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 4: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 5: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 6: Dev 8, If 0, Class=Vendor Specific Class, Driver=, 12M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 2: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 3: Dev 5, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 4: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 5: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 6: Dev 8, If 0, Class=Vendor Specific Class, Driver=, 12M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M
|__ Port 5: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 6: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 12: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M

我想知道我是否需要将特定驱动程序绑定(bind)到我的电机 Controller 。

最佳答案

我无法访问您的硬件,但我认为您的 libftdi/pylibftdi 问题可能与此类似:

Failed to Connect FT232RL Device with Pylibftdi (Thorlabs APT DC Motor Controller)

Thorlab 的 APT 协议(protocol)似乎有几种实现方式。看这个例子:https://github.com/MaxP92/thorlabs_python_low-level

您可能会为您的项目回收一些东西。

我猜你有理由使用 FTDI 设备的 USB 端,但我不相信无法从串行设备访问序列号。根据protocol manual ,有一个 MGMSG_HW_GET_INFO 命令,它应该为您提供序列号、型号、固件版本等信息。再说一次,我没有硬件来尝试这个,但也许你可以看看这个主意。

关于linux - pyUSB read() 总是返回相同的值,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/56486431/

27 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com