[chirp_devel] New driver for Abbree AR-F8
Chirp img file for testing. (Still work to be done, but I am looking for guidance) Currently fails tests with:
Abbree AR-F8 CopyAll CRASHED: `1026.6' is not in valid list: [67.0, 69.3, 71.9, 74.4, 77.0, 79.7, 82.5, 85.4, 88.5, 91.5, 94.8, 97.4, 100.0, 103.5, 107.2, 110.9, 114.8, 118.8, 123.0, 127.3, 131.8, 136.5, 141.3, 146.2, 151.4, 156.7, 159.8, 162.2, 165.5, 167.9, 171.3, 173.8, 177.3, 179.9, 183.5, 186.2, 189.9, 192.8, 196.6, 199.5, 203.5, 206.5, 210.7, 218.1, 225.7, 229.1, 233.6, 241.8, 250.3, 254.1, 56.0, 57.0, 58.0, 59.0, 60.0, 61.0, 62.0, 62.5, 63.0, 64.0] Abbree AR-F8 BruteForce CRASHED: `1025.9' is not in valid list: [67.0, 69.3, 71.9, 74.4, 77.0, 79.7, 82.5, 85.4, 88.5, 91.5, 94.8, 97.4, 100.0, 103.5, 107.2, 110.9, 114.8, 118.8, 123.0, 127.3, 131.8, 136.5, 141.3, 146.2, 151.4, 156.7, 159.8, 162.2, 165.5, 167.9, 171.3, 173.8, 177.3, 179.9, 183.5, 186.2, 189.9, 192.8, 196.6, 199.5, 203.5, 206.5, 210.7, 218.1, 225.7, 229.1, 233.6, 241.8, 250.3, 254.1, 56.0, 57.0, 58.0, 59.0, 60.0, 61.0, 62.0, 62.5, 63.0, 64.0] Abbree AR-F8 Edges PASSED: All tests Abbree AR-F8 Settings PASSED: All tests Abbree AR-F8 Banks SKIPPED: Banks not supported Abbree AR-F8 Detect PASSED: All tests Abbree AR-F8 Clone FAILED: Radio tried to write the wrong type of data to the SerialNone pipe.
On Sun, 1 May 2022 at 19:44, Mark Leyden mark.leyden@gmail.com wrote:
Thoughts welcome!
Hi Mark,
On Tue, May 3, 2022 at 7:42 PM Mark Leyden via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
Chirp img file for testing. (Still work to be done, but I am looking for guidance) Currently fails tests with:
Abbree AR-F8 CopyAll CRASHED: `1026.6' is not in valid list: [67.0, 69.3, 71.9, 74.4, 77.0, 79.7, 82.5, 85.4, 88.5, 91.5, 94.8, 97.4, 100.0, 103.5, 107.2, 110.9, 114.8, 118.8, 123.0, 127.3, 131.8, 136.5, 141.3, 146.2, 151.4, 156.7, 159.8, 162.2, 165.5, 167.9, 171.3, 173.8, 177.3, 179.9, 183.5, 186.2, 189.9, 192.8, 196.6, 199.5, 203.5, 206.5, 210.7, 218.1, 225.7, 229.1, 233.6, 241.8, 250.3, 254.1, 56.0, 57.0, 58.0, 59.0, 60.0, 61.0, 62.0, 62.5, 63.0, 64.0] Abbree AR-F8 BruteForce CRASHED: `1025.9' is not in valid list: [67.0, 69.3, 71.9, 74.4, 77.0, 79.7, 82.5, 85.4, 88.5, 91.5, 94.8, 97.4, 100.0, 103.5, 107.2, 110.9, 114.8, 118.8, 123.0, 127.3, 131.8, 136.5, 141.3, 146.2, 151.4, 156.7, 159.8, 162.2, 165.5, 167.9, 171.3, 173.8, 177.3, 179.9, 183.5, 186.2, 189.9, 192.8, 196.6, 199.5, 203.5, 206.5, 210.7, 218.1, 225.7, 229.1, 233.6, 241.8, 250.3, 254.1, 56.0, 57.0, 58.0, 59.0, 60.0, 61.0, 62.0, 62.5, 63.0, 64.0] Abbree AR-F8 Edges PASSED: All tests Abbree AR-F8 Settings PASSED: All tests Abbree AR-F8 Banks SKIPPED: Banks not supported Abbree AR-F8 Detect PASSED: All tests Abbree AR-F8 Clone FAILED: Radio tried to write the wrong type of data to the SerialNone pipe.
The CHIRP Supported Radio Models list shows the Abbree AR-F8 as already supported.
ABBREE * AR-F8 (use Wouxun KG-UV8D)
So I would suggest that you look at the KG-UV8D driver to see how it handles the CTCSS tones.
Where can your AR-F8 driver be obtained?
Jim KC9HI
Hi Jim, thanks for getting back to me. I have based the AR-F8 driver off the existing KG-UV8D driver, so I will go back and see that I have missed. (I was wondering if I missed something obvious as 1026.6 is not a tone supported by the radio so I'm not suprised it isn't in the list...) As for the driver, it should have been an attachment to the first mail in this thread - if not, please let me know how to post. As an aside, I'm developing using Python 3.9 and was wondering if there are difficulties with that? I still haven't gotten to the bottom of the 'Radio tried to write the wrong type of data to the SerialNone pipe' test as was wondering if it is a Python 2/3 thing?
Thanks again, Mark
On Wed, 4 May 2022 at 02:49, Jim Unroe rock.unroe@gmail.com wrote:
Hi Mark,
On Tue, May 3, 2022 at 7:42 PM Mark Leyden via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
Chirp img file for testing. (Still work to be done, but I am looking for
guidance) Currently fails tests with:
Abbree AR-F8 CopyAll CRASHED: `1026.6' is not in valid list:
[67.0, 69.3, 71.9, 74.4, 77.0, 79.7, 82.5, 85.4, 88.5, 91.5, 94.8, 97.4, 100.0, 103.5, 107.2, 110.9, 114.8, 118.8, 123.0, 127.3, 131.8, 136.5, 141.3, 146.2, 151.4, 156.7, 159.8, 162.2, 165.5, 167.9, 171.3, 173.8, 177.3, 179.9, 183.5, 186.2, 189.9, 192.8, 196.6, 199.5, 203.5, 206.5, 210.7, 218.1, 225.7, 229.1, 233.6, 241.8, 250.3, 254.1, 56.0, 57.0, 58.0, 59.0, 60.0, 61.0, 62.0, 62.5, 63.0, 64.0]
Abbree AR-F8 BruteForce CRASHED: `1025.9' is not in valid
list: [67.0, 69.3, 71.9, 74.4, 77.0, 79.7, 82.5, 85.4, 88.5, 91.5, 94.8, 97.4, 100.0, 103.5, 107.2, 110.9, 114.8, 118.8, 123.0, 127.3, 131.8, 136.5, 141.3, 146.2, 151.4, 156.7, 159.8, 162.2, 165.5, 167.9, 171.3, 173.8, 177.3, 179.9, 183.5, 186.2, 189.9, 192.8, 196.6, 199.5, 203.5, 206.5, 210.7, 218.1, 225.7, 229.1, 233.6, 241.8, 250.3, 254.1, 56.0, 57.0, 58.0, 59.0, 60.0, 61.0, 62.0, 62.5, 63.0, 64.0]
Abbree AR-F8 Edges PASSED: All tests Abbree AR-F8 Settings PASSED: All tests Abbree AR-F8 Banks SKIPPED: Banks not supported Abbree AR-F8 Detect PASSED: All tests Abbree AR-F8 Clone FAILED: Radio tried to write the
wrong type of data to the SerialNone pipe.
The CHIRP Supported Radio Models list shows the Abbree AR-F8 as already supported.
ABBREE
- AR-F8 (use Wouxun KG-UV8D)
So I would suggest that you look at the KG-UV8D driver to see how it handles the CTCSS tones.
Where can your AR-F8 driver be obtained?
Jim KC9HI
Hi Mark,
On Wed, May 4, 2022 at 8:13 AM Mark Leyden mark.leyden@gmail.com wrote:
Hi Jim, thanks for getting back to me. I have based the AR-F8 driver off the existing KG-UV8D driver, so I will go back and see that I have missed. (I was wondering if I missed something obvious as 1026.6 is not a tone supported by the radio so I'm not suprised it isn't in the list...) As for the driver, it should have been an attachment to the first mail in this thread - if not, please let me know how to post. As an aside, I'm developing using Python 3.9 and was wondering if there are difficulties with that? I still haven't gotten to the bottom of the 'Radio tried to write the wrong type of data to the SerialNone pipe' test as was wondering if it is a Python 2/3 thing?
Thanks again, Mark
I would have looked further into the "1026.6 error" to offer advice but I couldn't locate a copy of the driver that you are working on. I didn't notice if it was attached to your original request for help and I couldn't find the "ticket" that you will be submitting the patch against to see if I could find a copy of the driver posted there. Sorry.
Jim
Uploading patch again (being filtered out of email). I have included an image file also - need to remove .txt
On Wed, 4 May 2022 at 13:26, Jim Unroe rock.unroe@gmail.com wrote:
Hi Mark,
On Wed, May 4, 2022 at 8:13 AM Mark Leyden mark.leyden@gmail.com wrote:
Hi Jim, thanks for getting back to me. I have based the AR-F8 driver off
the existing KG-UV8D driver, so I will go back and see that I have missed. (I was wondering if I missed something obvious as 1026.6 is not a tone supported by the radio so I'm not suprised it isn't in the list...)
As for the driver, it should have been an attachment to the first mail
in this thread - if not, please let me know how to post.
As an aside, I'm developing using Python 3.9 and was wondering if there
are difficulties with that? I still haven't gotten to the bottom of the 'Radio tried to write the wrong type of data to the SerialNone pipe' test as was wondering if it is a Python 2/3 thing?
Thanks again, Mark
I would have looked further into the "1026.6 error" to offer advice but I couldn't locate a copy of the driver that you are working on. I didn't notice if it was attached to your original request for help and I couldn't find the "ticket" that you will be submitting the patch against to see if I could find a copy of the driver posted there. Sorry.
Jim
Hi Mark,
I finally got a chance to look at this. It would help if the first few channels had CTCSS tones and DTCS codes programmed in them using the OEM software or manually from the radio and a list stating the channel numbers and which tone/code is programmed in each.
But if I remark out the additional code that was added to the abbree_ar-f8.py _get_tone() helper over and above what is in the kguv8d.py code and then enable channel 41 which has a tone, it displays without error.
Loc: 41 Frequency: 430.937500 Duplex: Tone Tone: 71.9
Jim KC9HI
On Sat, May 7, 2022 at 5:05 PM Mark Leyden mark.leyden@gmail.com wrote:
Uploading patch again (being filtered out of email). I have included an image file also - need to remove .txt
On Wed, 4 May 2022 at 13:26, Jim Unroe rock.unroe@gmail.com wrote:
Hi Mark,
On Wed, May 4, 2022 at 8:13 AM Mark Leyden mark.leyden@gmail.com wrote:
Hi Jim, thanks for getting back to me. I have based the AR-F8 driver off the existing KG-UV8D driver, so I will go back and see that I have missed. (I was wondering if I missed something obvious as 1026.6 is not a tone supported by the radio so I'm not suprised it isn't in the list...) As for the driver, it should have been an attachment to the first mail in this thread - if not, please let me know how to post. As an aside, I'm developing using Python 3.9 and was wondering if there are difficulties with that? I still haven't gotten to the bottom of the 'Radio tried to write the wrong type of data to the SerialNone pipe' test as was wondering if it is a Python 2/3 thing?
Thanks again, Mark
I would have looked further into the "1026.6 error" to offer advice but I couldn't locate a copy of the driver that you are working on. I didn't notice if it was attached to your original request for help and I couldn't find the "ticket" that you will be submitting the patch against to see if I could find a copy of the driver posted there. Sorry.
Jim
participants (2)
-
Jim Unroe -
Mark Leyden