[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-20151005
A list of the changes included in this build (since the last daily) follows:
Changes for Build #361 [Cody P Schafer dev@codyps.com] drivers/ft60: remove extra "(None)" in duplex drop down (#2893)
ft60's driver uses the DUPLEX variable's indexes as the stored values in radio memory, and there are 2 empty string ("") options. Make chirpw's interface a bit nicer looking by hiding one of them (arbitrarily chose to hide the first as that is convenient code-wise).
[Cody P Schafer dev@codyps.com] drivers/ft60: add support for "off" duplex mode (#2891)
By using a tx frequency of '0', the radio (or at least my ft60) refuses to transmit (gives "ERROR" on the screen) when the PTT key is pressed.
I have been reading the discussions on the discussion board and have a simple question. I have a vs of Chirp that is working perfectly on my 5-v2+…. Why should I download a later vs and chance that something is different?
Tom
On Oct 5, 2015, at 12:07 AM, Build System via chirp_users chirp_users@intrepid.danplanet.com wrote:
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-20151005
A list of the changes included in this build (since the last daily) follows:
Changes for Build #361 [Cody P Schafer dev@codyps.com] drivers/ft60: remove extra "(None)" in duplex drop down (#2893)
ft60's driver uses the DUPLEX variable's indexes as the stored values in radio memory, and there are 2 empty string ("") options. Make chirpw's interface a bit nicer looking by hiding one of them (arbitrarily chose to hide the first as that is convenient code-wise).
[Cody P Schafer dev@codyps.com] drivers/ft60: add support for "off" duplex mode (#2891)
By using a tx frequency of '0', the radio (or at least my ft60) refuses to transmit (gives "ERROR" on the screen) when the PTT key is pressed.
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
The chance that something is different is actually a good thing.
Some radios such as the Baofeng series, make changes to the firmware on a regular basis. Cross Loading images from one radio to another with a different F/W version could disable the new radio. Added measures to prevent this are built into CHIRP. New features, improvements and updates are being added.
I personally always use the Latest Daily Build.
John
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Tom Sent: Monday, October 05, 2015 12:07 PM To: Build System; Discussion of CHIRP Subject: Re: [chirp_users] New Daily Build
I have been reading the discussions on the discussion board and have a simple question. I have a vs of Chirp that is working perfectly on my 5-v2+…. Why should I download a later vs and chance that something is different?
Tom
On Oct 5, 2015, at 12:07 AM, Build System via chirp_users chirp_users@intrepid.danplanet.com wrote:
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-20151005
A list of the changes included in this build (since the last daily) follows:
Changes for Build #361 [Cody P Schafer dev@codyps.com] drivers/ft60: remove extra "(None)" in duplex drop down (#2893)
ft60's driver uses the DUPLEX variable's indexes as the stored values in radio memory, and there are 2 empty string ("") options. Make chirpw's interface a bit nicer looking by hiding one of them (arbitrarily chose to hide the first as that is convenient code-wise).
[Cody P Schafer dev@codyps.com] drivers/ft60: add support for "off" duplex mode (#2891)
By using a tx frequency of '0', the radio (or at least my ft60) refuses to transmit (gives "ERROR" on the screen) when the PTT key is pressed.
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
_______________________________________________ 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.6140 / Virus Database: 4435/10763 - Release Date: 10/05/15
The chance that something is different is actually a good thing.
Yes, but also, every time a new build is generated, we tell you exactly what changed. For example:
A list of the changes included in this build (since the last daily) follows:
Changes for Build #361 [Cody P Schafer dev@codyps.com] drivers/ft60: remove extra "(None)" in duplex drop down (#2893)
ft60's driver uses the DUPLEX variable's indexes as the stored values in radio memory, and there are 2 empty string ("") options. Make chirpw's interface a bit nicer looking by hiding one of them (arbitrarily chose to hide the first as that is convenient code-wise).
[Cody P Schafer dev@codyps.com] drivers/ft60: add support for "off" duplex mode (#2891)
By using a tx frequency of '0', the radio (or at least my ft60) refuses to transmit (gives "ERROR" on the screen) when the PTT key is pressed.
There are two changes in this build and they only affect the Yaesu FT-60. Absolutely nothing else has changed. That means two things:
1. If you don't use an FT-60, you won't see any difference 2. If you upgrade anyway, you don't need to worry about breaking things
Staying on the latest daily is always a good idea, but there's really no reason to move unless you see that one of your radios is affected. Sometimes there are changes to the core, like a GUI improvement or something, which would apply to everyone. But, those will be described here in the same way.
There's nothing in the build that isn't shown in the list. In fact, the list of changes is compiled and reported by a machine based on actual changes to the code. So, you can absolutely use it as a way to decide whether you need to download and update what you have.
That said, if you don't follow all of them, understand what is said, or aren't sure when you last updated, then you should just always plan to be on the latest build.
Hope that helps,
--Dan
Thanks all… I will do so..
Tom
On Oct 5, 2015, at 10:28 AM, Dan Smith via chirp_users chirp_users@intrepid.danplanet.com wrote:
The chance that something is different is actually a good thing.
Yes, but also, every time a new build is generated, we tell you exactly what changed. For example:
A list of the changes included in this build (since the last daily) follows:
Changes for Build #361 [Cody P Schafer dev@codyps.com] drivers/ft60: remove extra "(None)" in duplex drop down (#2893)
ft60's driver uses the DUPLEX variable's indexes as the stored values in radio memory, and there are 2 empty string ("") options. Make chirpw's interface a bit nicer looking by hiding one of them (arbitrarily chose to hide the first as that is convenient code-wise).
[Cody P Schafer dev@codyps.com] drivers/ft60: add support for "off" duplex mode (#2891)
By using a tx frequency of '0', the radio (or at least my ft60) refuses to transmit (gives "ERROR" on the screen) when the PTT key is pressed.
There are two changes in this build and they only affect the Yaesu FT-60. Absolutely nothing else has changed. That means two things:
- If you don't use an FT-60, you won't see any difference
- If you upgrade anyway, you don't need to worry about breaking things
Staying on the latest daily is always a good idea, but there's really no reason to move unless you see that one of your radios is affected. Sometimes there are changes to the core, like a GUI improvement or something, which would apply to everyone. But, those will be described here in the same way.
There's nothing in the build that isn't shown in the list. In fact, the list of changes is compiled and reported by a machine based on actual changes to the code. So, you can absolutely use it as a way to decide whether you need to download and update what you have.
That said, if you don't follow all of them, understand what is said, or aren't sure when you last updated, then you should just always plan to be on the latest build.
Hope that helps,
--Dan _______________________________________________ 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
participants (4)
-
Build System -
Dan Smith -
John LaMartina -
Tom