RE: cable problems
Michael Baessler <[email protected]>
| Newsgroups | gmane.recreation.radio.hardware.icomr2 |
|---|---|
| Message-ID | <[email protected]> |
Brian, Thanks a bunch for the info. In answer to part of your question, when trying to load TO the radio, nothing happens. I've downloaded several different software packages for the R2 and they all have some kind of com issue with the scanner. This happens not only on my desktop at home but also my system at work. I've checked and double checked for any com port conflicts and none are evident. I am most likely going to have to order a new cable as it seems that I am not getting 2 way communication. A signal is obviously getting to the radio based on the display switching to CL OUT but nothing changes on the computer and I get the error messages after a moment or two which seems to indicate to me that nothing is coming from the radio. I just hope it's the cable at fault and not the R2. Thanks again. I'll keep you posted on what happens. Sincerely, Mike Baessler -----Original Message----- From: Brian B [mailto:rocketmannm-/[email protected]] Sent: Sun 2/8/2004 4:22 AM To: [email protected] Cc: Subject: RE: [icomr2] cable problems There may be some clues in what you pointed out yourself. For instance: I have selected a download from the scanner. In fact the radio will actually display "CL OUT" but nothing downloads. The program errors out saying either that a cloning cable is not connected to the specified port or that the ICOM is off or that there is an error opening COM1. The fact that the radio displays CL OUT shows that communication is happening via the cable on some level - otherwise the radio would display nothing. Do you get the same errors when trying to load information _to_ the radio, versus selecting "from" the radio? If not, the cable is likely fine. When I plug a stereo to mono adapter on the end of the cable it works fine on my Pro-96. Again, a sign that your cable is functional, as the protocols used by your PRO-96 are similar. I wonder if it would be possible to plug a mono to stereo adapter on the end of that configuration and make it work with the IC R2. This is sort of away from the mark - the cable is designed to be used WITHOUT a mono/stereo adapter, since it is the one sold by the manufacturer. When doing any troubleshooting, the simpler things are, the easier it is, especially when computers and communications are involved (I work with both as a robotics engineer). Adding adapters is likely to confuse (if not defeat) any systematic hunt for your culprit. Since you basically have only 3 "systems" to test, I'd tackle those first. My first suspect would be a software situation. As Bob Parnass suggests, I'd double check and try different Com configurations first, especially since your error message is coming from that software. From your indications, it sounds like a poll signal is going out, but the computer isn't seeing the handshake back. This may be a setting in the software, or even bad software (amazingly, perfectly good software does get corrupted now and then...) . If settings don't do the job, try removing TK2/TCL and downloading another copy, and see if the reinstall fixes it. If that doesn't work, make sure you don't have any other devices sharing the ports in the background. I had an instance when trying to set up a GPS unit for a COM line, where a PDA program had changed my FIFO settings and wouldn't let it talk properly.....si milar to your glitch. If all that checks, Try one of the other R2 software programs available on the web. If you still have a glitch at this point, I'd say the computer/software is all but eliminated. Next in line is the cable - I think you have pretty much tested that to a point where it is not likely the problem, but you can get the schematics for the cable online and do point-to-point testing from that, or spring for a new cable if that's not feasable, since they aren't very expensive - and the aftermarket versions (which work well, that's what I use) function just fine and are even cheaper. At this point, there's only one culprit - your radio. You can try to do a software reboot on the radio, hoping that this fixes things - but if this is genuinely the problem, you run a slight risk of things getting worse, not better, after a reset. Beyond all that, you'll just have to live with it or buy a new rig. Most involved digging you'll probably do is hunting for software conflicts - since that's right in line with your work, you have a definite advantage there, as a lot of that info is buried where most people can't find it without a hand holding walk-thru by a IT person. Good Luck, hope this was a little help.... -Brian --------------------------------- Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online [Non-text portions of this message have been removed] Post message: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List owner: [email protected] _____ Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/icomr2/ * To unsubscribe from this group, send an email to: [email protected] <mailto:[email protected]?subject=Unsubscribe> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service <http://docs.yahoo.com/info/terms/> . [Non-text portions of this message have been removed] Post message: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List owner: [email protected] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/icomr2/ <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/