October 2017 - Users - lists.chirpmyradio.com

[chirp_users] BF-888 PROGRAMING
by ROBERT SCHOBER 16 Oct '17

16 Oct '17

Is there a way to disable all TX and make it a RX only device?? Tnx, Bob

2 1

Re: [chirp_users] Connecting to my FT2DR
by rick 16 Oct '17

16 Oct '17

OK I found some more clues. I plugged in a Prolific USB to RS232 adapter. BINGO! 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 011: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub rick@rick-ham ~ $ ls /dev/tty*** /dev/tty /dev/tty21 /dev/tty35 /dev/tty49 /dev/tty62 /dev/ttyS17 /dev/ttyS30 /dev/tty0 /dev/tty22 /dev/tty36 /dev/tty5 /dev/tty63 /dev/ttyS18 /dev/ttyS31 /dev/tty1 /dev/tty23 /dev/tty37 /dev/tty50 /dev/tty7 /dev/ttyS19 /dev/ttyS4 /dev/tty10 /dev/tty24 /dev/tty38 /dev/tty51 /dev/tty8 /dev/ttyS2 /dev/ttyS5 /dev/tty11 /dev/tty25 /dev/tty39 /dev/tty52 /dev/tty9 /dev/ttyS20 /dev/ttyS6 /dev/tty12 /dev/tty26 /dev/tty4 /dev/tty53 /dev/ttyprintk /dev/ttyS21 /dev/ttyS7 /dev/tty13 /dev/tty27 /dev/tty40 /dev/tty54 /dev/ttyS0 /dev/ttyS22 /dev/ttyS8 /dev/tty14 /dev/tty28 /dev/tty41 /dev/tty55 /dev/ttyS1 /dev/ttyS23 /dev/ttyS9 /dev/tty15 /dev/tty29 /dev/tty42 /dev/tty56 /dev/ttyS10 /dev/ttyS24 /dev/ttyUSB0 /dev/tty16 /dev/tty3 /dev/tty43 /dev/tty57 /dev/ttyS11 /dev/ttyS25 /dev/tty17 /dev/tty30 /dev/tty44 /dev/tty58 /dev/ttyS12 /dev/ttyS26 /dev/tty18 /dev/tty31 /dev/tty45 /dev/tty59 /dev/ttyS13 /dev/ttyS27 /dev/tty19 /dev/tty32 /dev/tty46 /dev/tty6 /dev/ttyS14 /dev/ttyS28 /dev/tty2 /dev/tty33 /dev/tty47 /dev/tty60 /dev/ttyS15 /dev/ttyS29 /dev/tty20 /dev/tty34 /dev/tty48 /dev/tty61 /dev/ttyS16 /dev/ttyS3 rick@rick-ham ~ $ What cord are you using to connect your Yaesu FT2DR? I have been trying to use the cord that came with the radio. I have even tried connecting the radio and turning it on to clone mode to see if a tty port is created, no joy... It would appear that the cable provided with my radio is not a "smart" cable and even connecting to the radio does not create a port. Who tested the FT2DR? And what cord did they use? Rick

1 0

Re: [chirp_users] Connecting to my FT2DR
by rick 16 Oct '17

16 Oct '17

