Keying K3 on bootup
|
In today’s Contest University presentation, N6TV covered USB and Serial interfaces.
and THANK YOU N6TV!!
Bob gave the key item to get the FTDI seral converters programmed so don’t key rig on bootup
The COM port default settings is a bust
See pages 27/28 of his presentation (Link above)
One goes to Device Manager, picks the COM port, change advanced settings so “Serial Enumerator” is unchecked “Disable Modem Ctrl At Startup” is checked
Again, TNX Bob for fine presentation, it helped!!
73 W5AJ
Robert Midland, Texas
|
|
|
|
Dave Cole
Thank you, that has bothered me for years! All fixed now.
toggle quoted messageShow quoted text
73, and thanks, Dave (NK7Z) https://www.nk7z.net ARRL Volunteer Examiner ARRL Technical Specialist ARRL Asst. Director, NW Division, Technical Resources
On 5/14/20 4:42 PM, Robert W5AJ wrote:
In today’s Contest University presentation, N6TV covered USB and Serial interfaces.
|
|
|
|
Did you observe any power output? And what was done to "fix it"?
73 Bob, K4TAX
|
|
|
|
As noted below:
One goes to Device Manager, picks the COM port, change advanced settings so “Serial Enumerator” is unchecked “Disable Modem Ctrl At Startup” is checked
|
|
|
|
I was just trying this on my Windows 10/64 machine, which I believe is up-to-date. My COM ports all show up in Device Manager as PCI Serial Ports, e.g. "PCI Serial Port (COM4)" for my K3 CAT port. When I right click on the port, select Properties, select Port Settings, then Advanced, I don't see either of the specified settings. I see the settings for FIFO buffers and a pull-down to change the port name. What am I missing? 73, Randy, KS4L
On Thu, May 14, 2020 at 11:08 PM Robert W5AJ <woodr90@...> wrote:
|
|
|
|
Should have said this port (COM4) is an actual RS232 serial port, not USB. Maybe that's the difference. But it does key-up the K3 on boot-up. 73, Randy, KS4L
On Fri, May 15, 2020 at 10:17 AM Randy Moore <wrmoore47@...> wrote:
|
|
|
|
Joe, KO8V
I started looking into doing a custom FTDI driver to have those options set whenever an FTDI standard device is installed (i.e. factory vendor/product ids). It looks like it could be done. FTDI publishes a note on customizing the driver .INF file. I think I would have to uninstall the current driver and reinstall driver using the custiom .INF file. If any one has already done that, it would be great to share it. The information on doing this can be found in these two documents:
https://www.ftdichip.com/Support/Documents/AppNotes/AN_107_AdvancedDriverOptions_AN_000073.pdf https://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_149_Create_a_Custom_Driver_Executable.pdf -- 73 Joe, KO8V
|
|
|
|
Hi Randy, the driver settings in question are only available for FTDI chipsets. Unfortunately I have never seen the options exposed for other serial port drivers. Max NG7M
|
|
|
|
Joe, this reminds me of another solution here I have always thought would be nice... it would be to write a simple application that would enumerate through the serial port devices in the registry and detect the FTDI chipset based on expected registry values and then simply change the setting. Now all I need to do is get the motivation to do this! This type of an app would need to run with elevated privileges' / as admin. It could be done in vb script or power shell script or in any number of different languages that have access to the windows api's that let you modify the registry.
You could the just execute the script after an FTDI serial driver update or a bigger Windows update (like Windows 10 version release 2004 which will push out to consumers later this month or early next month). I'm digressing, but I already updated to Windows 10 2004, and as expected I needed to go in and set all the FTDI driver options again as described in Bob's presentation (ones that have been known for years now). I saw zero problems with the update... no funky com port number changes or issues with sound card default settings. It was a simple and smooth update. I have 11 FTDI comports in my setup too. Max NG7M
|
|
|