[chirp_users] New chirp-next build

[donotreply]

Greetings,

A new build of CHIRP-next is available. This includes changes made directly to 
the tree since yesterday and may include additional features, bug fixes, etc. 
As a reminder, this is different from the "daily" CHIRP builds in that new 
development and features are happening here. It is the latest and greatest, but 
also may be less stable than the "daily" builds at this time. If it works for 
you, we recommend using CHIRP-next, but if your radio is not yet working on it, 
then you may prefer to use the "daily" builds for the time being.

You can get it from here:

http://trac.chirp.danplanet.com/chirp_next/

A list of changes since the last build are here:

Changes for Build #35
[3046399+kk7ds] Fix insert/delete operations off-by-one

[3046399+kk7ds] Re-fix UV3R for python 3

[3046399+kk7ds] Disable selecting rows in the bank editor

[3046399+kk7ds] [uv5r.py] Add ability to upload all ranges

[3046399+kk7ds] Add DN to mode list for Yaesu System Fusion

[3046399+kk7ds] Make RepeaterBook return YSF (DN mode) repeaters

[3046399+kk7ds] Add mode filtering to RepeaterBook query

[3046399+kk7ds] Fix bug in RepeaterBook band selection

[3046399+kk7ds] Add __contains__ handler for RadioSettingGroup

[3046399+kk7ds] Fix setting boolean mem.extra properties

[3046399+kk7ds] Fix post-properties memory refresh

[3046399+kk7ds] Add DN mode support to FT1, FT2, FT3___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] New chirp-next build

[Dan Smith via chirp_users]

> [3046399+kk7ds] Add DN to mode list for Yaesu System Fusion
> 
> [3046399+kk7ds] Make RepeaterBook return YSF (DN mode) repeaters
> 
> [3046399+kk7ds] Add DN mode support to FT1, FT2, FT3

I'm not sure if anyone noticed this, but these are the first radios to have any 
sort of Yaesu System Fusion support in CHIRP. Honestly, it's a bit of a tough 
thing to wedge in, as YSF is a little strange. I'm not a YSF guy, so I'd 
appreciate any feedback on this (here if positive, and in a bug if you find an 
issue).

I tested this with an FT3, but I'm hopeful that it works for the FT1 and FT2. 
If anyone has one of those models and can confirm, that would be helpful.

Hopefully some of the other developers who contributed the other YSF radios 
will be able to circle back and extend those to support it as well in time.

--Dan
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] New chirp-next build

[Matt Foster]

I have a 7250, so if you get YSF support for that radio, I’d be happy to
test it!


On Thu, Jan 12, 2023 at 4:46 PM Dan Smith via chirp_users <
chirp_users@intrepid.danplanet.com> wrote:

> > [3046399+kk7ds] Add DN to mode list for Yaesu System Fusion
> >
> > [3046399+kk7ds] Make RepeaterBook return YSF (DN mode) repeaters
> >
> > [3046399+kk7ds] Add DN mode support to FT1, FT2, FT3
>
> I'm not sure if anyone noticed this, but these are the first radios to
> have any sort of Yaesu System Fusion support in CHIRP. Honestly, it's a bit
> of a tough thing to wedge in, as YSF is a little strange. I'm not a YSF
> guy, so I'd appreciate any feedback on this (here if positive, and in a bug
> if you find an issue).
>
> I tested this with an FT3, but I'm hopeful that it works for the FT1 and
> FT2. If anyone has one of those models and can confirm, that would be
> helpful.
>
> Hopefully some of the other developers who contributed the other YSF
> radios will be able to circle back and extend those to support it as well
> in time.
>
> --Dan
> ___
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Matt Foster at wedg...@gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscr...@intrepid.danplanet.com
> To report this email as off-topic, please email
> chirp_users-ow...@intrepid.danplanet.com
> Searchable archive:
> https://www.mail-archive.com/chirp_users@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 arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] New chirp-next build