On 15/10/17 20:00,chirp_users-request@intrepid.danplanet.com wrote: > On Sat, Oct 14, 2017 at 3:50 PM, rick via chirp_users > <chirp_users(a)intrepid.danplanet.com> wrote: >> Running Linux Mint 18.2 >> >> Loaded newest release version of Chirp-daily (CHIRP daily-20171013) >> >> When I try to download from radio, this error message is displayed before I >> can press send on the radio >> >> X An error has occurred >> Could not configure port: (5, 'input/output error') >> >> Attached png is screengrab >> >> I did some further digging and tried the first 10 "ttyS*" with the same >> results. >> >> lsusb command provides bus and device numbers but not which ttyS* is in use. >> >> Any Help? >> > I also run Linux Mint here. If you are using a USB based programming > cable you must scroll all the way down to the bottom of the list and > choose: /dev/ttyUSB0 > > Jim > Also make sure you are a member of the 'dialout' group (that is not the default case, sadly) else no serial port's (of whatever type) will be available to you. Open a terminal window, (and make it wide so lines don't wrap, making it much easier to see what's going on.) Then... dave-XPS-L502X ~ $*groups* dave adm/dialout/ cdrom sudo dip plugdev lpadmin sambashare wireshark (Everything BEFORE and including the '$' is the system prompt on the first line.? Your machine will be different. The command 'groups' was the entered command.?? The line under that is the system response) If 'dialout' does not appear in that list.?? Then do this... (Substitute <name> for/your/ login username,? sudo will ask for your login password.) dave-XPS-L502X ~ $*sudo adduser <name> dialout* You'll see a reply saying if you've been added to the dialout group, or are already a member. /*If */you were just added to that group, then, log out and log back in again (no need to reboot) and you'll now have access to the serial ports. An easy way to find out what port something is assigned to, is (again, in a terminal window) dave-XPS-L502X ~ $ *ls /dev/ttyU** /dev/ttyUSB0 This will list all attached and configured USB based serial ports. If you have multiple USB serial devices, then do that before and after connecting a new device, to find out what "device ID" the new device is assigned to. Hope something here helps. 73. Dave B Results; rick@rick-ham ~ $ groups rick adm dialout cdrom sudo dip plugdev lpadmin sambashare rick@rick-ham ~ $ ls /dev/ttyU** ls: cannot access '/dev/ttyU**': No such file or directory << with Yaesu cord plugged in rick@rick-ham ~ $ ls /dev/ttyU** ls: cannot access '/dev/ttyU**': No such file or directory << with RT systems cord plugged in 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 010: ID 2100:9068 RT Systems Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub rick@rick-ham ~ $ ls /dev autofs i2c-4 rfkill tty11 tty39 tty9 ttyS6 block initctl rtc tty12 tty4 ttyprintk ttyS7 bsg input rtc0 tty13 tty40 ttyS0 ttyS8 btrfs-control kmsg sda tty14 tty41 ttyS1 ttyS9 bus lightnvm sdb tty15 tty42 ttyS10 uhid cdrom log sdc tty16 tty43 ttyS11 uinput cdrw loop0 sdd tty17 tty44 ttyS12 urandom char loop1 sde tty18 tty45 ttyS13 usb console loop2 sdf tty19 tty46 ttyS14 userio core loop3 sdf1 tty2 tty47 ttyS15 vcs cpu_dma_latency loop4 sdf2 tty20 tty48 ttyS16 vcs1 cuse loop5 sdf5 tty21 tty49 ttyS17 vcs2 disk loop6 sg0 tty22 tty5 ttyS18 vcs3 dri loop7 sg1 tty23 tty50 ttyS19 vcs4 dvd loop-control sg2 tty24 tty51 ttyS2 vcs5 dvdrw mapper sg3 tty25 tty52 ttyS20 vcs6 ecryptfs mcelog sg4 tty26 tty53 ttyS21 vcsa fb0 mem sg5 tty27 tty54 ttyS22 vcsa1 fd memory_bandwidth sg6 tty28 tty55 ttyS23 vcsa2 full mqueue shm tty29 tty56 ttyS24 vcsa3 fuse net snapshot tty3 tty57 ttyS25 vcsa4 hidraw0 network_latency snd tty30 tty58 ttyS26 vcsa5 hidraw1 network_throughput sr0 tty31 tty59 ttyS27 vcsa6 hpet null stderr tty32 tty6 ttyS28 vfio hugepages port stdin tty33 tty60 ttyS29 vga_arbiter hwrng ppp stdout tty34 tty61 ttyS3 vhci i2c-0 psaux tty tty35 tty62 ttyS30 vhost-net i2c-1 ptmx tty0 tty36 tty63 ttyS31 zero i2c-2 pts tty1 tty37 tty7 ttyS4 i2c-3 random tty10 tty38 tty8 ttyS5 rick@rick-ham ~ $ ls /dev/usb hiddev0 rick@rick-ham ~ $ ls /dev/usb << with RT systems cord unplugged hiddev0 rick@rick-ham ~ $

1 0

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

16 Oct '17

