[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-20190925
A list of the changes included in this build (since the last daily) follows:
Changes for Build #593 [Rick DeWitt aa0rd@yahoo.com] [icf.py] Add download checksum calculation per issue #7075 Added logic in process_data_frame to calculate and compare csum. Issue #7075
Changes for Build #594
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:
This set includes a new "unified" MacOS build, which could use some testing. It bundles the entire runtime with the app itself, which means you do not need install it separately. Ideally for testing, you would *remove* the runtime from your system (which unfortunately Apple does not make very easy). If anyone has a spare MacOS system, virtual machine, or can clean the runtime from their system for testing, I'd surely appreciate some feedback about how this is (or is not) working, either here or on the relevant issue:
https://chirp.danplanet.com/issues/6443
Many thanks to Barry Nelson for his work on this!
Note that this unified build uses the system python runtime, and all the libraries are 64-bit. I get no warnings about 32-bit deprecation when I run it on a test system, so I *hope* this gets us out of Catalina jail...
Thanks!
--Dan
I can do some that testing here. I dont know if you’ve read my long winded email a couple weeks back regarding how the macOs version locks up the serial device hard while using the new Wouxon KG-8* drivers. This can only be duplicated when chirp is running under macOS. So Im under the impression that it has something to do with the runtime. I have both systems in High Sierra and Mojave . So I can check how well it can backward compat
Lynda
On Sep 25, 2019, at 7:27 AM, Dan Smith dsmith@danplanet.com wrote:
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:
This set includes a new "unified" MacOS build, which could use some testing. It bundles the entire runtime with the app itself, which means you do not need install it separately. Ideally for testing, you would *remove* the runtime from your system (which unfortunately Apple does not make very easy). If anyone has a spare MacOS system, virtual machine, or can clean the runtime from their system for testing, I'd surely appreciate some feedback about how this is (or is not) working, either here or on the relevant issue:
https://chirp.danplanet.com/issues/6443
Many thanks to Barry Nelson for his work on this!
Note that this unified build uses the system python runtime, and all the libraries are 64-bit. I get no warnings about 32-bit deprecation when I run it on a test system, so I *hope* this gets us out of Catalina jail...
Thanks!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Lynda Leung at x-rogue@mermaid.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I can do some that testing here. I dont know if you’ve read my long winded email a couple weeks back regarding how the macOs version locks up the serial device hard while using the new Wouxon KG-8* drivers. This can only be duplicated when chirp is running under macOS. So Im under the impression that it has something to do with the runtime.
No, that would be a driver problem. USB serial drivers on MacOS are generally pretty terrible. There is absolutely nothing that something in userland (an application) should be able to do to lock up a piece of hardware, especially something so simple as serial communication. There is nothing in the runtime relating to low-level serial communication. The reason that it doesn't happen on other OSes is because their drivers are better. This is the reason I've pretty much stopped using MacOS for any of my serial activities (CHIRP or otherwise).
The KeySpan drivers have always been the best supported under MacOS, and for anything that uses a 9-pin regular serial connector, I could always use the KeySpan to do what I needed. However, most everything I get nowadays has a USB converter in the cable shell. If I were to cut that off and rewire them all (which you could do) then I'd be able to continue, but that's just totally not worth it.
--Dan
Thanks for the tip. I actually have a keyspan serial port on my system. I’ll see If I can find a 9 pin everything else cable. But I mostly use a prolific device too, only because has a Kenwood style plug. Whats really odd is that I dont any issues with any other radios other than the KG-UV8* series, chirp won’t get stuck. No issues with all the Baofeng, Btech, Yaesu’s Windows VM running under MacOs as can use the Wouxun KG-UV8* driver is fine too. Thats why Im kinda not thinking its entirely a serial driver issue, but more an interaction with that chirp code than anything. I might still be wrong . Lynda
On Sep 26, 2019, at 6:38 AM, Dan Smith dsmith@danplanet.com wrote:
I can do some that testing here. I dont know if you’ve read my long winded email a couple weeks back regarding how the macOs version locks up the serial device hard while using the new Wouxon KG-8* drivers. This can only be duplicated when chirp is running under macOS. So Im under the impression that it has something to do with the runtime.
No, that would be a driver problem. USB serial drivers on MacOS are generally pretty terrible. There is absolutely nothing that something in userland (an application) should be able to do to lock up a piece of hardware, especially something so simple as serial communication. There is nothing in the runtime relating to low-level serial communication. The reason that it doesn't happen on other OSes is because their drivers are better. This is the reason I've pretty much stopped using MacOS for any of my serial activities (CHIRP or otherwise).
The KeySpan drivers have always been the best supported under MacOS, and for anything that uses a 9-pin regular serial connector, I could always use the KeySpan to do what I needed. However, most everything I get nowadays has a USB converter in the cable shell. If I were to cut that off and rewire them all (which you could do) then I'd be able to continue, but that's just totally not worth it.
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Lynda Leung at x-rogue@mermaid.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I don’t have a Mac to use, but might the problem be the at least 2 versions of the 8? I have an 8E, which is a tri band ham only, I think the other version is 2m/440 and maybe Part 90 compliant. You can use software from Powerwerx.com to program these radios. 2 different software versions, I think.
Jardy Dawson WA7JRD
Message sent from some electronic device that only the Manufacturer of said device really cares about.
On Sep 26, 2019, at 11:15, Mermaid x-rogue@mermaid.org wrote:
Thanks for the tip. I actually have a keyspan serial port on my system. I’ll see If I can find a 9 pin everything else cable. But I mostly use a prolific device too, only because has a Kenwood style plug. Whats really odd is that I dont any issues with any other radios other than the KG-UV8* series, chirp won’t get stuck. No issues with all the Baofeng, Btech, Yaesu’s Windows VM running under MacOs as can use the Wouxun KG-UV8* driver is fine too. Thats why Im kinda not thinking its entirely a serial driver issue, but more an interaction with that chirp code than anything. I might still be wrong . Lynda
On Sep 26, 2019, at 6:38 AM, Dan Smith dsmith@danplanet.com wrote:
I can do some that testing here. I dont know if you’ve read my long winded email a couple weeks back regarding how the macOs version locks up the serial device hard while using the new Wouxon KG-8* drivers. This can only be duplicated when chirp is running under macOS. So Im under the impression that it has something to do with the runtime.
No, that would be a driver problem. USB serial drivers on MacOS are generally pretty terrible. There is absolutely nothing that something in userland (an application) should be able to do to lock up a piece of hardware, especially something so simple as serial communication. There is nothing in the runtime relating to low-level serial communication. The reason that it doesn't happen on other OSes is because their drivers are better. This is the reason I've pretty much stopped using MacOS for any of my serial activities (CHIRP or otherwise).
The KeySpan drivers have always been the best supported under MacOS, and for anything that uses a 9-pin regular serial connector, I could always use the KeySpan to do what I needed. However, most everything I get nowadays has a USB converter in the cable shell. If I were to cut that off and rewire them all (which you could do) then I'd be able to continue, but that's just totally not worth it.
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Lynda Leung at x-rogue@mermaid.org 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 Jardy at jardy72@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Jardy,
Native Chirp drivers were developed and released this past May. It works fine until a recent macOS update. The OEM software is garbage, and thus there are reasons why a native chirp drivers was developed. I know these radios pretty well, as I am also an official direct wouxun dealer, and have dived pretty deep into the inner workings of these.
The E and T models are practically the same. Only real difference is that the firmware defaults to english upon reset, and the scrambler option is removed.
Lynda
On Sep 26, 2019, at 1:05 PM, Jardy via chirp_users chirp_users@intrepid.danplanet.com wrote:
I don’t have a Mac to use, but might the problem be the at least 2 versions of the 8? I have an 8E, which is a tri band ham only, I think the other version is 2m/440 and maybe Part 90 compliant. You can use software from Powerwerx.com to program these radios. 2 different software versions, I think.
Jardy Dawson WA7JRD
Message sent from some electronic device that only the Manufacturer of said device really cares about.
On Sep 26, 2019, at 11:15, Mermaid x-rogue@mermaid.org wrote:
Thanks for the tip. I actually have a keyspan serial port on my system. I’ll see If I can find a 9 pin everything else cable. But I mostly use a prolific device too, only because has a Kenwood style plug. Whats really odd is that I dont any issues with any other radios other than the KG-UV8* series, chirp won’t get stuck. No issues with all the Baofeng, Btech, Yaesu’s Windows VM running under MacOs as can use the Wouxun KG-UV8* driver is fine too. Thats why Im kinda not thinking its entirely a serial driver issue, but more an interaction with that chirp code than anything. I might still be wrong . Lynda
On Sep 26, 2019, at 6:38 AM, Dan Smith dsmith@danplanet.com wrote:
I can do some that testing here. I dont know if you’ve read my long winded email a couple weeks back regarding how the macOs version locks up the serial device hard while using the new Wouxon KG-8* drivers. This can only be duplicated when chirp is running under macOS. So Im under the impression that it has something to do with the runtime.
No, that would be a driver problem. USB serial drivers on MacOS are generally pretty terrible. There is absolutely nothing that something in userland (an application) should be able to do to lock up a piece of hardware, especially something so simple as serial communication. There is nothing in the runtime relating to low-level serial communication. The reason that it doesn't happen on other OSes is because their drivers are better. This is the reason I've pretty much stopped using MacOS for any of my serial activities (CHIRP or otherwise).
The KeySpan drivers have always been the best supported under MacOS, and for anything that uses a 9-pin regular serial connector, I could always use the KeySpan to do what I needed. However, most everything I get nowadays has a USB converter in the cable shell. If I were to cut that off and rewire them all (which you could do) then I'd be able to continue, but that's just totally not worth it.
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Lynda Leung at x-rogue@mermaid.org 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 Jardy at jardy72@yahoo.com 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 Lynda Leung at x-rogue@mermaid.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
participants (4)
-
Build System -
Dan Smith -
Jardy -
Mermaid