[Dan Smith via chirp_users]

> I have a 7250, so if you get YSF support for that radio, I’d be happy to test 
> it!

Have you tested it at all with CHIRP? There's a bug report open that makes the 
driver look super broken, but I'm wondering if it's a firmware version issue:

https://chirp.danplanet.com/issues/10251

I'd love to know if it works for you, as I didn't write the driver so I don't 
know much about it. If it does work for you, that driver inherits from the FT1 
base class like the others, so I *hope* enabling the YSF stuff for it would be 
easy if there's a tester handy.

--Dan
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] New chirp-next build

[Wayne]

Feedback...

I've just tested Chirp-Next-20230112 on my FT-70D.
Once I sorted out the correct Com port, both download and upload worked 
as expected.
Many thanks to the developers for all their work .

Wayne (VK6VE)


On 13/01/2023 6:45 am, Dan Smith via chirp_users wrote:
>> [3046399+kk7ds] Add DN to mode list for Yaesu System Fusion
>>
>> [3046399+kk7ds] Make RepeaterBook return YSF (DN mode) repeaters
>>
>> [3046399+kk7ds] Add DN mode support to FT1, FT2, FT3
> I'm not sure if anyone noticed this, but these are the first radios to have 
> any sort of Yaesu System Fusion support in CHIRP. Honestly, it's a bit of a 
> tough thing to wedge in, as YSF is a little strange. I'm not a YSF guy, so 
> I'd appreciate any feedback on this (here if positive, and in a bug if you 
> find an issue).
>
> I tested this with an FT3, but I'm hopeful that it works for the FT1 and FT2. 
> If anyone has one of those models and can confirm, that would be helpful.
>
> Hopefully some of the other developers who contributed the other YSF radios 
> will be able to circle back and extend those to support it as well in time.
>
> --Dan
> ___
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Wayne at wildca...@iinet.net.au
> To unsubscribe, send an email to 
> chirp_users-unsubscr...@intrepid.danplanet.com
> To report this email as off-topic, please email 
> chirp_users-ow...@intrepid.danplanet.com
> Searchable archive: 
> https://www.mail-archive.com/chirp_users@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 arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] New chirp-next build

[David Boucha]

Since you've brought up Yaesu & System Fusion...   I have an FTM-400 that I
love. (Though I haven't set it up since I moved about 6 months ago).
Has any work been done on supporting the FTM-400 in chirp? Is it
technically possible?

On Thu, Jan 12, 2023 at 3:45 PM Dan Smith via chirp_users <
chirp_users@intrepid.danplanet.com> wrote:

> > [3046399+kk7ds] Add DN to mode list for Yaesu System Fusion
> >
> > [3046399+kk7ds] Make RepeaterBook return YSF (DN mode) repeaters
> >
> > [3046399+kk7ds] Add DN mode support to FT1, FT2, FT3
>
> I'm not sure if anyone noticed this, but these are the first radios to
> have any sort of Yaesu System Fusion support in CHIRP. Honestly, it's a bit
> of a tough thing to wedge in, as YSF is a little strange. I'm not a YSF
> guy, so I'd appreciate any feedback on this (here if positive, and in a bug
> if you find an issue).
>
> I tested this with an FT3, but I'm hopeful that it works for the FT1 and
> FT2. If anyone has one of those models and can confirm, that would be
> helpful.
>
> Hopefully some of the other developers who contributed the other YSF
> radios will be able to circle back and extend those to support it as well
> in time.
>
> --Dan
> ___
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to UtahDave at bou...@gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscr...@intrepid.danplanet.com
> To report this email as off-topic, please email
> chirp_users-ow...@intrepid.danplanet.com
> Searchable archive:
> https://www.mail-archive.com/chirp_users@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 arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] New chirp-next build

[Dan Smith via chirp_users]

