Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios
>> ./chirp.py -r ic2820 -s /dev/ttyS1 --download-mmap Okay, you'll want to add "--mmap foo.img" to give it somewhere to save the image to once it gets there. > chirp.errors.InvalidDataError: Radio has unknown tone 0x8E Okay, I wasn't masking out enough bits for the tone value. You've got something turned on in a memory location that I don't have, and so you've got a bit (0x80) turned on that is throwing it out of range. I've tightened that down. If you want to grab a snapshot of my development tree and try again, it would be appreciated: http://d-rats.danplanet.com/hg/hgwebdir.cgi/chirp.hg/archive/tip.tar.gz It might be worth taking this off-list for a bit if this doesn't fix it for you. Just to avoid boring people with the details :) Thanks! -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS
Re: [dstar_digital] Re: CHIRP: An open-source programming tool for ICOM radios
> Not a problem. If I kow what I am doing. Okay, I'll see about putting in something to do that in the next post and we can go from there. I also realized that I know someone locally that as one each of a V82 and U82, so I might be able to borrow one for a while. -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS
Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios
On Wed, 2008-07-23 at 06:38 -0700, Dan Smith wrote:
> I wasn't aware that you could do clone operations through the front
> data port. You can use the CS-2820 through that port?
Yes.
> The serial cable schematics won't, but the CI-V cloning cables will:
Yep, but this isn't a CI-V cable. It's a standard three wire serial
cable.
> Did the radio go into "clone out" mode and take a couple minutes to do
> the clone?
Yes.
> Can you send me the ic2820.img file in the working directory so I can
> see if it looks like a valid memory image?
There isn't one.
Using chirp.py:
> ./chirp.py -r ic2820 -s /dev/ttyS1 --download-mmap
|==| 100.0% Cloning from radioTraceback (most recent call last):
File "./chirp.py", line 199, in
radio.sync_in()
File "/home/bmury/software/chirp-0.1.2/chirp/ic2820.py", line 62, in sync_in
self.process_mmap()
File "/home/bmury/software/chirp-0.1.2/chirp/ic2820.py", line 40, in
process_mmap
self._memories = ic2820_ll.parse_map_for_memory(self._mmap)
File "/home/bmury/software/chirp-0.1.2/chirp/ic2820_ll.py", line 121, in
parse_map_for_memory
m = get_memory(map, i)
File "/home/bmury/software/chirp-0.1.2/chirp/ic2820_ll.py", line 56, in
get_memory
raise errors.InvalidDataError("Radio has unknown tone 0x%02X" % _tonei)
chirp.errors.InvalidDataError: Radio has unknown tone 0x8E
RE: [dstar_digital] Re: CHIRP: An open-source programming tool for ICOM radios
> Support for programming the repeater modules and > the repeater controller under Linux would be a joy. > > Go figure that the GW runs on Linux, but you need > Windoze to set the frequencies in the repeater modules! Good point ... Since the USB ports result in com port emulation in Windows (and its been a while but I think for both the controller and the band modules there are Linux drivers for the chips) it shouldn't be too difficult to figure out what's going back and forth over that pseudo serial interface. I wonder if there's something available that would allow you to monitor the bytes in/out of the virtual com port. (Wonder if its some simple command line interface that ICOM built a Windows based GUI around?) Bob McCormick W1QA
Re: [dstar_digital] Re: CHIRP: An open-source programming tool for ICOM radios
Not a problem. If I kow what I am doing. Tom - Original Message - From: Dan Smith To: dstar_digital@yahoogroups.com Sent: Tuesday, July 22, 2008 9:48 PM Subject: Re: [dstar_digital] Re: CHIRP: An open-source programming tool for ICOM radios > Is there something special that a V82 or U82 wil not work with your > program? I don't have a V82 to play with, but there shouldn't be anything preventing me from adding support for it. In fact, I can try adding a function to the next version to allow downloading of the memory map for any type, which you can send to me for analysis. I may be able to decode some of it by proxy, if you tell me what you have programmed into the first few memory channels. Would you be interested? -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS -- No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.5.5/1569 - Release Date: 7/23/2008 1:31 PM [Non-text portions of this message have been removed]
[dstar_digital] "Satellite Weekend" Webcast - Automatic Digital Telemetry Capture
The AMSAT-UK “Satellite Weekend” will be held at the University of Surrey, Guildford, England over 3 days from Friday 25th until Sunday July 27th and is open to all. On the Sunday there will be several presentations on the GENSO project. The aim of this project is to automatically collect Digital Telemetry Data from Amateur Radio and Educational satellites. Currently the Amateur packet standard AX.25 is used by most satellites although one satellite under construction is planning to use D-STAR a trend which is likely to continue. For further details see http://www.uk.amsat.org/Colloquium/ Programme: http://www.uk.amsat.org/content/view/640/213/ Travel information: http://www.uk.amsat.org/content/view/23/52/ A site map showing location of the Management Building and the adjacent main car park and conference visitors parking can be seen at http://www.uk.amsat.org/images/stories/uosmap6.jpg New for 2008, it has been arranged with the University for "walkin" day visitors at lectures/beginners sessions. It does not entitle you to any other of the functions. There is no need to book, just turn up on the day. It would help if you could let us know in advance if you intend using this facility, please email [EMAIL PROTECTED] AMSAT-UK Tel: +44 (0)1258 453959 Email: [EMAIL PROTECTED] Join AMSAT-UK Online at: https://secure.amsat.org.uk/subscription/ Webcast: http://www.batc.tv/ AMSAT-UK Web: http://www.uk.amsat.org/ 73 Trevor M5AKA
Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios
> Well, my guess would be that's because it's downloading information that > isn't a normal memory image from the radio. Thus, when it's done, it > still doesn't have a valid image and won't let you try to export it. > > Did the radio go into "clone out" mode and take a couple minutes to do > the clone? Okay, I just tried and it worked through the serial port. I can't get my ID-800 to do that, so I'm guessing it's just a feature of the 2820, but I'll have to experiment some more. I will post a new version this afternoon with the ability to choose between a CI-V cable and a straight RS-232 cable. Brian, my memory image loaded fine through the front data port, so if you will send me your image (privately) I'll figure out why it's not loading and try to roll the change into the version I post with the cable switch. Thanks! -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS
Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios
> No, it's a homebrew cable. I'm using the front data port. So, someone else mentioned something about this. I wasn't aware that you could do clone operations through the front data port. You can use the CS-2820 through that port? > Oh? I didn't know that. I found a document online that shows a cable > schematic, it does not have them connected together. The serial cable schematics won't, but the CI-V cloning cables will: http://uk.geocities.com/blakkekatte/CIVhardware.html > Yeah, that works. I just did a successful download. It won't let me > export, import, or upload (those are disabled, and it says "no image", > even after downloading), but that's a different issue... I'm going to > play around with the command line tool and see what I can do with that. Well, my guess would be that's because it's downloading information that isn't a normal memory image from the radio. Thus, when it's done, it still doesn't have a valid image and won't let you try to export it. Did the radio go into "clone out" mode and take a couple minutes to do the clone? Can you send me the ic2820.img file in the working directory so I can see if it looks like a valid memory image? In the meantime, I'll try doing a clone of my 2820 through the front data port and see what I get :) -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS
Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios
On Tue, 2008-07-22 at 16:48 -0700, Dan Smith wrote: > It's strange that your cable doesn't seem to be echoing what the PC > sends. Are you using an OPC-478? No, it's a homebrew cable. I'm using the front data port. > In the ICOM (and I think all other) > cables, the TX and RX pins are tied together in the db9 connector, Oh? I didn't know that. I found a document online that shows a cable schematic, it does not have them connected together. > If you want, edit chirp/icf.py, and in the send_clone_frame() > function, > put "return frame" right after the "pipe.write(frame)" line. This > should stop it from eating and comparing the echo. Yeah, that works. I just did a successful download. It won't let me export, import, or upload (those are disabled, and it says "no image", even after downloading), but that's a different issue... I'm going to play around with the command line tool and see what I can do with that. Thanks for the help! Brian
