I wholeheartedly agree with your comment about lack of documenting all the tinkering required to get this to work. This normally means that you have to have power applied to the radio (says captain obvious), but also the radio had to be turned on at least once before the connection attempt.
#ICOM 7300 115200 SCOPE RS BA1 DRIVERS#
One other thing that took me a while was to make sure that the radio drivers are loaded on the server pc before a connection attempt. I think one of the problems with this software is that while almost everyone eventually gets it working, nobody ever documents all the tinkering they did when they were finally able to make it work, so nobody is ever sure exactly what they did that resolved it. Note: you should be able to see these first three on the Remote Utility window
On the Remote Control window, go to 'Option', and 'Connect Settings' and verify your com port, baud rate, and CI-V address.īaud rate = 115200 (again, yours may vary)ĬI-V Address (radio) = 94 (Most 7300's should have this setting) When I run the Remote Utility on the remote PC, and attempt to connect, it connects but, when I run the Remote Control on that remote PC, the Cannot open COM port error occurs.Īny suggestions would be much appreciated. I thought I had everything configured as directed but, although the base station PC connects to the radio, I have no errors indicated, and I can control the radio via the base station PC, when I attempt to control the radio from the remote PC (on the same Wi-Fi home network), I get that "Cannot open COM Port" error. I have the radio connected via a USB cable to the base station PC and RA-BA1 installed on both PCs. I expect I am misinterpreting something and there is a simple configuration that I have wrong.
#ICOM 7300 115200 SCOPE RS BA1 PRO#
I am running the latest Win10 Pro OS version on both my base station PC/server and my remote PC. I know this is a very old thread but, although I've had the software for quite some time, I am just now attempting to remote my 7300 and I am getting exactly the same error.