> Since you've brought up Yaesu & System Fusion...   I have an FTM-400 that I 
> love. (Though I haven't set it up since I moved about 6 months ago).
> Has any work been done on supporting the FTM-400 in chirp? Is it technically 
> possible?

I haven't done any work but it looks like there are plenty of requests and some 
start was made years ago:

https://chirp.danplanet.com/issues/1469

--Dan
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] New chirp-next build

[David Boucha]

That's really helpful!  Thanks, Dan.

On Thu, Jan 12, 2023 at 5:43 PM Dan Smith via chirp_users <
chirp_users@intrepid.danplanet.com> wrote:

> > Since you've brought up Yaesu & System Fusion...   I have an FTM-400
> that I love. (Though I haven't set it up since I moved about 6 months ago).
> > Has any work been done on supporting the FTM-400 in chirp? Is it
> technically possible?
>
> I haven't done any work but it looks like there are plenty of requests and
> some start was made years ago:
>
> https://chirp.danplanet.com/issues/1469
>
> --Dan
> ___
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to UtahDave at bou...@gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscr...@intrepid.danplanet.com
> To report this email as off-topic, please email
> chirp_users-ow...@intrepid.danplanet.com
> Searchable archive:
> https://www.mail-archive.com/chirp_users@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 arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

[chirp_users] help running chirp-next on RPI

[Robert Cartier via chirp_users]

I have no luck trying to find the base program ..on the latest builds tarball 
for chirp-next

I have had no issue running chirp and running chirpw

Must be missing something very basic but I dont see any docs to guide me


THanks in advance

Robert Cartier
kd...@icloud.com 

___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

[chirp_users] Importing a CSV file into the memory of an Alinco DJ-G7T

[Stuart Longland VK4MSL via chirp_users]

Hi all,

Has anyone had any luck loading a CSV file into an Alinco DJ-G7T.  I
have organised a list of FM repeaters for 2m/70cm/23cm from the WIA
repeater data spreadsheet.

I won't publish it here, but suffice to say, it's more than I want to
try and punch in via the keypad.  556 records.

First problem is getting Chirp to even talk to the DJ-G7T.  I have no
idea what firmware it runs.  I went looking in its menus but could not
find where this information is shown.  All I can say is I bought this
from a online retailer (Andrews Communications) in Sydney around 2020.

I am running the latest commit of Chirp: commit
49698a5b21a5a696be7f2121bc3ec8f4605b5b0c on Gentoo Linux AMD64 with
Python 3.10.6, wxpython 4.0.7-r2 and wxgtk 3.0.5.1.  Gentoo no longer
ship Python 2.7.  No I do not have a Windows-based PC as I don't use
legacy operating systems for production work.

To even get Chirp to talk to the Alinco, I needed to patch it (I think
this will preclude me using a pre-made "binary"):

diff --git a/chirp/drivers/alinco.py b/chirp/drivers/alinco.py
index 7bfffa39..b3350653 100644
--- a/chirp/drivers/alinco.py
+++ b/chirp/drivers/alinco.py
@@ -595,7 +595,7 @@ class AlincoDJG7EG(AlincoStyleRadio):
 TMODES = ["", "??1", "Tone", "TSQL", "TSQL-R", "DTCS"]
 
 # This is a bit of a hack to avoid overwriting _identify()
-_model = b"AL~DJ-G7EG"
+_model = b"AL~DJ-G7T"
 _memsize = 0x1a7c0
 _range = [(50, 13)]

I was then able to download an image file from the radio.

If I load up my CSV file, the upload option is greyed out.  So clearly
I don't directly open the CSV file, I have to "import" it somehow.

If I try to copy the repeaters into the image from the radio, even just
one repeater, Chirp segfaults.  So clearly it's not a matter of copy
and paste.

How does one import a CSV file into an existing radio image?
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] Importing a CSV file into the memory of an AlincoDJ-G7T

[K0LNY_Glenn]

