blocks|key|4330817|text|在我的经验中，每次将设备插入完全相同的USB端口会导致它获得相同的COM端口号。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4330818|如果您需要将设备插入不同的USB端口，也可以更改分配给设备的端口号(设备管理器，编辑COM端口的属性)。在过去，我会用COM端口号标记设备，然后将其插入我笔记本电脑上的每个USB端口，并将COM端口重新分配为该数字，而不管它插在哪里。|4330819|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my experience, plugging the device into the exact same USB port each time results in it getting the same COM port number.

It's also possible to change the port number assigned to a device (Device Manager, edit Properties of the COM port) if you need to plug it into a different USB port. In the past I have labeled a device with a COM port number, and then plugged it into each USB port on my laptop and reassigned the COM port to be that number, regardless of where it's plugged in.

blocks|key|3850722|text|FTDI驱动程序将根据所连接设备的序列号将串行端口分配给相同的COM端口。因此，无论USB端口是什么，端口都应该保持不变。但是，如果您插入新的USB设备，它将不会重复使用以前分配的COM端口。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3850723|FTDI有一个app+note，更详细地解释了这个过程。|offset|length|3850724|我曾经遇到过多产驱动程序的稳定性问题，所以我不使用多产的USB转串行设备，也不能评论他们的映射策略。|3850725|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ftdichip.com/Support/Documents/AppNotes/AN_123_How%2520COM%2520Ports_Are%2520Allocated%2520on%2520Driver_Installation.pdf^0|0|7|8|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

The FTDI driver will assign serial ports to the same COM ports by the serial number of the device connected. So, the ports should remain the same regardless of USB port. However, if you plug in a new USB device, it will not reuse the previously assigned COM ports.

FTDI has an <a href="http://www.ftdichip.com/Support/Documents/AppNotes/AN_123_How%20COM%20Ports_Are%20Allocated%20on%20Driver_Installation.pdf" rel="noreferrer">app note</a> explaining the process in more detail.

I've had general stability problems with Prolific drivers, so I do not use Prolific USB-to-serial devices and can't comment on their mapping strategy.

blocks|key|3850772|text|使用ComPortMan将COM端口号绑定到设备。下面是一个ComPortMan.INI示例，摘自Help+page|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3850773|[ComPorts10]
DeviceID=USB\VID_067B&PID_2517
PortName=COM5

[ComPorts20]
DeviceID=USB\VID_1234&PID_5678
PortName=COM6|code-block|syntax|javascript|3850774|注意:我发现有时需要在设备ID后附加一个*才能正常工作。|3850775|entityMap|0|LINK|mutability|MUTABLE|url|http://www.uwe-sieber.de/comportman_e.html|1|http://www.uwe-sieber.de/comportman_help_e.html^0|U|E|2|A|0|1D|9|1|0|0|K|1|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]|$9|12|A|13|1|14]]|E|$]]|$1|F|3|G|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]|U|$5|P|Q|R|E|$S|V]]]]

Use <a href="http://www.uwe-sieber.de/comportman_e.html" rel="nofollow noreferrer">ComPortMan</a> to bind COM port numbers to devices. Taken from the <a href="http://www.uwe-sieber.de/comportman_help_e.html" rel="nofollow noreferrer">Help page</a>, here's an example <code>ComPortMan.INI</code>:

<pre><code>[ComPorts10]
DeviceID=USB\VID_067B&amp;PID_2517
PortName=COM5

[ComPorts20]
DeviceID=USB\VID_1234&amp;PID_5678
PortName=COM6
</code></pre>

Note: I've found that sometimes a <code>*</code> needs to be appended to the Device ID for this to work.

blocks|key|14128|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|14129|entityMap^0|0^^$0|@$1|2|3|-4|4|5|6|C|7|@]|8|@]|9|$]]|$1|A|3|-4|4|5|6|D|7|@]|8|@]|9|$]]]|B|$]]

