<div dir="ltr">Uploading patch again (being filtered out of email). I have included an image file also - need to remove .txt<div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 4 May 2022 at 13:26, Jim Unroe <<a href="mailto:rock.unroe@gmail.com">rock.unroe@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Mark,<br>
<br>
On Wed, May 4, 2022 at 8:13 AM Mark Leyden <<a href="mailto:mark.leyden@gmail.com" target="_blank">mark.leyden@gmail.com</a>> wrote:<br>
><br>
> 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...)<br>
> 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.<br>
> 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?<br>
><br>
> Thanks again,<br>
> Mark<br>
<br>
I would have looked further into the "1026.6 error" to offer advice<br>
but I couldn't locate a copy of the driver that you are working on. I<br>
didn't notice if it was attached to your original request for help and<br>
I couldn't find the "ticket" that you will be submitting the patch<br>
against to see if I could find a copy of the driver posted there.<br>
Sorry.<br>
<br>
Jim<br>
</blockquote></div>