Hello everyone, I recently purchased an Icom 8600 and am really enjoying it. I've used RT Systems for other radios in the past and am, or at least I thought I was, fairly well versed in how their software works. I've run into a challenge and wanted to throw it out to the community to see if any of you can offer suggestions.
I've populated an RT radio file with some very basic info from RadioReference for my local area and am trying to send it to the radio. I've got the latest firmware on the receiver (1.34) and have updated the USB drivers on the dedicated PC I'm using to interface with the receiver. I *can* suck down the data from the radio into an RT file. Further, I can push back up the exact same file. The receiver works as I expect it to.
The problem occurs when I try to push a new radio file up to the receiver. I tried two methods - I am a premium subscriber on RR and had the download tool create an 8600 specific file. When I try to push that to the radio using RT Systems, it goes through its "CLONE IN" process and then either hangs at the end or fails and reports "ERROR". Ok, I sucked over the data from the radio and copied and pasted the data from my RR files to put into the file from the radio. Then I push that up to the radio. No joy. In an attempt to trouble-shoot, I manually added a few rows/records in the file that I pulled from the radio and pushed them to the radio - works fine.
So... it's something to do with my larger files, I think. The "larger" files have about 200, 250 rows. I'm using five groups and have applied unique names to each group. The group names are less than 10 digits. I've also perused through the file and can find nothing really unexpected in the file - errors in the mode, frequency out of band, etc.
I don't know that this will be my "final" file, but I'm just trying to learn how to interface with the radio from an RT Systems perspective. I've attached the RT Systems file to this post as a zipped file. Would greatly appreciated any pointers. I supposed I could just create new files and add ten rows at a time to the data until I find the offending record - I'm assuming that something in the datafile is not grooving to the radio.
Many thanks,
dan
I've populated an RT radio file with some very basic info from RadioReference for my local area and am trying to send it to the radio. I've got the latest firmware on the receiver (1.34) and have updated the USB drivers on the dedicated PC I'm using to interface with the receiver. I *can* suck down the data from the radio into an RT file. Further, I can push back up the exact same file. The receiver works as I expect it to.
The problem occurs when I try to push a new radio file up to the receiver. I tried two methods - I am a premium subscriber on RR and had the download tool create an 8600 specific file. When I try to push that to the radio using RT Systems, it goes through its "CLONE IN" process and then either hangs at the end or fails and reports "ERROR". Ok, I sucked over the data from the radio and copied and pasted the data from my RR files to put into the file from the radio. Then I push that up to the radio. No joy. In an attempt to trouble-shoot, I manually added a few rows/records in the file that I pulled from the radio and pushed them to the radio - works fine.
So... it's something to do with my larger files, I think. The "larger" files have about 200, 250 rows. I'm using five groups and have applied unique names to each group. The group names are less than 10 digits. I've also perused through the file and can find nothing really unexpected in the file - errors in the mode, frequency out of band, etc.
I don't know that this will be my "final" file, but I'm just trying to learn how to interface with the radio from an RT Systems perspective. I've attached the RT Systems file to this post as a zipped file. Would greatly appreciated any pointers. I supposed I could just create new files and add ten rows at a time to the data until I find the offending record - I'm assuming that something in the datafile is not grooving to the radio.
Many thanks,
dan