The FTDI config tool can, I believe, set fixed COM port numbers and rename devices to show up as being "Your product name", which makes it easier to find the device programmatically if it does move around (you're not just looking for COM ports).

blocks|key|14150|text|对于XP|type|unstyled|depth|inlineStyleRanges|entityRanges|data|14151|标记usb/com设备的usb端口，反之亦然。或者将usb/com设备逐个插入所有的usb端口，设置相同的设置，这样插入任何一个usb端口都会得到相同的设置。|14152|当心！|14153|如果设置在模式状态下显示或无，则usb硬件设备管理器中的高级端口设置将与模式状态(运行cmd、模式)不同|14154|如果设置正确，真正的9/25引脚串行端口将不会显示在模式状态中，只有那些USB2serial才会显示。如果它没有显示或没有显示正确的速度，打印机将打印有趣的字母，等等。|14155|如果模式状态与设备管理器设置不匹配，特别是波特率，则设备不起作用。除非您的自定义软件可以在通信前预先设置comport。|14156|另一个问题:如果有多个usb2serial，即使是相同的驱动程序也可能会因为它们共享相同的ser2pl.sys而发生故障|14157|使用模式测试usb2serial设备:使用模式设置com？对于硬件或XonXoff，如果显示无或无法设置，则此设备的驱动程序错误或设备部分有故障。它仍然在无检测条件下工作。如果您不需要对硬件进行任何检测，这是可以接受的。示例:+check是打印机联机打印，无将不提供脱机状态，..|14158|为了保存，我现在只使用一个usb2serial设备，并获得主板与2板载或添加串行端口的串行卡，...|14159|更不用说Pl2303+usb了..ca-42和dku-5，最近3个月，每个都只能在不同版本的驱动程序上使用。大多数新电脑只有USB接口。所以我找到了一个手机用的ca-42(com1)和一个打印机用的usb2serial(com2)。我面临着太多的问题。已尝试使用1个pl2303和1个CH340+(不同驱动器)问题，因为ser2pl.sys外观不能与2共享。|14160|目前，正在使用的打印机和usb+pl2303+ca-42(com2)的手机板上的com1，到目前为止，到目前为止，没有问题。祈祷我的手指。|14161|干杯。|14162|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|15|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|16|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|17|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|18|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|19|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1A|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Y|$]]

for XP

tag the usb port for the usb/com device or visa versa.
or put the usb/com device into all usb port one by one, set same setting, so plug into any usb port
will get the same.

beware!

advance port setting in hardware device manager for usb will not same as
mode status (run cmd, mode) if the setting show or none in the mode status

the real 9/25 pins serial port will not show in the mode status, only those USB2serial will be, if got the right setting. if it didn't show up or not show the right speed as for printer will print funny letters, etc.

if mode status not match with the device manager setting especially the bauds rate, then device not function.
unless your custom software can set the comport in advance before communicating.

another issue:
if have multiple usb2serial even same driver can malfunction because they share the same ser2pl.sys 

using mode to test the usb2serial device:
using mode set the com? to hardware or XonXoff, if it show none or it cann't be set, then this device's driver BUGs or device is part faulty.
It still work on NONE detection condition,.. that fine if you do not need any detection of the hardware.
example: check is the printer online for print, NONE will not provide the offline status,..

for save, I am now only use 1 usb2serial device and get motherboard with 2 onboard or add on serial card for serial port,...

not to mention of Pl2303 usb,.. ca-42 &amp; dku-5, have them all for last 3 months
each of it can only use on different version of driver,..
most new PC only has USB ports,.. so I found 1 ca-42(com1) for cell phone &amp; 1 usb2serial(com2) for printer. I have
facing so much problems. tried use 1 pl2303 &amp; 1 CH340 (different drive) problem too because of the ser2pl.sys
look as it not share by 2.

currently, on hand using onboard com1 for printer &amp; usb pl2303 ca-42(com2) for cell phone, so far so good, no problem yet.
cross my fingers.