Hi Stuart,
Under "file" is "import", I think alt I is the keyboard shortcut.
Browse to your CSV file and let it import.
HTH.
Glenn

- Original Message - 
From: "Stuart Longland VK4MSL via chirp_users" 

To: 
Sent: Thursday, January 12, 2023 9:25 PM
Subject: [chirp_users] Importing a CSV file into the memory of an 
AlincoDJ-G7T


Hi all,

Has anyone had any luck loading a CSV file into an Alinco DJ-G7T.  I
have organised a list of FM repeaters for 2m/70cm/23cm from the WIA
repeater data spreadsheet.

I won't publish it here, but suffice to say, it's more than I want to
try and punch in via the keypad.  556 records.

First problem is getting Chirp to even talk to the DJ-G7T.  I have no
idea what firmware it runs.  I went looking in its menus but could not
find where this information is shown.  All I can say is I bought this
from a online retailer (Andrews Communications) in Sydney around 2020.

I am running the latest commit of Chirp: commit
49698a5b21a5a696be7f2121bc3ec8f4605b5b0c on Gentoo Linux AMD64 with
Python 3.10.6, wxpython 4.0.7-r2 and wxgtk 3.0.5.1.  Gentoo no longer
ship Python 2.7.  No I do not have a Windows-based PC as I don't use
legacy operating systems for production work.

To even get Chirp to talk to the Alinco, I needed to patch it (I think
this will preclude me using a pre-made "binary"):

diff --git a/chirp/drivers/alinco.py b/chirp/drivers/alinco.py
index 7bfffa39..b3350653 100644
--- a/chirp/drivers/alinco.py
+++ b/chirp/drivers/alinco.py
@@ -595,7 +595,7 @@ class AlincoDJG7EG(AlincoStyleRadio):
 TMODES = ["", "??1", "Tone", "TSQL", "TSQL-R", "DTCS"]

 # This is a bit of a hack to avoid overwriting _identify()
-_model = b"AL~DJ-G7EG"
+_model = b"AL~DJ-G7T"
 _memsize = 0x1a7c0
 _range = [(50, 13)]

I was then able to download an image file from the radio.

If I load up my CSV file, the upload option is greyed out.  So clearly
I don't directly open the CSV file, I have to "import" it somehow.

If I try to copy the repeaters into the image from the radio, even just
one repeater, Chirp segfaults.  So clearly it's not a matter of copy
and paste.

How does one import a CSV file into an existing radio image?
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to K0LNY at glenn@ervin.email
To unsubscribe, send an email to 
chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@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 arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] Importing a CSV file into the memory of an Alinco DJ-G7T

[Dan Smith via chirp_users]

> To even get Chirp to talk to the Alinco, I needed to patch it (I think
> this will preclude me using a pre-made "binary"):
> 
> diff --git a/chirp/drivers/alinco.py b/chirp/drivers/alinco.py
> index 7bfffa39..b3350653 100644
> --- a/chirp/drivers/alinco.py
> +++ b/chirp/drivers/alinco.py
> @@ -595,7 +595,7 @@ class AlincoDJG7EG(AlincoStyleRadio):
> TMODES = ["", "??1", "Tone", "TSQL", "TSQL-R", "DTCS"]
> 
> # This is a bit of a hack to avoid overwriting _identify()
> -_model = b"AL~DJ-G7EG"
> +_model = b"AL~DJ-G7T"
> _memsize = 0x1a7c0
> _range = [(50, 13)]

This clearly means that your DJ-G7 is some other flavor than the one for which 
a driver has been written. I'm guessing the one in the tree is the european 
version and yours is...something else?

Feel free to open a new feature request for that model to help get it included 
in chirp as a first class citizen.

> If I load up my CSV file, the upload option is greyed out.  So clearly
> I don't directly open the CSV file, I have to "import" it somehow.

