October 2017 - Users - lists.chirpmyradio.com

[chirp_users] BF-888S Transmit Inhibit?
by Richard Dillman 28 Oct '17

28 Oct '17

Is it possible to set transmit inhibit (receive only) for a channel in the BF-888S? Many Thanks, RD =============================== Richard Dillman, Transmitter Wrangler KWMR Community Radio for West Marin ===============================

2 2

[chirp_users] FT2DR connecting with Linux
by rick 27 Oct '17

27 Oct '17

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.

3 2

[chirp_users] Connecting to a FT2DR
by Rick Begeman 23 Oct '17

23 Oct '17

Forgot to ask 5v or 3.3 volt FTDI?

1 0

[chirp_users] Connecting to a FT2DR
by Rick Begeman 23 Oct '17

23 Oct '17

What cable is being used for a FT2DR and Linux?The factory cable does not create a ttyUSB port when connected to the Linux box.Will an FTDI cable with a mini USB work with this radio?

1 0

[chirp_users] New Daily Build
by Build System 20 Oct '17

20 Oct '17

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20171020 A list of the changes included in this build (since the last daily) follows: Changes for Build #503 [Dan Smith <dsmith(a)danplanet.com>] [BTECH] Fix scramble bit resetting for BTECH color LCD variants Since we never expose the scramble setting, we never get a chance to ensure that bit is set to zero on these radios. Since the base driver never fully clears a memory that it is brining out of empty state, this bit can be set when it shouldn't be. This change always zeroes it for that radio, fully clears memories when bringing them out of empty state, and also zeroes the settings before applying the actual mem.extra settings when doing that. #5261 [Dan Smith <dsmith(a)danplanet.com>] Make tests module generate a unittest-compatible interface This lets us use the integrated unittest runner, which does things like report failures at the end, stdio buffering, etc. You can still use the old tests/run_tests if desired (for now), but this makes it much nicer for the build system. Loosely related to #5237 [Dan Smith <dsmith(a)danplanet.com>] Make run_tests a proper python module Also provide a run_tests shell wrapper for compatibility. Related to #5237

1 0

[chirp_users] Baofeng 888 problem
by Doug 18 Oct '17

18 Oct '17

I have programmed hundres of baofeng 888's. Latest batch the settings menu cannot be changed. Something has changed. Anyone see this problem? Using latest chirp. Doug Crompton WA3DSP http://www.crompton.com

1 0

[chirp_users] Txmy disable?
by rkruz 18 Oct '17

18 Oct '17

For a particular memory is there a setting(s) for listen only that will prevent the radio from transmitting for the baofengs? This for private or pro repeaters. Thx -------- Original message --------From: Baji Panchumarti <ohiobaji(a)gmail.com> Date: 10/18/17 2:02 PM (GMT-08:00) To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Subject: Re: [chirp_users] Location field This feature is useful if you have one radio that you only program from PC-to-Radio, and if you are using CHIRP to keep track of Frequencies. The minute you read the channels off a radio (Radio-to-PC) in the other direction, the location field and the notes field would be empty. And it would likely be a chore to transplant your location data and notes from another CHIRP programming list. I believe the columns present in CHIRP are an aggregation of programmable fields found across multiple radios that are CHIRP compatible. ~baji / K 8 I I T . _ . _ . On Wed, Oct 18, 2017 R Kruz wrote: In the database fields it would be super helpful if there was a field for location. A field long enough to spell out a city or locations something like Santiago Peak. I understand this would not appear in the Baofeng radio display but just having it in the Chirp data base would be very helpful. Even a notes field to use for this would be great. thanks! _______________________________________________

2 1

Re: [chirp_users] Location field
by Baji Panchumarti 18 Oct '17

18 Oct '17

This feature is useful if you have one radio that you only program from PC-to-Radio, and if you are using CHIRP to keep track of Frequencies. The minute you read the channels off a radio (Radio-to-PC) in the other direction, the location field and the notes field would be empty. And it would likely be a chore to transplant your location data and notes from another CHIRP programming list. I believe the columns present in CHIRP are an aggregation of programmable fields found across multiple radios that are CHIRP compatible. ~baji / K 8 I I T . _ . _ . On Wed, Oct 18, 2017 R K ruz wrote: In the database fields it would be super helpful if there was a field for > location. A field long enough to spell out a city or locations something > like Santiago Peak. I understand this would not appear in the Baofeng > radio display but just having it in the Chirp data base would be very > helpful. Even a notes field to use for this would be great. thanks! > > _______________________________________________ >

1 0

[chirp_users] Location field
by r kruz 18 Oct '17

18 Oct '17

In the database fields it would be super helpful if there was a field for location. A field long enough to spell out a city or locations something like Santiago Peak. I understand this would not appear in the Baofeng radio display but just having it in the Chirp data base would be very helpful. Even a notes field to use for this would be great. thanks!

1 0

Re: [chirp_users] Connecting to my FT2DR
by Dave B 18 Oct '17

18 Oct '17

Hi Rick On 17/10/17 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > rick@rick-ham ~ $ groups > rick adm dialout cdrom sudo dip plugdev lpadmin sambashare Good... > rick@rick-ham ~ $ ls /dev/ttyU** > ls: cannot access '/dev/ttyU**': No such file or directory? << with That should be ls /dev/ttyU* (One star! Some spurious ones appeared as a result of me trying to be clever..) Also try... dmesg | tail Immediately after connecting the (powered up) radio and lead, or your Prolific based lead. Example... dave-XPS-L502X ~ $ dmesg | tail [ 504.731848] usb 2-1.2: Product: US232R [ 504.731853] usb 2-1.2: Manufacturer: FTDI [ 504.731857] usb 2-1.2: SerialNumber: FTDBHZL8 [ 504.733883] ftdi_sio 2-1.2:1.0: FTDI USB Serial Device converter detected [ 504.734055] usb 2-1.2: Detected FT232RL [ 504.734063] usb 2-1.2: Number of endpoints 2 [ 504.734071] usb 2-1.2: Endpoint 1 MaxPacketSize 64 [ 504.734079] usb 2-1.2: Endpoint 2 MaxPacketSize 64 [ 504.734085] usb 2-1.2: Setting MaxPacketSize 64 [ 504.734681] usb 2-1.2: FTDI USB Serial Device converter now attached to ttyUSB0 dave-XPS-L502X ~ $ (That was after connecting a FTDI based USB<>Serial adapter.) ~~~ If you do:- dmesg | tail -20 You'll get the last 20 lines of the dmesg output. Without the -20 (or other number) you'll get 10 lines by default. Try:- dmesg on it's own as a comparison! ;-) See:- man tail for details of the tail filter. ~~~ If you have the radio's user manual, and it has all the CAT commands etc described, install "cutecom" A nice little graphical serial terminal program... sudo apt update && sudo apt install cutecom Should do the trick. (You'll only be asked for your password once.) (Launch it from the command line with just cutecom or find it in the "Other" menu choices from the Mint menu button, at least that's where it is on this box.) Then you can try to manually communicate with the rig, to try out the interface. That can be another "steep learning curve" but it'll do you good to learn how to do such things for the future, especially with bit rate, data bits, parity and so on. Hope something helps. PM me if you need to keep from QRM'ing the list. (I've Bcc'd you direct so you can reply direct if needed..) 73. Dave B.

1 0