Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Windows 11 and cable compatibility
|
Gentlemen,
Is anyone out there using a PC with Windows 11 to program their TT3/TT4 devices? If so, have you used any of the Byonics USB programming cables and Prolifics drivers? I have had a report of incompatibility with the cables and WIN 11. Not wanting to possibly ruin my life, or at least a computer, by loading an OS that is probably as buggy as a Louisiana swamp, I thought it best to seek the wisdom of the crowd!
73,
Allen AF6OF
|
开云体育When Windows 10 came out, there were problems with ‘Prolific’ chip cables. These chips were fake Prolific chips from China. Windows always wants to use the latest and greatest drivers. For the fake chips, these drivers caused those chips to not work. The work around for this is to roll back the Prolific driver to 3.2.0.0. The cables then work just fine. You can find the 3.2.0.0. driver at www.miklor.com, along with a large amount of other very useful information.?Jardy Dawson WA7JRD Message sent by....Oh look!! Pretty lights!! On Nov 4, 2021, at 15:26, vhsproducts via groups.io <vhsproducts@...> wrote:
|
|
Agreed!!
toggle quoted message
Show quoted text
HOWEVER, the question becomes whether Windows 11 will allow the install of the older drivers. Rob KB8RCO
|
|
Jardy, Thanks, I will pass that along to the guy with the cable problems. I suspect that as Robert suggests, that WIN 11 will not handle "legacy" devices, but it is worth a shot! Our cables ( Which don't use counterfeit chips, BTW) are pretty much identical to the similar Kenwood cables with the 2.5mm plugs for APRS handhelds, so they may be having similar problems. 73, Allen AF6OF On Thu, Nov 4, 2021 at 4:01 PM Rob Giuliano via <kb8rco=[email protected]> wrote: Agreed!! |
|
I’m not using Windows of any kind, but I am now having trouble with my USB cables for the TT4, I have upgraded from Debian 10 to Debian 11, (LINUX) and the cable stopped working altogether. Anyone else having the same issue? Thanks! BJ Sent from myMail for iOS Thursday, November 4, 2021, 15:26 -0700 from vhsproducts@... <vhsproducts@...>:
|
|
Tell us what chip is in the cable. Post the output of "lsusb" command.
toggle quoted message
Show quoted text
If the chip is FTDI or CP2101 it should be ok. If it is a PL2302 then throw it away. Cliff K6CLS CM87 On November 4, 2021 3:40:45 PM PDT, BJ Miller <ve7lad@...> wrote:
|
|
BJ: I have not used debian directly, but I use both Pop-OS and Linux Mint (ubuntu/debian roots), and I need to add usb vid/pid IDs for usb devices I use.? Perhaps you need to add your serial dongle IDs as a rule file. as sudo, in the? /etc/udev/rules.d directory, I create a file called 10-gil.rules with two lines as follows: SUBSYSTEM=="usb", ATTR{idVendor}=="0483", ATTR{idProduct}=="5750", TAG+="uaccess" KERNEL=="hidraw*", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5750", TAG+="uaccess" That is the vid/pid for an stm micro I use as a custom hid device. The number in the filename is a load priority or something, and really does not seem critical.? Segger uses a file called 99-jlink.rules for their swd dongles. fwiw, gil ----- Original message ----- From: BJ Miller <ve7lad@...> Subject: Re: [TinyTrak] Windows 11 and cable compatibility Date: Thursday, November 04, 2021 3:40 PM I’m not using Windows of any kind, but I am now having trouble with my USB cables for the TT4, I have upgraded from Debian 10 to Debian 11, (LINUX) and the cable stopped working altogether. Anyone else having the same issue? Thanks! BJ Sent from myMail for iOS Thursday, November 4, 2021, 15:26 -0700 from vhsproducts@... <vhsproducts@...>:
|
|
BJ, Linux is pretty close to driver independent - more specifically, everything is a file and a generic driver for devices will pretty much handle what is needed.? I have not found a single USB-RS232 or USB-TTL device that didn't just work on any version of Linux I've used, when paired with the proper /dev/tty???? file link. For all practical purposes, the main issues are device naming and making sure your application is pointed at the device connected to the TT4. In most cases, udev rules are the best solution for ensuring you are pointing to the corrrect device. That said, if you are trying to use WINE and Windows configuration tools, or terminal programs (like TeraTerm Pro), that is a different story. If you give a bit more detail on your setup: ? Okay -> got that it is Debian 11. ? As stated -> lsusb output for the device (PL2302 have worked fine on everything I have) would be helpful ? What application are you running to interface with the TT4? Robert Giuliano
On Thursday, November 4, 2021, 08:04:38 PM EDT, Cliff Sojourner <cls@...> wrote:
Tell us what chip is in the cable. Post the output of "lsusb" command. If the chip is FTDI or CP2101 it should be ok. If it is a PL2302 then throw it away. Cliff K6CLS CM87 On November 4, 2021 3:40:45 PM PDT, BJ Miller <ve7lad@...> wrote:
Gentlemen,
Is anyone out there using a PC with Windows 11 to program their TT3/TT4 devices? If so, have you used any of the Byonics USB programming cables and Prolifics drivers? I have had a report of incompatibility with the cables and WIN 11. Not wanting to possibly ruin my life, or at least a computer, by loading an OS that is probably as buggy as a Louisiana swamp, I thought it best to seek the wisdom of the crowd!
73,
Allen AF6OF
|
|
You should not need 2 dev rules to define a device. Most often, USB serial devices (USB-TTL or USB-RS232) fall under SUBSYSTEM=='tty". Looking at my udev rules, reminds me that you have to ensure your user has permisssion for the device. Be sure and add your user to group "dialout" I? have the file 50-tty.rules that redefines devices to map to WINE usable names and looks like this: # ======================================================================== # This file was created to accoyunt for all USB devices that need to #?? report as COM# devices for WINE.? Setup as follows #?? ?COM1??? =>????? ttyS0 is a physical device on the motherboard #?? ?COM2??? =>????? ttyS1 is an optional physical device on the motherboard #?? ?COM3??? =>????? TNC-X #?? ?COM4??? =>????? Arduino Nano (or Nano in the RSHFIQ) #?? ?COM5??? =>????? CH341 (I2C/SPI/UART - any mode) #?? ?COM6??? =>????? Teensy #?? ?COM7??? =>????? ublox #?? ?COM8??? =>????? T3_301 #?? ?COM9??? =>????? {not assigned} # # # It can be modify, as long as you keep each rule on a single #? line, and change only the value of the NAME= key. # # ======================================================================== # TNC-X shows as ttyUSB#?? => symlink TNC-X to ttyS2 (WINE COM3) SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", SYMLINK+="ttyS2", GROUP="dialout" # Arduino 101 in DFU Mode?? From installation # Nano shows as ttyUSB#?? => symlink nano to ttyS3 (WINE COM4) # My Arduino Nano info?? QinHeng Electronics HL-340 USB-Serial adapter SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", MODE="0666", SYMLINK+="ttyS3", GROUP="dialout" # CH341 shows as ttyUSB#??? => symlink CH341 to ttyS4 (WINE COM5) in UART mode SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="5523", SYMLINK+="ttyS4", GROUP="dialout" # CH341 shows as ttyUSB#??? => symlink CH341 to ttyS4 (WINE COM5) in SPI/I2C mode # SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="5512", SYMLINK+="ttyS4", GROUP="dialout" SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="5512", SYMLINK+="ttyS4", GROUP="dialout" # After this file is installed, physically unplug and reconnect Teensy shows as ttyACM#? => symlink teensy to ttyS5 (WINE COM6) ? ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04*", ENV{ID_MM_DEVICE_IGNORE}="1", ENV{ID_MM_PORT_IGNORE}="1" ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789a]*", ENV{MTP_NO_PROBE}="1" KERNEL=="ttyACM*", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04*", MODE:="0666", RUN:="/bin/stty -F /dev/%k raw -echo" KERNEL=="hidraw*", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04*", MODE:="0666" SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04*", MODE:="0666" SUBSYSTEM=="tty", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04*", SYMLINK+="ttyS5", GROUP="dialout" # UDEV Rules for ublox GPS shows as ttyACM#? => symlink ublox GPS to ttyS6 (WINE COM7) ? # SUBSYSTEM=="tty", ATTRS{idVendor}=="1546", ATTRS{idProduct}=="01a8", SYMLINK+="ttyS6", GROUP="dialout" SUBSYSTEM=="tty", ATTRS{idVendor}=="1546", ATTRS{idProduct}=="01a8", SYMLINK="ttyS6", GROUP="dialout" # T3-301 module shows as ttyUSB#?? => symlink T3-301 module to ttyS7 (WINE COM8) FC-301D with T3-301 module SUBSYSTEM=="tty", ATTRS{idVendor}=="134a", ATTRS{idProduct}=="9000", SYMLINK="ttyS7", GROUP="dialout" # UDEV Rules for CP210x USB to TTL #???? Have many, so unsure if more than one plugged in? #???? No unique ATTRS{} found? shows as ttyUSB#? => symlink CP210x to ttyS8 (WINE COM9) ? SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", SYMLINK="ttyS8", GROUP="dialout" This is on KUbuntu, but the same on my Pis and several other distros with and without Debian roots.. Robert Giuliano
On Thursday, November 4, 2021, 08:14:53 PM EDT, Gil Smith <tinytrak@...> wrote:
BJ: I have not used debian directly, but I use both Pop-OS and Linux Mint (ubuntu/debian roots), and I need to add usb vid/pid IDs for usb devices I use.? Perhaps you need to add your serial dongle IDs as a rule file. as sudo, in the? /etc/udev/rules.d directory, I create a file called 10-gil.rules with two lines as follows: SUBSYSTEM=="usb", ATTR{idVendor}=="0483", ATTR{idProduct}=="5750", TAG+="uaccess" KERNEL=="hidraw*", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5750", TAG+="uaccess" That is the vid/pid for an stm micro I use as a custom hid device. The number in the filename is a load priority or something, and really does not seem critical.? Segger uses a file called 99-jlink.rules for their swd dongles. fwiw, gil ----- Original message ----- From: BJ Miller <ve7lad@...> Subject: Re: [TinyTrak] Windows 11 and cable compatibility Date: Thursday, November 04, 2021 3:40 PM I’m not using Windows of any kind, but I am now having trouble with my USB cables for the TT4, I have upgraded from Debian 10 to Debian 11, (LINUX) and the cable stopped working altogether. Anyone else having the same issue? Thanks! BJ Sent from myMail for iOS Thursday, November 4, 2021, 15:26 -0700 from vhsproducts@... <vhsproducts@...>:
|
|
Ahh yes Rob, forgot the dialout group for tty access. Recently ran into that when I plugged in an adafruit 954 (uses silabs CP2012): gil@pop-os:~$ lsusb ... Bus 001 Device 009: ID 10c4:ea60 Silicon Labs CP210x UART Bridge gil@pop-os:~$ lsusb -d 10c4:ea60 -v Bus 001 Device 009: ID 10c4:ea60 Silicon Labs CP210x UART Bridge ...(gory details) gil@pop-os:~$ sudo dmesg --human|tail ... [? +0.002242] cp210x 1-1:1.0: cp210x converter detected [? +0.001796] usb 1-1: cp210x converter now attached to ttyUSB0 gil@pop-os:~$ cd /dev gil@pop-os:/dev$ ll ttyU* crw-rw---- 1 root dialout 188, 0 Oct 27 14:12 ttyUSB0 === need to add dialout group: gil@pop-os:~$ sudo usermod -a -G dialout gil gil@pop-os:~$ groups gil adm sudo lpadmin === wait, what?? Oh, need to log out/in to update groups (or shutdown/restart) then: gil@pop-os:~$ groups gil adm tty dialout sudo lpadmin === now need a term-emu and picocom is handy: gil@pop-os:~$ sudo apt-get install picocom === then, add to home,? ~/.bash_aliases: ??? alias pico="picocom -b 115200 -r -l /dev/ttyUSB0" ----- Original message ----- From: "Rob Giuliano via groups.io" <kb8rco=[email protected]> Subject: Re: [TinyTrak] Windows 11 and cable compatibility Date: Thursday, November 04, 2021 5:58 PM You should not need 2 dev rules to define a device. Most often, USB serial devices (USB-TTL or USB-RS232) fall under SUBSYSTEM=='tty". Looking at my udev rules, reminds me that you have to ensure your user has permisssion for the device. Be sure and add your user to group "dialout" I? have the file 50-tty.rules that redefines devices to map to WINE usable names and looks like this: # ======================================================================== # This file was created to accoyunt for all USB devices that need to #?? report as COM# devices for WINE.? Setup as follows #?? ?COM1??? =>????? ttyS0 is a physical device on the motherboard #?? ?COM2??? =>????? ttyS1 is an optional physical device on the motherboard #?? ?COM3??? =>????? TNC-X #?? ?COM4??? =>????? Arduino Nano (or Nano in the RSHFIQ) #?? ?COM5??? =>????? CH341 (I2C/SPI/UART - any mode) #?? ?COM6??? =>????? Teensy #?? ?COM7??? =>????? ublox #?? ?COM8??? =>????? T3_301 #?? ?COM9??? =>????? {not assigned} # # # It can be modify, as long as you keep each rule on a single #? line, and change only the value of the NAME= key. # # ======================================================================== # TNC-X shows as ttyUSB#?? => symlink TNC-X to ttyS2 (WINE COM3) SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", SYMLINK+="ttyS2", GROUP="dialout" # Arduino 101 in DFU Mode?? From installation # Nano shows as ttyUSB#?? => symlink nano to ttyS3 (WINE COM4) # My Arduino Nano info?? QinHeng Electronics HL-340 USB-Serial adapter SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", MODE="0666", SYMLINK+="ttyS3", GROUP="dialout" # CH341 shows as ttyUSB#??? => symlink CH341 to ttyS4 (WINE COM5) in UART mode SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="5523", SYMLINK+="ttyS4", GROUP="dialout" # CH341 shows as ttyUSB#??? => symlink CH341 to ttyS4 (WINE COM5) in SPI/I2C mode # SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="5512", SYMLINK+="ttyS4", GROUP="dialout" SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="5512", SYMLINK+="ttyS4", GROUP="dialout" # After this file is installed, physically unplug and reconnect Teensy shows as ttyACM#? => symlink teensy to ttyS5 (WINE COM6) ? ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04*", ENV{ID_MM_DEVICE_IGNORE}="1", ENV{ID_MM_PORT_IGNORE}="1" ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789a]*", ENV{MTP_NO_PROBE}="1" KERNEL=="ttyACM*", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04*", MODE:="0666", RUN:="/bin/stty -F /dev/%k raw -echo" KERNEL=="hidraw*", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04*", MODE:="0666" SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04*", MODE:="0666" SUBSYSTEM=="tty", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04*", SYMLINK+="ttyS5", GROUP="dialout" # UDEV Rules for ublox GPS shows as ttyACM#? => symlink ublox GPS to ttyS6 (WINE COM7) ? # SUBSYSTEM=="tty", ATTRS{idVendor}=="1546", ATTRS{idProduct}=="01a8", SYMLINK+="ttyS6", GROUP="dialout" SUBSYSTEM=="tty", ATTRS{idVendor}=="1546", ATTRS{idProduct}=="01a8", SYMLINK="ttyS6", GROUP="dialout" # T3-301 module shows as ttyUSB#?? => symlink T3-301 module to ttyS7 (WINE COM8) FC-301D with T3-301 module SUBSYSTEM=="tty", ATTRS{idVendor}=="134a", ATTRS{idProduct}=="9000", SYMLINK="ttyS7", GROUP="dialout" # UDEV Rules for CP210x USB to TTL #???? Have many, so unsure if more than one plugged in? #???? No unique ATTRS{} found? shows as ttyUSB#? => symlink CP210x to ttyS8 (WINE COM9) ? SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", SYMLINK="ttyS8", GROUP="dialout" This is on KUbuntu, but the same on my Pis and several other distros with and without Debian roots.. Robert Giuliano KB8RCO On Thursday, November 4, 2021, 08:14:53 PM EDT, Gil Smith <tinytrak@...> wrote: BJ: I have not used debian directly, but I use both Pop-OS and Linux Mint (ubuntu/debian roots), and I need to add usb vid/pid IDs for usb devices I use.? Perhaps you need to add your serial dongle IDs as a rule file. as sudo, in the? /etc/udev/rules.d directory, I create a file called 10-gil.rules with two lines as follows: SUBSYSTEM=="usb", ATTR{idVendor}=="0483", ATTR{idProduct}=="5750", TAG+="uaccess" KERNEL=="hidraw*", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5750", TAG+="uaccess" That is the vid/pid for an stm micro I use as a custom hid device. The number in the filename is a load priority or something, and really does not seem critical.? Segger uses a file called 99-jlink.rules for their swd dongles. fwiw, gil ----- Original message ----- From: BJ Miller <ve7lad@...> Subject: Re: [TinyTrak] Windows 11 and cable compatibility Date: Thursday, November 04, 2021 3:40 PM I’m not using Windows of any kind, but I am now having trouble with my USB cables for the TT4, I have upgraded from Debian 10 to Debian 11, (LINUX) and the cable stopped working altogether. Anyone else having the same issue? Thanks! BJ Sent from myMail for iOS Thursday, November 4, 2021, 15:26 -0700 from vhsproducts@... <vhsproducts@...>:
|
|
Our customer has reported that an old driver (?Profilic?USB Drivers for PL2303TA?version 3.4.67.325 for Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1 32-bit (x86), 64-bit (x64).) works with WIN 11 too, so problem solved!
73,
Allen AF6OF -----Original Message-----
From: vhsproducts@... To: [email protected] <[email protected]> Sent: Thu, Nov 4, 2021 3:26 pm Subject: Windows 11 and cable compatibility Gentlemen,
Is anyone out there using a PC with Windows 11 to program their TT3/TT4 devices? If so, have you used any of the Byonics USB programming cables and Prolifics drivers? I have had a report of incompatibility with the cables and WIN 11. Not wanting to possibly ruin my life, or at least a computer, by loading an OS that is probably as buggy as a Louisiana swamp, I thought it best to seek the wisdom of the crowd!
73,
Allen AF6OF
|
|
I had a problem with two Proliphic cables used for my amplifier and tuner. Device manager read something like, Not compatible, contact manufacturer.? I selected rollback driver and the cables now work fine. At one point Windows 11 said there was a new Proliphic driver. I updated the driver and it went back to not working. I chose rollback driver again and it’s been fine ever since.? Curt |
|
For the time?being, I am going to regard Windows 11 as being an instrument of satan. Historically, this seems to be the best way of thinking about Microsoft products in early releases! 73, Allen AF6OF On Sat, Nov 6, 2021 at 4:29 AM Curt M. <WU3URADIO@...> wrote:
|
|
Especially when you look back at their release history.
toggle quoted message
Show quoted text
For a long, long time, they produced an "about every other realease was just CRAP". Rob KB8RCO
|
|
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> on behalf of Allen Lord <allen@...>
Sent: Saturday, 6 November 2021 11:27 PM To: [email protected] Group Moderators <[email protected]> Subject: Re: [TinyTrak] Windows 11 and cable compatibility ?
For the time?being, I am going to regard Windows 11 as being an instrument of satan. Historically, this seems to be the best way of thinking about Microsoft products in early releases!
73,
Allen AF6OF
On Sat, Nov 6, 2021 at 4:29 AM Curt M. <WU3URADIO@...> wrote:
|
|
I too have be bitten by this issue.? The issue is not a Microsoft issue but rather a Byonics problem.? The cable that came with my recently purchased MicroFox uses the Prolific PL2303TA usb to serial bridge controller which reached end of life in 2020.? I have been able to work around the issue for the time being by following the instructions for using the instructions found here--https://embetronicx.com/uncategorized/fixed-prolific-pl2303ta-usb-to-serial-and-windows-11/ .? Note the driver is on a google drive so not sure how long it will be there.? I also had to be sure that I used a low number for my com port likely because of limitations in the Byonics software.
It would be nice to find a supported solution.? Perhaps FTDI or Silicon Labs has a device that would solve the problem.?? Joe AF1E ? |
开云体育If you have Prolific cables that aren’t working, try rolling the driver back to 3.2.0.0. You can find the driver and the reasons for it, along with a lot more useful info at www.miklor.com.?Jardy Dawson WA7JRD Message sent by....Oh look!! Pretty lights!! On Nov 28, 2022, at 15:26, Joe Spears <jgspears@...> wrote:
|
Cliff Sojourner K6CLS
Doug J
Joe Spears AF1E
to navigate to use esc to dismiss