cheers.

blocks|key|3850742|text|每个FTDI设备都有一个序列号。在软件中，当枚举(循环)可用的FTDI设备时。是的，您可以同时插入多个FTDI设备。请用户选择相应的。设备。并在每次循环访问可用设备时保存和恢复序列号。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3850743|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Every FTDI device has a serial number.. in your software, when enumerating (looping) through the available FTDI devices.. yes you can have many multiple FTDI devices plugged in at once..
ask the user to select the approp. device. and save and restore the serial number each time you loop through the available devices..

blocks|key|3850753|text|使用"FT_INF+2.0.61.242+-自定义INF文件生成器“，并将”初始索引“设置为要分配的第一个COM端口号(例如32)。然后使用新生成的.inf安装FTDI驱动程序(可能需要.cat文件自签名)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3850754|或编辑ftdiport.inf:+FtdiPort.NT.AddService.AddReg+HKR，"Parameters\VID_0403&PID_6001"，"InitialIndex",0x00010001,32|3850755|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Use "FT_INF 2.0.61.242 - Custom INF File Generator"
and set "Initial Index" to the first COM port number to be assigned (e.g. 32).
Then install the FTDI driver using the newly generated .inf (might require .cat file self-signing)

or edit ftdiport.inf:
[FtdiPort.NT.AddService.AddReg]
HKR,"Parameters\VID_0403&amp;PID_6001","InitialIndex",0x00010001,32

blocks|key|3850763|text|如FTDI+following+Application+Note中所述，编辑注册表并创建设置为0x01的REG_BINARY值，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3850764|HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags\IgnoreHWSerNum{De副VID、PID和接口}|3850765|例如：|3850766|IgnoreHWSerNum04030300|3850767|将忽略VID为0403且PID为0300的所有USB设备的序列号。所有这些设备将获取相同的驱动程序和相同的COM端口|3850768|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ftdichip.com/Support/Documents/AppNotes/AN_123_How%2520COM%2520Ports_Are%2520Allocated%2520on%2520Driver_Installation.pdf^0|1|V|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]]]

As described in the <a href="http://www.ftdichip.com/Support/Documents/AppNotes/AN_123_How%20COM%20Ports_Are%20Allocated%20on%20Driver_Installation.pdf" rel="nofollow noreferrer">FTDI following Application Note</a>, edit the Registry and create a REG_BINARY value set to 0x01 as follow:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags\IgnoreHWSerNum{De
vice VID, PID and interface} 

For example:

IgnoreHWSerNum04030300

Will ignore the serial number of all USB devices with VID 0403 and PID 0300. All these devices will acquires the same driver and the same COM Port

I develop embedded systems and need serial ports for communication.

In Windows XP the numbers for USB serial port dongles keep moving around, which makes it hard to use in scripts or makefiles (for example for flash programming NXP controllers via their built-in bootloader, or for controlling a target and two lab devices at the same time).

Is there a way to fix the COM-port for such a dongle? In Linux I can do this via udev by matching against the serial number of FTDI dongles (see <a href="https://stackoverflow.com/a/13741634/49246">this answer I just gave</a> while searching for an answer to this question).

How to get stable COM-ports for USB serial dongles in Windows XP?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我是开发嵌入式系统的，需要串口通信。在Windows XP中，USB串行端口加密狗的编号不断移动，因此很难在脚本或生成文件中使用(例如，用于通过内置引导加载程序对恩智浦控制器进行闪存编程，或用于同时控制一个目标和两个实验室设备)。有没有办法修复这样的加密狗的串口？在Linux中，我可以通过udev来匹配FTDI加密狗的序列号(在搜索这个问题的答案时，请参阅 )。

问如何在Windows XP中为USB串行加密狗获得稳定的串口？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Windows XP中为USB串行加密狗获得稳定的串口？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Windows XP中为USB串行加密狗获得稳定的串口？
EN