Please ignore there are some spurious *'s creeping in, where in this case, it makes the text bold. My mistake in formatting the message to emphasize things. :-( Other than the command line command ls /dev/ttyU* please ignore them! 73. Dave B. On 16/10/17 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 16 Oct 2017 09:11:40 +0100 > From: Dave B <g8kbv(a)uku.co.uk> > Subject: Re: [chirp_users] Connecting to my FT2DR > To: chirp_users(a)intrepid.danplanet.com > Message-ID: <8bbf66d1-c00e-161d-c946-780fffa8de0a(a)uku.co.uk> > Content-Type: text/plain; charset="utf-8" > > On 15/10/17 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: >> On Sat, Oct 14, 2017 at 3:50 PM, rick via chirp_users >> <chirp_users(a)intrepid.danplanet.com> wrote: >>> Running Linux Mint 18.2 >>> >>> Loaded newest release version of Chirp-daily (CHIRP daily-20171013) >>> >>> When I try to download from radio, this error message is displayed before I >>> can press send on the radio >>> >>> X An error has occurred >>> Could not configure port: (5, 'input/output error') >>> >>> Attached png is screengrab >>> >>> I did some further digging and tried the first 10 "ttyS*" with the same >>> results. >>> >>> lsusb command provides bus and device numbers but not which ttyS* is in use. >>> >>> Any Help? >>> >> I also run Linux Mint here. If you are using a USB based programming >> cable you must scroll all the way down to the bottom of the list and >> choose: /dev/ttyUSB0 >> >> Jim >> > Also make sure you are a member of the 'dialout' group (that is not the > default case, sadly) else no serial port's (of whatever type) will be > available to you. > > Open a terminal window, (and make it wide so lines don't wrap, making it > much easier to see what's going on.) > > Then... > > dave-XPS-L502X ~ $ *groups* > dave adm /dialout/ cdrom sudo dip plugdev lpadmin sambashare wireshark > > (Everything BEFORE and including the '$' is the system prompt on the > first line.? Your machine will be different. > The command 'groups' was the entered command.?? The line under that is > the system response) > > If 'dialout' does not appear in that list.?? Then do this... > (Substitute <name> for /your/ login username,? sudo will ask for your > login password.) > > dave-XPS-L502X ~ $ *sudo adduser <name> dialout* > > You'll see a reply saying if you've been added to the dialout group, or > are already a member. > > /*If */you were just added to that group, then, log out and log back in > again (no need to reboot) and you'll now have access to the serial ports. > > An easy way to find out what port something is assigned to, is (again, > in a terminal window) > > dave-XPS-L502X ~ $ *ls /dev/ttyU** > /dev/ttyUSB0 > > This will list all attached and configured USB based serial ports. > > If you have multiple USB serial devices, then do that before and after > connecting a new device, to find out what "device ID" the new device is > assigned to. > > Hope something here helps. > > 73. > > Dave B > > >

1 0

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

16 Oct '17

On 15/10/17 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > On Sat, Oct 14, 2017 at 3:50 PM, rick via chirp_users > <chirp_users(a)intrepid.danplanet.com> wrote: >> Running Linux Mint 18.2 >> >> Loaded newest release version of Chirp-daily (CHIRP daily-20171013) >> >> When I try to download from radio, this error message is displayed before I >> can press send on the radio >> >> X An error has occurred >> Could not configure port: (5, 'input/output error') >> >> Attached png is screengrab >> >> I did some further digging and tried the first 10 "ttyS*" with the same >> results. >> >> lsusb command provides bus and device numbers but not which ttyS* is in use. >> >> Any Help? >> > I also run Linux Mint here. If you are using a USB based programming > cable you must scroll all the way down to the bottom of the list and > choose: /dev/ttyUSB0 > > Jim > Also make sure you are a member of the 'dialout' group (that is not the default case, sadly) else no serial port's (of whatever type) will be available to you. Open a terminal window, (and make it wide so lines don't wrap, making it much easier to see what's going on.) Then... dave-XPS-L502X ~ $ *groups* dave adm /dialout/ cdrom sudo dip plugdev lpadmin sambashare wireshark (Everything BEFORE and including the '$' is the system prompt on the first line. Your machine will be different. The command 'groups' was the entered command. The line under that is the system response) If 'dialout' does not appear in that list. Then do this... (Substitute <name> for /your/ login username, sudo will ask for your login password.) dave-XPS-L502X ~ $ *sudo adduser <name> dialout* You'll see a reply saying if you've been added to the dialout group, or are already a member. /*If */you were just added to that group, then, log out and log back in again (no need to reboot) and you'll now have access to the serial ports. An easy way to find out what port something is assigned to, is (again, in a terminal window) dave-XPS-L502X ~ $ *ls /dev/ttyU** /dev/ttyUSB0 This will list all attached and configured USB based serial ports. If you have multiple USB serial devices, then do that before and after connecting a new device, to find out what "device ID" the new device is assigned to. Hope something here helps. 73. Dave B

