[chirp_users] FT2DR connecting with Linux
Who has tested the FT2DR radio with linux?
What USB cable did you use?
My spidey senses are telling me no one has tested this combination.
Chirp works fine with my FT7900 and a FTDI cable.
It appears the cable provided with the FT2DR is not a 232 converter.
I am also guessing that there is a PL2303 chip in the radio. (Yaesu provides PL2303 drivers for windows.)
Problem is it does not identify itself as such so Linux does not know what to do with it.
this is the output of lsusb with the radio plugged in and turned on
rick@rick-ham ~ $ lsusb Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0c45:7412 Microdia Bus 002 Device 004: ID 26aa:0001 <<<<<<<<<<<<<<< this is the radio, no ID Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
NOTE - This device disappears when the send button on the radio is activated and the radio reports an Error.
This is the output of lsusb with the cord unplugged at the radio (cord still plugged into computer)
rick@rick-ham ~ $ lsusb Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0c45:7412 Microdia Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Given this, I conclude this is an "empty" straight through USB cable.
I can't use https://github.com//torvalds/linux/blob/master/drivers/usb/serial/pl2303.c because the chip does not identify.
Am I trying to use the wrong cable? It's possible I mixed up the cable with another or I received a defective cable. Yaesu does not offer a cable as an accy, so I can't buy a new one retail.
This is the output of isusb with my FT7900 cable connected
lsusb Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0c45:7412 Microdia Bus 002 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC <<<<This is it Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
This is my RT Systems cable connected
rick@rick-ham ~ $ lsusb Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0c45:7412 Microdia Bus 002 Device 008: ID 2100:9068 RT Systems Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
rick@rick-ham ~ $ ls /dev | grep tty tty tty0 tty1 tty10 tty11 tty12 tty13 tty14 tty15 tty16 tty17 tty18 tty19 tty2 tty20 tty21 tty22 tty23 tty24 tty25 tty26 tty27 tty28 tty29 tty3 tty30 tty31 tty32 tty33 tty34 tty35 tty36 tty37 tty38 tty39 tty4 tty40 tty41 tty42 tty43 tty44 tty45 tty46 tty47 tty48 tty49 tty5 tty50 tty51 tty52 tty53 tty54 tty55 tty56 tty57 tty58 tty59 tty6 tty60 tty61 tty62 tty63 tty7 tty8 tty9 ttyprintk ttyS0 ttyS1 ttyS10 ttyS11 ttyS12 ttyS13 ttyS14 ttyS15 ttyS16 ttyS17 ttyS18 ttyS19 ttyS2 ttyS20 ttyS21 ttyS22 ttyS23 ttyS24 ttyS25 ttyS26 ttyS27 ttyS28 ttyS29 ttyS3 ttyS30 ttyS31 ttyS4 ttyS5 ttyS6 ttyS7 ttyS8 ttyS9
Not recognised
Also I see that Yaesu has different ADMS software for the new firmware version that was just released. My spidey senses tell me that Chirp won't work with the new firmware. So this may all be for naught.
I've used the FT1XD with the stock cable and chirp on ubuntu. I'd be surprised if there was any significant difference that would keep the ft2dr from working, but don't have one to test with.
Tom Henderson
On 10/27/2017 03:06 PM, rick via chirp_users wrote:
Who has tested the FT2DR radio with linux?
What USB cable did you use?
My spidey senses are telling me no one has tested this combination.
Chirp works fine with my FT7900 and a FTDI cable.
It appears the cable provided with the FT2DR is not a 232 converter.
I am also guessing that there is a PL2303 chip in the radio. (Yaesu provides PL2303 drivers for windows.)
Problem is it does not identify itself as such so Linux does not know what to do with it.
this is the output of lsusb with the radio plugged in and turned on
rick@rick-ham ~ $ lsusb Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0c45:7412 Microdia Bus 002 Device 004: ID 26aa:0001 <<<<<<<<<<<<<<< this is the radio, no ID Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
NOTE - This device disappears when the send button on the radio is activated and the radio reports an Error.
This is the output of lsusb with the cord unplugged at the radio (cord still plugged into computer)
rick@rick-ham ~ $ lsusb Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0c45:7412 Microdia Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Given this, I conclude this is an "empty" straight through USB cable.
I can't use https://github.com//torvalds/linux/blob/master/drivers/usb/serial/pl2303.c because the chip does not identify.
Am I trying to use the wrong cable? It's possible I mixed up the cable with another or I received a defective cable. Yaesu does not offer a cable as an accy, so I can't buy a new one retail.
This is the output of isusb with my FT7900 cable connected
lsusb Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0c45:7412 Microdia Bus 002 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC <<<<This is it Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
This is my RT Systems cable connected
rick@rick-ham ~ $ lsusb Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0c45:7412 Microdia Bus 002 Device 008: ID 2100:9068 RT Systems Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
rick@rick-ham ~ $ ls /dev | grep tty tty tty0 tty1 tty10 tty11 tty12 tty13 tty14 tty15 tty16 tty17 tty18 tty19 tty2 tty20 tty21 tty22 tty23 tty24 tty25 tty26 tty27 tty28 tty29 tty3 tty30 tty31 tty32 tty33 tty34 tty35 tty36 tty37 tty38 tty39 tty4 tty40 tty41 tty42 tty43 tty44 tty45 tty46 tty47 tty48 tty49 tty5 tty50 tty51 tty52 tty53 tty54 tty55 tty56 tty57 tty58 tty59 tty6 tty60 tty61 tty62 tty63 tty7 tty8 tty9 ttyprintk ttyS0 ttyS1 ttyS10 ttyS11 ttyS12 ttyS13 ttyS14 ttyS15 ttyS16 ttyS17 ttyS18 ttyS19 ttyS2 ttyS20 ttyS21 ttyS22 ttyS23 ttyS24 ttyS25 ttyS26 ttyS27 ttyS28 ttyS29 ttyS3 ttyS30 ttyS31 ttyS4 ttyS5 ttyS6 ttyS7 ttyS8 ttyS9
Not recognised
Also I see that Yaesu has different ADMS software for the new firmware version that was just released. My spidey senses tell me that Chirp won't work with the new firmware. So this may all be for naught.
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tom KM4UQB at tom@henderson4.us To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
You need the SCU-19 cable to use FT-2D with Chirp
Roger G8XAN
On 27 October 2017 at 23:12, Tom Henderson Tom@henderson4.us wrote:
I've used the FT1XD with the stock cable and chirp on ubuntu. I'd be surprised if there was any significant difference that would keep the ft2dr from working, but don't have one to test with.
Tom Henderson
On 10/27/2017 03:06 PM, rick via chirp_users wrote:
Who has tested the FT2DR radio with linux?
What USB cable did you use?
My spidey senses are telling me no one has tested this combination.
Chirp works fine with my FT7900 and a FTDI cable.
It appears the cable provided with the FT2DR is not a 232 converter.
I am also guessing that there is a PL2303 chip in the radio. (Yaesu provides PL2303 drivers for windows.)
Problem is it does not identify itself as such so Linux does not know what to do with it.
this is the output of lsusb with the radio plugged in and turned on
rick@rick-ham ~ $ lsusb Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0c45:7412 Microdia Bus 002 Device 004: ID 26aa:0001 <<<<<<<<<<<<<<< this is the radio, no ID Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
NOTE - This device disappears when the send button on the radio is activated and the radio reports an Error.
This is the output of lsusb with the cord unplugged at the radio (cord still plugged into computer)
rick@rick-ham ~ $ lsusb Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0c45:7412 Microdia Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Given this, I conclude this is an "empty" straight through USB cable.
I can't use https://github.com//torvalds/linux/blob/master/drivers/usb/ serial/pl2303.c because the chip does not identify.
Am I trying to use the wrong cable? It's possible I mixed up the cable with another or I received a defective cable. Yaesu does not offer a cable as an accy, so I can't buy a new one retail.
This is the output of isusb with my FT7900 cable connected
lsusb Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0c45:7412 Microdia Bus 002 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC <<<<This is it Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
This is my RT Systems cable connected
rick@rick-ham ~ $ lsusb Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0c45:7412 Microdia Bus 002 Device 008: ID 2100:9068 RT Systems Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
rick@rick-ham ~ $ ls /dev | grep tty tty tty0 tty1 tty10 tty11 tty12 tty13 tty14 tty15 tty16 tty17 tty18 tty19 tty2 tty20 tty21 tty22 tty23 tty24 tty25 tty26 tty27 tty28 tty29 tty3 tty30 tty31 tty32 tty33 tty34 tty35 tty36 tty37 tty38 tty39 tty4 tty40 tty41 tty42 tty43 tty44 tty45 tty46 tty47 tty48 tty49 tty5 tty50 tty51 tty52 tty53 tty54 tty55 tty56 tty57 tty58 tty59 tty6 tty60 tty61 tty62 tty63 tty7 tty8 tty9 ttyprintk ttyS0 ttyS1 ttyS10 ttyS11 ttyS12 ttyS13 ttyS14 ttyS15 ttyS16 ttyS17 ttyS18 ttyS19 ttyS2 ttyS20 ttyS21 ttyS22 ttyS23 ttyS24 ttyS25 ttyS26 ttyS27 ttyS28 ttyS29 ttyS3 ttyS30 ttyS31 ttyS4 ttyS5 ttyS6 ttyS7 ttyS8 ttyS9
Not recognised
Also I see that Yaesu has different ADMS software for the new firmware version that was just released. My spidey senses tell me that Chirp won't work with the new firmware. So this may all be for naught.
chirp_users mailing listchirp_users@intrepid.danplanet.comhttp://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tom KM4UQB at tom@henderson4.us To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Roger Woods at woodsrb@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
participants (3)
-
rick -
Roger Woods -
Tom Henderson