[chirp_devel] Hello

[Richard Farina]

On 01/12/2012 06:44 PM, Andrew Errington wrote:
> On Fri, January 13, 2012 04:32, Richard Farina wrote:
>> On 01/11/2012 10:16 AM, Dan Smith wrote:
>>
>>>> What do I have to do to add support for the VX-2R?  I suspect I could
>>>> edit the VX-3 code, or could somebody tell me if it Just Works anyway?
>>>> I have read
>>>> the list archives (and most of the main chirp_users list) but no
>>>> mention is made of this radio.  Google doesn't tell me much either.
>>> As Rick said, start with the VX7 driver. The clone bits should mostly
>>> be correct, with the exception of the length of the last block. From
>>> there, you'll need to change the memory format to match that of the
>>> VX-2, which
>>> will almost definitely use different offsets for the start of the memory
>>>   channels, and likely have a few other differences in the format
>>> itself.
>>>
>>> The first thing to do is make a vx2 driver out of the vx-7 so that it
>>> shows up on its own in the UI. Then make sure you can clone out of the
>>> radio to it and determine the proper length of the final block. Then
>>> you should be able to save the image, even though the parsing code will
>>> choke on the actual contents.
>> When I started doing all this I used VX2 commander to dump the radio
>> (gives you the length of the image) and then I can easily check memory
>> one and find the stored frequency in the image dump (giving you the start
>> of the memory section of the image).  All in all, it's not that hard.
> So far all I have done is strip the RS232 level shifter and support
> components off the USB-serial adapter, leaving the FTDI chip behind.  I
> need to cut the trace to the VCCIO pad and link it to 3V3OUT, then link
> TxD and RxD together and off to a 4-way plug for the VX2r.  It's easy to
> do, but it takes time.
>
> I have also made a copy of the VX7 module and called it VX2, and it shows
> up in the UI, but I can't do any more until I have a serial interface to
> talk to.
>
> I also installed VX2 commander under WINE, but I don't know if I'll use
> it.  It runs, but of course I still need a serial device.
last time I tried to run vx commander in wine it barfed horribly, 
although I don't know much about wine.  I use vx commander in a windows 
virtual machine very well.

-Rick WZ3RO

>
> Thanks everyone for your interest.  I am writing this all down so that
> someone can speak up if I am about to do something stupid.
>
> 73,
>
> Andrew
>
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
>