Hi everyone,
I just became interested in Chirp, but I have a Yaesu VX-2R, which does not seem to be supported.
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.
I generally use Linux, and I am comfortable with Python. I have one VX-2R, and I don't want to break it..., but having said that I am building my own interface cable by hacking an FTDI-based USB->serial adaptor. All I have to do is remove the RS232 level shifter chip and connect VCCIO on the FTDI chip to 3V3 instead of 5V. Naturally I am doing all of this in my copious free time, so who knows when it will be finished.
Thanks in advance for anything about the VX-2R,
73,
Andrew ZL3AME
On 01/11/2012 05:38 AM, Andrew Errington wrote:
Hi everyone,
I just became interested in Chirp, but I have a Yaesu VX-2R, which does not seem to be supported.
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 VX-7 is a better starting point as the clone for the vx2 is closer to that. I have been wanting to add support for that radio for months but I have zero freetime (and no vx2) so if you want to work on it please go for it ;-)
-Rick WZ3RO
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.
I generally use Linux, and I am comfortable with Python. I have one VX-2R, and I don't want to break it..., but having said that I am building my own interface cable by hacking an FTDI-based USB->serial adaptor. All I have to do is remove the RS232 level shifter chip and connect VCCIO on the FTDI chip to 3V3 instead of 5V. Naturally I am doing all of this in my copious free time, so who knows when it will be finished.
Thanks in advance for anything about the VX-2R,
73,
Andrew ZL3AME _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
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.
Looking at the image with a hex editor, you should be able to determine where your first memory channel is, by looking for the BCD-encoded frequency. Adjust the offset of the start of the memory channel list and things should start to come into view. Once you have it aligned like that, you can start using the "show raw memory" function in the UI (right click on the channel to get it) and speed up the decoding process quite a bit.
I generally use Linux, and I am comfortable with Python. I have one VX-2R, and I don't want to break it..., but having said that I am building my own interface cable by hacking an FTDI-based USB->serial adaptor. All I have to do is remove the RS232 level shifter chip and connect VCCIO on the FTDI chip to 3V3 instead of 5V. Naturally I am doing all of this in my copious free time, so who knows when it will be finished.
You won't break the radio, although you might have to erase the memory a couple times before you get it right. I've never bricked a radio. It sounds like you've got the right skills to do this, so dive in and ask more questions :)
Thanks!
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.
-Rick WZ3RO
Looking at the image with a hex editor, you should be able to determine where your first memory channel is, by looking for the BCD-encoded frequency. Adjust the offset of the start of the memory channel list and things should start to come into view. Once you have it aligned like that, you can start using the "show raw memory" function in the UI (right click on the channel to get it) and speed up the decoding process quite a bit.
I generally use Linux, and I am comfortable with Python. I have one VX-2R, and I don't want to break it..., but having said that I am building my own interface cable by hacking an FTDI-based USB->serial adaptor. All I have to do is remove the RS232 level shifter chip and connect VCCIO on the FTDI chip to 3V3 instead of 5V. Naturally I am doing all of this in my copious free time, so who knows when it will be finished.
You won't break the radio, although you might have to erase the memory a couple times before you get it right. I've never bricked a radio. It sounds like you've got the right skills to do this, so dive in and ask more questions :)
Thanks!
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.
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
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@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
On 1/12/2012 6:44 PM, Andrew Errington wrote:
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. [...] It's easy to do, but it takes time.
I reallse you've already started on this path, for other there are a number of sources of FTDI usb<->serial cables that operate at either 5V or 3.3V including FTDI themselves.
I previously posted this to chirp_users:
http://intrepid.danplanet.com/pipermail/chirp_users/2011-November/001529.htm...
http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_CABL...
You can get that cable as well as some other good FTDI usb serial breakout boards from some of the electronics DIY places like Adafruit, Sparkfun, Seeedstudio, etc.
https://www.adafruit.com/products/70
Or
https://www.adafruit.com/products/284
Or
http://www.sparkfun.com/products/9873
I realize you are in the UK, I believe there are a number of UK/EU DIY sources.
On Fri, January 13, 2012 09:20, Robert Terzi wrote:
On 1/12/2012 6:44 PM, Andrew Errington wrote:
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. [...] It's easy to do, but it takes time.
I reallse you've already started on this path, for other there are a number of sources of FTDI usb<->serial cables that operate at either 5V or 3.3V including FTDI themselves.
Yes, I know, but I wanted to make it myself. It is a learning exercise as much as anything. I will buy another one and make a 5V version for my FT-817ND (how appropriate that someone else is working on that model...)
Actually, I am in South Korea. There is a cool parts website here called eleparts.com, and they do stock the FTDI modules, but I got the serial adapter at a local computer store. I cut off the plastic moulding and I am hacking on the little circuit board inside.
Best wishes,
Andrew
On 13/01/2012 03:46, Andrew Errington wrote:
Yes, I know, but I wanted to make it myself. It is a learning exercise as much as anything. I will buy another one and make a 5V version for my FT-817ND (how appropriate that someone else is working on that model...)
For the 817 you can also consider the bluetooth one which is described here http://www.yo3ggx.ro/ Nice idea to have the radio and pc completed isoleted, isn't? I ordered a pair of BT module some days ago for about 7$ each but have to wait weeks before they arrive.
73 de IZ3GME Marco
On 1/12/2012 6:44 PM, Andrew Errington wrote:
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.
For radios that have a symmetric clone protocol like some of the other VX models, you can actually have the two pieces of software talk to each other through a null modem, without a radio...
On 01/12/2012 07:26 PM, Robert Terzi wrote:
On 1/12/2012 6:44 PM, Andrew Errington wrote:
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.
For radios that have a symmetric clone protocol like some of the other VX models, you can actually have the two pieces of software talk to each other through a null modem, without a radio...
The one caveat to this method is you must assume the other software behaves like the radio. It is important to note that it is close but not exact. Working with the radio is much better.
-Rick WZ3RO
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
participants (5)
-
Andrew Errington -
Dan Smith -
IZ3GME Marco -
Richard Farina -
Robert Terzi