Hi all,
Can someone try using v0.1.12 to upload and download from their Yaesu VX6? There has been a report that this operation is broken in 0.1.12 and I'd like to get confirmation of that before I try to find one to borrow.
Thanks!
Can someone try using v0.1.12 to upload and download from their Yaesu VX6? There has been a report that this operation is broken in 0.1.12 and I'd like to get confirmation of that before I try to find one to borrow.
Err, sorry there was some confusion. The problem is actually with an FT8900. Can someone test that for us? Just downloading from the radio, changing something and then uploading again should do the trick.
Unfortunately, it's much harder for me to lay hands on an 8900 so I really need to know it's broken first.
Thanks!
*I'll try later today **Alvin Koffman *
IN brightest day, in blackest night,
*No evil shall escape my sight*
*Let those who worship evil's might,*
*Beware my power... *
*My Holy Spirit's light! *
On Thu, Sep 15, 2011 at 9:50 AM, Dan Smith dsmith@danplanet.com wrote:
Can someone try using v0.1.12 to upload and download from their Yaesu VX6? There has been a report that this operation is broken in 0.1.12 and I'd like to get confirmation of that before I try to find one to borrow.
Err, sorry there was some confusion. The problem is actually with an FT8900. Can someone test that for us? Just downloading from the radio, changing something and then uploading again should do the trick.
Unfortunately, it's much harder for me to lay hands on an 8900 so I really need to know it's broken first.
Thanks!
-- Dan Smith www.danplanet.com KK7DS _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
On 9/15/2011 8:50 AM, Dan Smith wrote:
Can someone try using v0.1.12 to upload and download from their Yaesu VX6? There has been a report that this operation is broken in 0.1.12 and I'd like to get confirmation of that before I try to find one to borrow.
Err, sorry there was some confusion. The problem is actually with an FT8900. Can someone test that for us? Just downloading from the radio, changing something and then uploading again should do the trick.
Unfortunately, it's much harder for me to lay hands on an 8900 so I really need to know it's broken first.
Thanks!
Dan I have an Ft-8800 How different is that from the Ft-8900 ? The are both pretty close to the same.
Allan WB5QNG
On 9/15/2011 8:39 AM, Dan Smith wrote:
Hi all,
Can someone try using v0.1.12 to upload and download from their Yaesu VX6? There has been a report that this operation is broken in 0.1.12 and I'd like to get confirmation of that before I try to find one to borrow.
Thanks!
Dan Download from Radio seems to work fine. Uploads are not consistent. Some memory locations did not program at all, some were partially programmed ( i.e name field was messed up). This was verified with other programming software VX-6 commander.
Allan WB5QNG
Yeah, the 8800 and 8900 use the same driver in CHIRP, so I'd expect the upload process to be identical. The problem reported was with the actual uploading, which you seem to be able to do just fine.
Download from Radio seems to work fine. Uploads are not consistent. Some memory locations did not program at all, some were partially programmed ( i.e name field was messed up). This was verified with other programming software VX-6 commander.
Okay, can you file bugs (issues) on the website for these and attach .img files (and maybe screenshots as well)? If so, I'll get these resolved.
Thanks!
Dan I got everything working. Still had to specifically import a few channels but at least that worked this time. Is there any documentation ( wiki or otherwise) on how to use Chirp and about the different format to save in ( csv, vs chrisp vs img) ? How difficult would it be to allow something like an import of a csv to a generic radio then set the type up and do a write to the Radio. Currently I do not seem to be able to setup the type of radio except for a read from the radio. Once I have read from a radio then I can import the CSv and write back to the radio. In most of the cases I work with I am prepared to trash whatever is currently there and overwrite it with new info. Still need the read function for verifying the programming I just wrote.
Allan WB5QNG
On 9/15/2011 10:09 AM, Dan Smith wrote:
Yeah, the 8800 and 8900 use the same driver in CHIRP, so I'd expect the upload process to be identical. The problem reported was with the actual uploading, which you seem to be able to do just fine.
Download from Radio seems to work fine. Uploads are not consistent. Some memory locations did not program at all, some were partially programmed ( i.e name field was messed up). This was verified with other programming software VX-6 commander.
Okay, can you file bugs (issues) on the website for these and attach .img files (and maybe screenshots as well)? If so, I'll get these resolved.
Thanks!
Is there any documentation ( wiki or otherwise) on how to use Chirp and about the different format to save in ( csv, vs chrisp vs img) ?
Just the beginner's guide:
http://chirp.danplanet.com/projects/chirp/wiki/Beginners_Guide
If you and others can come up with some specific things that you'd like to see documented, I'll be glad to try to write those up. Being neck-deep in the internals, it's hard for me to "see" what needs to be documented.
Of course, anyone that wants to take a stab at actually writing something up gets bonus points :)
How difficult would it be to allow something like an import of a csv to a generic radio then set the type up and do a write to the Radio.
Well, you can import a CSV into a CSV right now. I think what you're looking for is the ability to upload a CSV directly into a radio, and have CHIRP do the behind-the-scenes work to create an empty image, right?
I'm a little hesitant to start distributing blank images of radios with CHIRP itself, but I have considered providing some sort of a bootstrap process which would let you capture "base" images of your radios and have them stored internally. Then, chirp could provide something like a direct upload from CSV by silently merging to the base image and uploading that.
Is that what you're looking for?
The only problem here is that you could put something in your CSV that your radio can't support, which means when you go to do the upload, you'd see an error like "The IC-2720 doesn't support 50.525MHz" as opposed to seeing it immediately while editing now. It's definitely something I can look into though.
I also worry that people will constantly be asking why CHIRP is (seemingly) reversing settings such as backlight intensity or beep volume. Since that stuff would be stored in the base image, if you tweaked it just before doing an upload, it would revert.
Do other people think this is a useful workflow?
Currently I do not seem to be able to setup the type of radio except for a read from the radio.
Well, the idea has always been that you download an image of your radio, edit or import, and then upload. You can store a .img file of your 2720 and open it later (without having to do a download first).
Dan You might want to highlight the beginner guide on the wiki page, I must have looked past it over a dozen time before I found it. Not sure what you need help with on Documentation, I do some "JIT" Just in time type guides for our MRC group. I can maybe help with some documentation. I did not realize the other options were so intermixed with the memories. The read before write now make more sense. I see a need for a bulk erase memories option. In my case I want to leave everything but the memories alone, and replace anything there. So reading the Radio, Blow off the current memories, import new list, program radio. would be my primary mode of operation. At least for the first radio, after that the next 25 or 100 are exactly the same. i.e. in MRC we have 27 radios that should be exactly the same. So I would read the first one, setup the memories, then program all the rest the same.
Allan WB5QNG
On 9/19/2011 12:16 PM, Dan Smith wrote:
Is there any documentation ( wiki or otherwise) on how to use Chirp and about the different format to save in ( csv, vs chrisp vs img) ?
Just the beginner's guide:
http://chirp.danplanet.com/projects/chirp/wiki/Beginners_GuideIf you and others can come up with some specific things that you'd like to see documented, I'll be glad to try to write those up. Being neck-deep in the internals, it's hard for me to "see" what needs to be documented.
Of course, anyone that wants to take a stab at actually writing something up gets bonus points :)
How difficult would it be to allow something like an import of a csv to a generic radio then set the type up and do a write to the Radio.
Well, you can import a CSV into a CSV right now. I think what you're looking for is the ability to upload a CSV directly into a radio, and have CHIRP do the behind-the-scenes work to create an empty image, right?
I'm a little hesitant to start distributing blank images of radios with CHIRP itself, but I have considered providing some sort of a bootstrap process which would let you capture "base" images of your radios and have them stored internally. Then, chirp could provide something like a direct upload from CSV by silently merging to the base image and uploading that.
Is that what you're looking for?
The only problem here is that you could put something in your CSV that your radio can't support, which means when you go to do the upload, you'd see an error like "The IC-2720 doesn't support 50.525MHz" as opposed to seeing it immediately while editing now. It's definitely something I can look into though.
I also worry that people will constantly be asking why CHIRP is (seemingly) reversing settings such as backlight intensity or beep volume. Since that stuff would be stored in the base image, if you tweaked it just before doing an upload, it would revert.
Do other people think this is a useful workflow?
Currently I do not seem to be able to setup the type of radio except for a read from the radio.
Well, the idea has always been that you download an image of your radio, edit or import, and then upload. You can store a .img file of your 2720 and open it later (without having to do a download first).
I did not realize the other options were so intermixed with the memories. The read before write now make more sense.
Yep, every setting you can change in the radio is stored in the image with the memories. On Icom, Kenwood (and some other) radios, it would be possible to do a download, merge, upload operation to get closer to what you want. However, Yaesu radios would require a lot of button pushing by the operator to make that work since they are not as sophisticated. That means it'd be hard to implement in a way that would make everyone happy.
I see a need for a bulk erase memories option.
Select all, right click, delete all should do it, right?
So I would read the first one, setup the memories, then program all the rest the same.
And, of course, if they are all the same model, you'd not do the import each time, but rather blow the same image into every radio, which should go pretty fast.
Dan,
FYI, the fields in the Yaesu VX-6R are as follows: Tag,RX Freq,Name,Mode,Skip,Step,Masked,RPT Sh,ShiftFrq,TS/DCS,Tone,DCS,TX Pwr,TX Dev,Clk Sh,BANK 1,BANK 2,BANK 3,BANK 4,BANK 5,BANK 6,BANK 7,BANK 8,BANK 9,BANK10,BANK11,BANK12,BANK13,BANK14,BANK15,BANK16,BANK17,BANK18,BANK19,BANK 20,BANK21,BANK22,BANK23,BANK24
The Fields will look something like this: ABERNA,146.760,ALPHA,NFM,OFF,5 KHz,NO,-RPT,0.6,TONE,179.9,23,HIGH,NORM,OFF,,,,,,,,,,,,,,,,,,,,,,,, ABERNA,444.000,ALPHA,NFM,OFF,5 KHz,NO,+RPT,5,TONE,118.8,23,HIGH,NORM,OFF,,,,,,,,,,,,,,,,,,,,,,,,
This layout is from V6Commander..
-- John Gorena
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users- bounces@intrepid.danplanet.com] On Behalf Of Dan Smith Sent: Monday, September 19, 2011 6:16 PM To: Discussion of CHIRP Subject: Re: [chirp_users] IC-2720
I did not realize the other options were so intermixed with the memories. The read before write now make more sense.
Yep, every setting you can change in the radio is stored in the image with the memories. On Icom, Kenwood (and some other) radios, it would be possible to do a download, merge, upload operation to get closer to what you want. However, Yaesu radios would require a lot of button pushing by the operator to make that work since they are not as sophisticated. That means it'd be hard to implement in a way that would make everyone happy.
I see a need for a bulk erase memories option.
Select all, right click, delete all should do it, right?
So I would read the first one, setup the memories, then program all the rest the same.
And, of course, if they are all the same model, you'd not do the import each time, but rather blow the same image into every radio, which should go pretty fast.
-- Dan Smith www.danplanet.com KK7DS _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Dan,
There was some discussion on what the fields were. I just wanted you to know the fields on the VX-6r. Sorry for the confussion.
-- John Gorena
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users- bounces@intrepid.danplanet.com] On Behalf Of Dan Smith Sent: Tuesday, September 20, 2011 9:56 AM To: chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] IC-2720
FYI, the fields in the Yaesu VX-6R are as follows:
<snip>
This layout is from V6Commander..
Sorry, what? I think I'm missing how this tied to the rest of the
thread...
-- Dan Smith www.danplanet.com KK7DS _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
participants (4)
-
Allan R. Batteiger -
Alvin Koffman -
Dan Smith -
John Gorena