You can't upload a CSV to the radio, for sure, as mentioned in the Beginner's 
Guide:

https://chirp.danplanet.com/projects/chirp/wiki/Beginners_Guide

That also covers how to get memories into your radio's image via copy and paste.

> If I try to copy the repeaters into the image from the radio, even just
> one repeater, Chirp segfaults.  So clearly it's not a matter of copy
> and paste.

Yes, copy and paste is how you do it. A segfault in a python application means 
something is very wrong, but almost surely with the stack of non-python stuff 
underneath it (wx, GTK, etc, etc). I've not seen a segault using CHIRP in I 
can't even remember how long. Last one was absolutely with the GTK/cocoa stuff 
from the python2 years, as that has always been a bit tipsy. Since copy and 
paste interacts with your system clipboard, if that's where the segfault 
happens I'd guess there's some mismatched libraries involved.

Feel free to open a bug and provide more information to help track down the 
segfault if you'd like.

--Dan
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] Importing a CSV file into the memory of an AlincoDJ-G7T

[Stuart Longland VK4MSL via chirp_users]

On Thu, 12 Jan 2023 21:30:40 -0600
"K0LNY_Glenn"  wrote:

> Under "file" is "import", I think alt I is the keyboard shortcut.
> Browse to your CSV file and let it import.

How far below "file" is "import"?  I don't see it.  I see "open" --
this lets me open a CSV file, but won't let me load it into a radio.
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] Importing a CSV file into the memory of an AlincoDJ-G7T

[Dan Smith via chirp_users]

> How far below "file" is "import"?  I don't see it.  I see "open" --
> this lets me open a CSV file, but won't let me load it into a radio.

There is no File->Import in chirp-next. Glenn is thinking about chirp-legacy.

--Dan
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] Importing a CSV file into the memory of an Alinco DJ-G7T

[Dan Smith via chirp_users]

> I believe others already have, at least two or three times looking at
> the bug tracker, many of which have patches.  I didn't want to clutter
> it with duplicates.
> 
> https://chirp.danplanet.com/projects/chirp/search?utf8=%E2%9C%93&scope=&issues=1&q=DJ-G7T

Fair enough. I've never taken patches through the bug tracker as a general 
rule, although people attach them there sometimes. That's why those issues 
aren't open and have comments about following the process. I also need a test 
image of the radio in order to add it to the tree, not just a patch. If you can 
muster the github steps to get that submitted that would be great. However, if 
you can either test one of the existing patches and attach your test image, or 
open a new one with your image and patch, I can work the process for you.

> As far as I know this is the US version of the DJ-G7.  Here in
> Australia we have a 4MHz-wide 2m band (144-148MHz) and nearly all the
> FM repeaters are in the upper 2MHz.
> 
> The other difference is the European DJ-G7 uses 9kHz spacing for MW
> broadcast reception -- whereas the US DJ-G7 uses 10kHz (annoying,
> because Australia has had a 9kHz spacing on MW since 1978).
> 
> Other than that, I suspect the two sets are practically identical.

Neither of those are likely to impact CHIRP, so yep, should be okay.

> I'll have to do some investigation then.  The files I'm working with
> are here (patch, image dump from radio and my repeater listing):
> 
> http://static.vk4msl.id.au/chirp/2023/01/13-djg7t/

I can probably turn that into a patch, but I need someone to test it before 
I'll put it in. If you'll open an issue for this, we can collaborate on getting 
something tested and into the tree.

> I guess a feature to allow one to import memory channels from a CSV
> (overwriting existing ones) would be handy as copying and pasting
> channels gets cumbersome.

Feedback from the legacy version was that copy and paste was far more flexible 
and user-friendly, and even being a CLI and developer type myself, that's how I 
do it. I rarely want to import everything from my master list into every radio, 
given a non-overlapping set of supported features, bands and modes.