1 0

[chirp_users] Yaesu Vx8dr question
by serialman 14 Oct '17

14 Oct '17

Great Product I am using this product with my yeasu vx8dr and I have noticed one problem. The Ux and Lx memories are not displayed and this are not programmable through chirpw Is there anyway to program the U1/L1 through U10/L10 with chirpw? Thanks Chip

3 5

[chirp_users] Connecting to my FT2DR
by rick 14 Oct '17

14 Oct '17

Running Linux Mint 18.2 Loaded newest release version of Chirp-daily (CHIRP daily-20171013) When I try to download from radio, this error message is displayed before I can press send on the radio X An error has occurred Could not configure port: (5, 'input/output error') Attached png is screengrab I did some further digging and tried the first 10 "ttyS*" with the same results. lsusb command provides bus and device numbers but not which ttyS* is in use. Any Help?

2 1

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

13 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-20171013 A list of the changes included in this build (since the last daily) follows: Changes for Build #502 [Dan Smith <dsmith(a)danplanet.com>] Remove leftover debug from #5237

1 0

[chirp_users] IC-746PRO?
by Dan Romanchik KB6NU 12 Oct '17

12 Oct '17

Has anyone been successful getting Chirp to work with an ICOM IC-746PRO? Here, Chirp seems to go through the motions of talking to my IC-746PRO, but it never downloads the memory, nor does it allow me to program any of the memories. 73! Dan KB6NU ---------------------------------------------------------- CW Geek, Ham Radio Instructor Author of the "No Nonsense" amateur radio license study guides Read my ham radio blog at http://www.kb6nu.com

1 0

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

12 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-20171012 A list of the changes included in this build (since the last daily) follows: Changes for Build #501 [Dan Smith <dsmith(a)danplanet.com>] Fix long-standing test runner output bug The unified logging code arrests stdout for the purposes of non-interactive console logging to a file. This has been preventing proper console output when running in the build system, making it harder to debug failures. This adds a CHIRP_TESTENV override environment variable, and always sets it from the test runner since we should always have interactive output from it. Related to #5237 [Dan Smith <dsmith(a)danplanet.com>] Remove unnecessary test tools After #5237 these are no longer necessary and duplicative. [Dan Smith <dsmith(a)danplanet.com>] Add tox.ini for running tests Tox handles venv creation and management of setup install for running tests. Since we have a venv required already, this just makes sense. Now, instead of: ./run_all_tests.sh You can just run: tox Assuming you have tox installed (pip install tox). You can run individual test groups like this: tox -e unit tox -e driver and still pass arguments to the driver tests per usual with: tox -e driver -- -d Icom_IC-2200H I'll be working to make the build system use tox for running tests with better isolation and hopefully more repeatability. #5237 [Dan Smith <dsmith(a)danplanet.com>] Some fixes to run_tests First, in r2787 we made the BruteForce test do RadioFeatures validation on a memory, avoiding a failure if the memory did not validate. For some reason we still required that radio.validate_memory() pass for any of those tests, which doesn't allow for the radio to ban quirks in the tests. This makes us not fail if the radio rightly fails to validate. Second, we were modifying the memory in do_mode() so that once we passed FM in the mode sequence we were always trying freq+100Mhz. Depending on how we ran the tests (i.e. which order we hit the modes) this would sometimes fail. This makes us copy the original memory so we're stable throughout the modes. Related to #5237 [Dan Smith <dsmith(a)danplanet.com>] [icq7] Add validate_memory() for sub-30MHz AM requirement This driver has a requirement that anything under 30MHz be AM. Validate that in validate_memory() so we can properly handle cases where that won't work. Found in the pursuit of #5237 [Dan Smith <dsmith(a)danplanet.com>] Remove dedicated silly rptbuild setup handler This just makes setup.py more complicated and there's no reason to build this as a separate package. Just build it as an additional script on the main default build. Needed for #5237 [Dan Smith <dsmith(a)danplanet.com>] Let make_supported.py take an output filename as the first argument Needed for #5237 [Dan Smith <dsmith(a)danplanet.com>] More pep8 compliance fixes #2355 [Imuli <i(a)imu.li>] [uv5r] UV-82 use ASCII charset Partially fixes #5227 The UV-82 supports all of ASCII (with two replacements). I imagine other Baofeng radios do also, so this provides an easy means to specify supported characters for different models.

1 0