[chirp_devel] New Model #6259 Yaesu FT-7100
Hello
Please find the driver for FT-7100 in the attachment. It works fine with the radio and the FT-7100 Programmer from "FT Systems".
There are a few issues to integrate the functionality to Chirp.
a) The total number of memories is constant. However it is possible to define the number of VHF and UHV channels. --> What mechanism do I have to use? - User interface to ask the number of channels. How? - Refresh the user interface after work. How?
b) There is one more tone_mode available named "CTCSS Bell". How do I add it?
c) There are a few more RadioSetting like show_name, is_masked and is_packet96. How do I add them?
b) Testing is missing
Best regards,
Bruno
Please find the driver for FT-7100 in the attachment. It works fine with the radio and the FT-7100 Programmer from "FT Systems".
There are a few issues to integrate the functionality to Chirp.
a) The total number of memories is constant. However it is possible to define the number of VHF and UHV channels. --> What mechanism do I have to use?
- User interface to ask the number of channels. How?
You can add a radio setting for this. Check out some of the other drivers that implement "get_settings()" like the uv5r.
- Refresh the user interface after work. How?
This will be hard. I think you probably just want to warn the user, potentially with one of the warning messages (like the experimental one) that they have to reload the file after they change that setting. You might also make the driver immediately check the value when it loads the file, and then refuse to set/get any more memories if it changes. Then you can raise a RadioError() with the message explaining that they need to save and reload.
b) There is one more tone_mode available named "CTCSS Bell". How do I add it?
Sorry for not answering this the first time you asked...
I know some radios consider this a tone mode, but it's really not. It's a bell flag that is only active in concert with a coded squelch mechanism. I would recommend you put this flag in mem.extra and let people toggle it there if they want, separate from the actual tone mode.
c) There are a few more RadioSetting like show_name, is_masked and is_packet96. How do I add them?
These sound like settings from other drivers, which probably don't apply to you, so no need to implement them.
b) Testing is missing
Does this mean the existing tests don't pass? If you could attach an image file to the relevant bug, I will pull it into the tree when I apply your patch so the tests will run.
Thanks!
--Dan
Am Montag, 26. November 2018, 14.01:31 schrieb Dan Smith via chirp_devel:
Please find the driver for FT-7100 in the attachment. It works fine with the radio and the FT-7100 Programmer from "FT Systems".
There are a few issues to integrate the functionality to Chirp.
a) The total number of memories is constant. However it is possible to define the number of VHF and UHV channels. --> What mechanism do I have to use? - User interface to ask the number of channels. How?
You can add a radio setting for this. Check out some of the other drivers that implement "get_settings()" like the uv5r.
- Refresh the user interface after work. How?
This will be hard. I think you probably just want to warn the user, potentially with one of the warning messages (like the experimental one) that they have to reload the file after they change that setting. You might also make the driver immediately check the value when it loads the file, and then refuse to set/get any more memories if it changes. Then you can raise a RadioError() with the message explaining that they need to save and reload.
I will try it out.
b) There is one more tone_mode available named "CTCSS Bell". How do I add it?
Sorry for not answering this the first time you asked...
No problem. I can imagine that a question is sooner answered when there is real code behind it.
I know some radios consider this a tone mode, but it's really not. It's a bell flag that is only active in concert with a coded squelch mechanism. I would recommend you put this flag in mem.extra and let people toggle it
Thanks, good idea.
How do I use mem.extra? I haven't found an example.
there if they want, separate from the actual tone mode.
c) There are a few more RadioSetting like show_name, is_masked and is_packet96. How do I add them?
These sound like settings from other drivers, which probably don't apply to you, so no need to implement them.
b) Testing is missing
Does this mean the existing tests don't pass? If you could attach an image file to the relevant bug, I will pull it into the tree when I apply your patch so the tests will run.
Sorry. I mean that I haven't run any test. Not even had a look at the tests.
Thanks!
--Dan
Thanks, Bruno
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
How do I use mem.extra? I haven't found an example.
Here is one:
https://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/uv...
there if they want, separate from the actual tone mode.
c) There are a few more RadioSetting like show_name, is_masked and is_packet96. How do I add them?
These sound like settings from other drivers, which probably don't apply to you, so no need to implement them.
b) Testing is missing
Does this mean the existing tests don't pass? If you could attach an image file to the relevant bug, I will pull it into the tree when I apply your patch so the tests will run.
Sorry. I mean that I haven't run any test. Not even had a look at the tests.
Okay, I'll want to make sure it passes the usual tests before we apply it.
Thanks Bruno!
--Dan
Am Dienstag, 27. November 2018, 12.35:54 schrieb Dan Smith via chirp_devel:
How do I use mem.extra? I haven't found an example.
Here is one:
https://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/uv 5r.py#L931
Thanks, but I don't get it.
- I open tests/images/Baofeng_UV-5R.img - The code at chirp/drivers/uv5r.py#L931 gets executed, no exception is thrown. (Verified with winpdb) -> Behind the column "Skip" I expect more columns named "BCL", "PTT ID" and "PTT ID Code" to show up. But there is no extra column appearing.
Where do I go wrong?
Best regards, Bruno
Thanks, but I don't get it.
- I open tests/images/Baofeng_UV-5R.img
- The code at chirp/drivers/uv5r.py#L931 gets executed, no exception is
thrown. (Verified with winpdb) -> Behind the column "Skip" I expect more columns named "BCL", "PTT ID" and "PTT ID Code" to show up. But there is no extra column appearing.
Where do I go wrong?
Right-click on the memory, choose properties.
--Dan
Am Freitag, 30. November 2018, 09.09:36 schrieb Dan Smith via chirp_devel:
Thanks, but I don't get it.
- I open tests/images/Baofeng_UV-5R.img
- The code at chirp/drivers/uv5r.py#L931 gets executed, no exception is
thrown. (Verified with winpdb) -> Behind the column "Skip" I expect more columns named "BCL", "PTT ID" and "PTT ID Code" to show up. But there is no extra column appearing.
Where do I go wrong?
Right-click on the memory, choose properties.
--Dan
Thanks. I didn't notice the second tab named "Other".
Bruno
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
participants (2)
-
Bruno -
Dan Smith