The legacy version had a very complex import mechanism, which I never used, and 
if you watch some of the youtube videos people have made, it far complicates 
for them what would be much easier with copy and paste. The mere existence 
seemed to make people think they had to do import instead of copy/paste. Having 
a just-overwrite-everything import is an option and I could add that, and may 
in the future, but for the moment copy and paste is the workflow.

Sometimes simpler is better, especially in a GUI app.

> Another prospect might be a CLI interface, so I could just prepare the
> file, then tell `chirp` to download from the radio (or load from an
> existing image), replace the channels, then upload it back to the
> radio.

There is a CLI in the git tree and some people do use it. If you find it 
useful, feel free to file a feature request to have it included in the source 
distribution.

--Dan
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email 
chirp_users-ow...@intrepid.danplanet.com
Searchable archive: 
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Re: [chirp_users] Importing a CSV file into the memory of an Alinco DJ-G7T

[Stuart Longland VK4MSL via chirp_users]

On Thu, 12 Jan 2023 19:38:20 -0800
Dan Smith via chirp_users  wrote:

> > If I try to copy the repeaters into the image from the radio, even just
> > one repeater, Chirp segfaults.  So clearly it's not a matter of copy
> > and paste.  
> 
> Yes, copy and paste is how you do it. A segfault in a python
> application means something is very wrong, but almost surely with the
> stack of non-python stuff underneath it (wx, GTK, etc, etc).

Okay, so trying again under `gdb`, I got this stack trace.

