[chirp_users] New Daily Build
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-20150210
A list of the changes included in this build (since the last daily) follows:
Changes for Build #324 [K. Arvanitis kosta@alumni.uvic.ca] Fixup wouxun radio settings
There was a small issue with the construction the top level radio settings group for some of the wouxun radios. This attempts to resolve that.
Bug #2285
Wondering if there is any trick to getting Chirp to work with the SainSonic AP510 tracker? I have a Slackware laptop that is running Vbox so I can fire up an XP client. I can connect the AP510 to /dev/ttyUSB0 change the permission so the "user" can use it with sudo, use Vbox to open the XP client and get the port recognized as a viable "com" port. The AP510 software will then work fine and program device no problem through this convoluted connection! :-)
If I simply connect the AP510 up by itself and change the permission on /dev/ttyUSB0 with sudo and fire up the "latest" Linux Chirp version, if I follow the command from Chirp to turn on the device it fails to read it every time.
I mean I suppose I could place the Windows version of Chirp on the XP client but I would prefer to leave it off.
Is the Linux version of Chirp unable to read/program the AP510? I'm using the provided cable. Kurt KC9LDH
On Wed, Feb 11, 2015 at 1:11 PM, Kurt ksaves2@sbcglobal.net wrote:
If I simply connect the AP510 up by itself and change the permission on /dev/ttyUSB0 with sudo and fire up the "latest" Linux Chirp version, if I follow the command from Chirp to turn on the device it fails to read it every time.
...
Is the Linux version of Chirp unable to read/program the AP510? I'm using the provided cable. Kurt KC9LDH
The non-working example you gave is how I program my AP510 every time, from Linux. I've only verified it works with the latest 20141008 (rx free) firmware. Is this the version you have?
My only other thought is that you are messing things up with permissions. My user is a member of the dialout group and I don't have to touch permissions to use the USB-serial port.
Tom KD7LXL
On Wed, Feb 11, 2015 at 1:21 PM, Tom Hayward tom@tomh.us wrote:
On Wed, Feb 11, 2015 at 1:11 PM, Kurt ksaves2@sbcglobal.net wrote:
Is the Linux version of Chirp unable to read/program the AP510? I'm using the provided cable. Kurt KC9LDH
The non-working example you gave is how I program my AP510 every time, from Linux. I've only verified it works with the latest 20141008 (rx free) firmware. Is this the version you have?
As mentioned in a private email, Kurt actually has firmware version 20141215. Thanks for tipping me off--this is a new version I haven't tested, and it was not released through the same channels as previous versions.
I flashed my AP510 with the new firmware and it woke up in a boot loop. I was eventually able to get it to connect to the stock programming software and load the default configuration. This tamed it. This is a good indication that some significant internal changes took place between versions.
I snooped the serial protocol a bit and found they modified the command to put it into configuration mode. This is why Chirp is unable to read your AP510. I have not looked much farther than this, however I suspect they did not change the initialization on a whim, but to prevent accidental programming with software intended for older versions.
I will need to take a thorough look at the new protocol before updating Chirp. Hopefully I can support both the new and old protocols concurrently, unlike the stock software.
Tom KD7LXL
I picked up a second unit and it apparently had an ancient bit of firmware on it. I didn't get the date but Chirp would read a frequency off of it. I flashed to the 12152014 firmware and Chirp isn't able to read it. So, it's a firmware issue. Also the transmit delay can't be changed but that's a Sainsonic issue and not Chirp. I may try flashing to an older firmware.
Location is here:
http://www.radioddity.com/us/avrt5-aprs-tracker-vhf-with-gps-bluetooth-therm...
Go to "Downloads" and click on "AP510 APRS Software" . Rename to *.zip and unpack. I virus scanned and it's O.K. KC9LDH
From: Tom Hayward tom@tomh.us To: Kurt ksaves2@sbcglobal.net; Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Wednesday, February 11, 2015 7:57 PM Subject: Re: [chirp_users] SainSonic AP510
On Wed, Feb 11, 2015 at 1:21 PM, Tom Hayward tom@tomh.us wrote:
On Wed, Feb 11, 2015 at 1:11 PM, Kurt ksaves2@sbcglobal.net wrote:
Is the Linux version of Chirp unable to read/program the AP510? I'm using the provided cable. Kurt KC9LDH
The non-working example you gave is how I program my AP510 every time, from Linux. I've only verified it works with the latest 20141008 (rx free) firmware. Is this the version you have?
As mentioned in a private email, Kurt actually has firmware version 20141215. Thanks for tipping me off--this is a new version I haven't tested, and it was not released through the same channels as previous versions.
I flashed my AP510 with the new firmware and it woke up in a boot loop. I was eventually able to get it to connect to the stock programming software and load the default configuration. This tamed it. This is a good indication that some significant internal changes took place between versions.
I snooped the serial protocol a bit and found they modified the command to put it into configuration mode. This is why Chirp is unable to read your AP510. I have not looked much farther than this, however I suspect they did not change the initialization on a whim, but to prevent accidental programming with software intended for older versions.
I will need to take a thorough look at the new protocol before updating Chirp. Hopefully I can support both the new and old protocols concurrently, unlike the stock software.
Tom KD7LXL
Yup, I flashed it to the 10/2014 firmware and Chirp reads it fine. Sooooooo, AP510 users, you flash to the 12152014 firmware and Chirp can no longer work with the device. Will have to use the programming software provided with the firmware. Nice thing is the device can be flashed back and forth very easily so one may play around with it and see what they like.
Kurt KC9LDH
________________________________ From: Kurt ksaves2@sbcglobal.net To: "chirp_users@intrepid.danplanet.com" chirp_users@intrepid.danplanet.com Sent: Saturday, February 14, 2015 2:11 PM Subject: Re: [chirp_users] SainSonic AP510
I picked up a second unit and it apparently had an ancient bit of firmware on it. I didn't get the date but Chirp would read a frequency off of it. I flashed to the 12152014 firmware and Chirp isn't able to read it. So, it's a firmware issue. Also the transmit delay can't be changed but that's a Sainsonic issue and not Chirp. I may try flashing to an older firmware.
Location is here:
http://www.radioddity.com/us/avrt5-aprs-tracker-vhf-with-gps-bluetooth-therm...
Go to "Downloads" and click on "AP510 APRS Software" . Rename to *.zip and unpack. I virus scanned and it's O.K. KC9LDH
From: Tom Hayward tom@tomh.us To: Kurt ksaves2@sbcglobal.net; Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Wednesday, February 11, 2015 7:57 PM Subject: Re: [chirp_users] SainSonic AP510
On Wed, Feb 11, 2015 at 1:21 PM, Tom Hayward tom@tomh.us wrote:
On Wed, Feb 11, 2015 at 1:11 PM, Kurt ksaves2@sbcglobal.net wrote:
Is the Linux version of Chirp unable to read/program the AP510? I'm using the provided cable. Kurt KC9LDH
The non-working example you gave is how I program my AP510 every time, from Linux. I've only verified it works with the latest 20141008 (rx free) firmware. Is this the version you have?
As mentioned in a private email, Kurt actually has firmware version 20141215. Thanks for tipping me off--this is a new version I haven't tested, and it was not released through the same channels as previous versions.
I flashed my AP510 with the new firmware and it woke up in a boot loop. I was eventually able to get it to connect to the stock programming software and load the default configuration. This tamed it. This is a good indication that some significant internal changes took place between versions.
I snooped the serial protocol a bit and found they modified the command to put it into configuration mode. This is why Chirp is unable to read your AP510. I have not looked much farther than this, however I suspect they did not change the initialization on a whim, but to prevent accidental programming with software intended for older versions.
I will need to take a thorough look at the new protocol before updating Chirp. Hopefully I can support both the new and old protocols concurrently, unlike the stock software.
Tom KD7LXL
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Feb 14, 2015 8:35 PM, "Kurt" ksaves2@sbcglobal.net wrote:
Yup, I flashed it to the 10/2014 firmware and Chirp reads it fine.
Sooooooo, AP510 users, you flash to the 12152014 firmware and
Chirp can no longer work with the device.
I spent about five minutes with the new firmware and got Chirp to read it. I'll need to add some logic to differentiate between the two protocols, and update the decoding for the fields they rewrote, like SmartBeaconing. It shouldn't be too long until I have a Chirp update out for the new firmware.
Tom KD7LXL
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Works fine for me in Ubuntu. User is added to group dialout for access to serial ports. No need to use sudo.
On 02/11/2015 03:11 PM, Kurt wrote:
Wondering if there is any trick to getting Chirp to work with the SainSonic AP510 tracker? I have a Slackware laptop that is running Vbox so I can fire up an XP client. I can connect the AP510 to /dev/ttyUSB0 change the permission so the "user" can use it with sudo, use Vbox to open the XP client and get the port recognized as a viable "com" port. The AP510 software will then work fine and program device no problem through this convoluted connection! :-)
If I simply connect the AP510 up by itself and change the permission on /dev/ttyUSB0 with sudo and fire up the "latest" Linux Chirp version, if I follow the command from Chirp to turn on the device it fails to read it every time.
I mean I suppose I could place the Windows version of Chirp on the XP client but I would prefer to leave it off.
Is the Linux version of Chirp unable to read/program the AP510? I'm using the provided cable. Kurt KC9LDH
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users Unsubscribe: http://intrepid.danplanet.com/mailman/options/chirp_users
- -- /************************************************* * Amateur Radio Station AC0HY * * W. Paul Mills SN807 * * Assistant EC Alpha-1 ARES Shawnee/Wabunsee, KS * * President Kaw Valley Amateur Radio Club * *************************************************/
Chirp can be used to program the Baofeng UV-3R. Is that also true for the new UV-3R+ as it is not specifically listed on the website. Richard AG5M
Yes, I use it with my UV3R+
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Richard AG5M Sent: Saturday, March 21, 2015 12:48 PM To: Discussion of CHIRP Subject: [chirp_users] Question UV-3R and UV-3R+
Chirp can be used to program the Baofeng UV-3R. Is that also true for the new UV-3R+ as it is not specifically listed on the website. Richard AG5M
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5856 / Virus Database: 4311/9351 - Release Date: 03/21/15
participants (6)
-
Build System -
John LaMartina -
Kurt -
Richard AG5M -
Tom Hayward -
W Paul Mills