[chirp_devel] [PATCH] Initial Yaesu FT3DR commit #7059 #7143
# HG changeset patch # User Ray Cielencki rayslinky@gmail.com # Date 1572667651 14400 # Sat Nov 02 00:07:31 2019 -0400 # Node ID 24a6266d93018cca758c63a32f58cb26427d59c0 # Parent 60b0754e45de1557ca2597c41a2966129653eeef Initial Yaesu FT3DR commit #7059 #7143
diff -r 60b0754e45de -r 24a6266d9301 chirp/drivers/ft3d.py --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/chirp/drivers/ft3d.py Sat Nov 02 00:07:31 2019 -0400 @@ -0,0 +1,11 @@ +from chirp.drivers import ft2d +from chirp import directory + +@directory.register +class FT3D(ft2d.FT2D): + """Yaesu FT-3D""" + BAUD_RATE = 38400 + MODEL = "FT3D" + VARIANT = "R" + + _model = "AH72M" diff -r 60b0754e45de -r 24a6266d9301 tests/images/Yaesu_FT3D_R.img Binary file tests/images/Yaesu_FT3D_R.img has changed
Hi Ray,
# HG changeset patch # User Ray Cielencki rayslinky@gmail.com # Date 1572667651 14400 # Sat Nov 02 00:07:31 2019 -0400 # Node ID 24a6266d93018cca758c63a32f58cb26427d59c0 # Parent 60b0754e45de1557ca2597c41a2966129653eeef Initial Yaesu FT3DR commit #7059 #7143
Is more coming or is this sufficient to make the FT3DR work with chirp?
diff -r 60b0754e45de -r 24a6266d9301 chirp/drivers/ft3d.py --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/chirp/drivers/ft3d.py Sat Nov 02 00:07:31 2019 -0400 @@ -0,0 +1,11 @@ +from chirp.drivers import ft2d +from chirp import directory
+@directory.register +class FT3D(ft2d.FT2D):
- """Yaesu FT-3D"""
- BAUD_RATE = 38400
- MODEL = "FT3D"
- VARIANT = "R"
- _model = "AH72M"
If this is all that is needed, could we just stuff this definition into one of the other files? For simple subclasses that is what we normally do. Not all the files need to contain a single definition and be named accordingly.
diff -r 60b0754e45de -r 24a6266d9301 tests/images/Yaesu_FT3D_R.img Binary file tests/images/Yaesu_FT3D_R.img has changed
Can you attach the image to the bug? I'll pull it down and add it in when I apply.
Thanks!
--Dan
On Tue, Nov 5, 2019 at 10:18 AM Dan Smith via chirp_devel < chirp_devel@intrepid.danplanet.com> wrote:
Hi Ray,
# HG changeset patch # User Ray Cielencki rayslinky@gmail.com # Date 1572667651 14400 # Sat Nov 02 00:07:31 2019 -0400 # Node ID 24a6266d93018cca758c63a32f58cb26427d59c0 # Parent 60b0754e45de1557ca2597c41a2966129653eeef Initial Yaesu FT3DR commit #7059 #7143
Is more coming or is this sufficient to make the FT3DR work with chirp?
There might be a few additions, but I think they'll be made in the ft1d memory map.
diff -r 60b0754e45de -r 24a6266d9301 chirp/drivers/ft3d.py --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/chirp/drivers/ft3d.py Sat Nov 02 00:07:31 2019 -0400 @@ -0,0 +1,11 @@ +from chirp.drivers import ft2d +from chirp import directory
+@directory.register +class FT3D(ft2d.FT2D):
- """Yaesu FT-3D"""
- BAUD_RATE = 38400
- MODEL = "FT3D"
- VARIANT = "R"
- _model = "AH72M"
If this is all that is needed, could we just stuff this definition into one of the other files? For simple subclasses that is what we normally do. Not all the files need to contain a single definition and be named accordingly.
Sorry, I missed that. I'll resubmit it in the ft2d driver.
diff -r 60b0754e45de -r 24a6266d9301 tests/images/Yaesu_FT3D_R.img Binary file tests/images/Yaesu_FT3D_R.img has changed
Can you attach the image to the bug? I'll pull it down and add it in when I apply.
Done, on #7059.
Thanks!
--Dan
Thank you! Ray
participants (3)
-
Dan Smith -
ray c -
Ray Cielencki