Thread 1 "python3" received signal SIGSEGV, Segmentation fault.
0x77dee14c in ?? () from /usr/lib64/libpython3.10.so.1.0
(gdb) bt
#0  0x77dee14c in  () at /usr/lib64/libpython3.10.so.1.0
#1  0x77dee8c3 in _PyObject_GC_New () at /usr/lib64/libpython3.10.so.1.0
#2  0x77d0379f in PyMemoryView_FromBuffer () at 
/usr/lib64/libpython3.10.so.1.0
#3  0x7659c49d in i_wxPyMakeBuffer(void*, long, bool) ()
at 
/usr/lib/python3.10/site-packages/wx/_core.cpython-310-x86_64-linux-gnu.so
#4  0x76661a38 in  () at 
/usr/lib/python3.10/site-packages/wx/_core.cpython-310-x86_64-linux-gnu.so
#5  0x77d04454 in  () at /usr/lib64/libpython3.10.so.1.0
#6  0x77cc7015 in _PyObject_MakeTpCall () at 
/usr/lib64/libpython3.10.so.1.0
#7  0x77c7bc86 in _PyEval_EvalFrameDefault () at 
/usr/lib64/libpython3.10.so.1.0
#8  0x77d8de54 in  () at /usr/lib64/libpython3.10.so.1.0
#9  0x77c780ee in _PyEval_EvalFrameDefault () at 
/usr/lib64/libpython3.10.so.1.0
#10 0x77d8de54 in  () at /usr/lib64/libpython3.10.so.1.0
#11 0x77c7b1bb in _PyEval_EvalFrameDefault () at 
/usr/lib64/libpython3.10.so.1.0
#12 0x77d8de54 in  () at /usr/lib64/libpython3.10.so.1.0
#13 0x77c7b1bb in _PyEval_EvalFrameDefault () at 
/usr/lib64/libpython3.10.so.1.0
#14 0x77d8de54 in  () at /usr/lib64/libpython3.10.so.1.0
#15 0x77c7b1bb in _PyEval_EvalFrameDefault () at 
/usr/lib64/libpython3.10.so.1.0
#16 0x77d8de54 in  () at /usr/lib64/libpython3.10.so.1.0
#17 0x77cc9aa2 in  () at /usr/lib64/libpython3.10.so.1.0
#18 0x766b05f1 in wxPyCallback::EventThunker(wxEvent&) ()
at 
/usr/lib/python3.10/site-packages/wx/_core.cpython-310-x86_64-linux-gnu.so
#19 0x75af2af6 in 
wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&) ()
at /usr/lib64/libwx_baseu-3.0-gtk3.so.0
#20 0x75af2e6a in wxEvtHandler::SearchDynamicEventTable(wxEvent&) () at 
/usr/lib64/libwx_baseu-3.0-gtk3.so.0
#21 0x75af2f00 in wxEvtHandler::TryHereOnly(wxEvent&) () at 
/usr/lib64/libwx_baseu-3.0-gtk3.so.0
#22 0x75af2fbb in wxEvtHandler::ProcessEventLocally(wxEvent&) () at 
/usr/lib64/libwx_baseu-3.0-gtk3.so.0
#23 0x75af3091 in wxEvtHandler::ProcessEvent(wxEvent&) () at 
/usr/lib64/libwx_baseu-3.0-gtk3.so.0
#24 0x76705633 in sipwxFrame::ProcessEvent(wxEvent&) ()
at 
/usr/lib/python3.10/site-packages/wx/_core.cpython-310-x86_64-linux-gnu.so
#25 0x760525da in wxWindowBase::TryAfter(wxEvent&) () at 
/usr/lib64/libwx_gtk3u_core-3.0-gtk3.so.0
#26 0x767f5583 in sipwxMenuBar::TryAfter(wxEvent&) ()
--Type  for more, q to quit, c to continue without paging--
at 
/usr/lib/python3.10/site-packages/wx/_core.cpython-310-x86_64-linux-gnu.so
#27 0x767f5443 in sipwxMenuBar::ProcessEvent(wxEvent&) ()
at 
/usr/lib/python3.10/site-packages/wx/_core.cpython-310-x86_64-linux-gnu.so
#28 0x75af2df7 in wxEvtHandler::SafelyProcessEvent(wxEvent&) () at 
/usr/lib64/libwx_baseu-3.0-gtk3.so.0
#29 0x7600594a in wxMenuBase::SendEvent(int, int) () at 
/usr/lib64/libwx_gtk3u_core-3.0-gtk3.so.0
#30 0x75efe103 in  () at /usr/lib64/libwx_gtk3u_core-3.0-gtk3.so.0
#31 0x74b785cf in g_closure_invoke () at /usr/lib64/libgobject-2.0.so.0
#32 0x74b8a5f6 in  () at /usr/lib64/libgobject-2.0.so.0
#33 0x74b90f0c in g_signal_emit_valist () at 
/usr/lib64/libgobject-2.0.so.0
#34 0x74b9105f in g_signal_emit () at /usr/lib64/libgobject-2.0.so.0
#35 0x752374e0 in  () at /usr/lib64/libgtk-3.so.0
#36 0x74b785cf in g_closure_invoke () at /usr/lib64/libgobject-2.0.so.0
#37 0x74b8a5f6 in  () at /usr/lib64/libgobject-2.0.so.0
#38 0x74b907eb in g_signal_emit_valist () at 
/usr/lib64/libgobject-2.0.so.0
#39 0x74b9105f in g_signal_emit () at /usr/lib64/libgobject-2.0.so.0
#40 0x74fa9bd8 in gtk_accel_group_activate () at 
/usr/lib64/libgtk-3.so.0
#41 0x74fab4ed in gtk_accel_groups_activate () at 
/usr/lib64/libgtk-3.so.0
#42 0x7525abce in gtk_window_activate_key () at /usr/lib64/libgtk-3.so.0
#43 0x75e8f3db in  () at /usr/lib64/libwx_gtk3u_core-3.0-gtk3.so.0
#44 0x7528b5e7 in  () at /usr/lib64/libgtk-3.so.0
#45 0x74b785cf in g_closure_invoke () at /usr/lib64/libgobject-2.0.so.0
#46 0x74b8a5f6 in  () at /usr/lib64/libgobject-2.0.so.0
#47 0x74b90