spaghetti_developer Posted July 11, 2012 Report Share Posted July 11, 2012 Hi guys, Every time I connect RS232/USB converter to my USB port, windows sets a new COM number to my device. Now this number became too high and, even though it shouldn't create problems, I would like to reset it and start again from COM2 and go on (the COM1 is the physical RS232 on board of my desktop). Do you know how can I reset this enumerator? Thank you in advance. Quote Link to comment
asbo Posted July 11, 2012 Report Share Posted July 11, 2012 My Coffee cup: How to clear or Reset COM port ? 1188 - RESETTING YOUR COMPUTER'S COM PORT ASSIGNMENT Quote Link to comment
spaghetti_developer Posted July 11, 2012 Author Report Share Posted July 11, 2012 Thank you asbo for the links, I've already read them and I've done a tool that do exactly what it is described on that posts automatically. I think it can be useful for the other users of this group. My software is specific for FTDI converter but I think it can be adapted for any other type of converter easily. Attached the zip with my code! COMPortsEnumCleaner.zip Quote Link to comment
spaghetti_developer Posted July 12, 2012 Author Report Share Posted July 12, 2012 I've made a new version of this software, the difference of this one from the previous is that I've introduced a recursive function to clean the FTDI registry keys instead of the step-by-step clean function which presume you have to know the number of indent keys inside the root key you have passed. I leaved both of the solutions on the project to let you to choose which solution is better for your usage. Switch from one solution to the other is easy, simply change the function FTDI - regKeyCleaner_recursively with the FTDI - regKeyCleaner_byStep. The feed-backs are welcome. COMPortsEnumCleaner_V2.zip Quote Link to comment
Phillip Brooks Posted July 12, 2012 Report Share Posted July 12, 2012 You might be able to change the COM port assignment behavior by using one of the techniques in this document: http://www.ftdichip.com/Support/Documents/AppNotes/AN_123_How%20COM%20Ports_Are%20Allocated%20on%20Driver_Installation.pdf Quote Link to comment
spaghetti_developer Posted July 13, 2012 Author Report Share Posted July 13, 2012 Well, I'd read that document before developed my software. In the document is described how to clean the registry key manually, but how about cleans hundreds of COM ports assigned? It's a very boring job, so I developed a software which does that, automatically. Quote Link to comment
Mustafa Acar Posted July 4, 2016 Report Share Posted July 4, 2016 Hi, Thank you, for project but I have a problem. When ı run your program. This error appear. "Possible reason(s): LabVIEW: Remote registry access denied." Quote Link to comment
LogMAN Posted July 4, 2016 Report Share Posted July 4, 2016 2 hours ago, Mustafa Acar said: Hi, Thank you, for project but I have a problem. When ı run your program. This error appear. "Possible reason(s): LabVIEW: Remote registry access denied." Run the program as Administrator. Quote Link to comment
Mustafa Acar Posted July 4, 2016 Report Share Posted July 4, 2016 Actually, I want use in my VI . How can I do it ? Quote Link to comment
LogMAN Posted July 4, 2016 Report Share Posted July 4, 2016 3 minutes ago, Mustafa Acar said: Actually, I want use in my VI . How can I do it ? What is your issue? Put COMPorts_EnumCleaner.vi onto your block diagram and you are ready to go. In all cases you need Administrator privileges. If you want to run the code from within LabVIEW (by running the VI), you'll have to start LabVIEW as Administrator too. Quote Link to comment
mru4913 Posted February 8, 2017 Report Share Posted February 8, 2017 @spaghetti_developer Thank you for your sharing. I do not think i can open your VI project which is named as PortsCleaner? It said that "Open Registry Key.vi" has error. Do you know what's wrong? Quote Link to comment
hooovahh Posted February 10, 2017 Report Share Posted February 10, 2017 The Open Registry Key.vi is a VI installed with LabVIEW. It is part of the vi.lib. If this VI is broken then there is probably something wrong with your install of LabVIEW and you should probably repair it. I opened the posted code and nothing is broken. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.