Remote Rig
RRC 1258 Support in English => General discussion forum => Topic started by: wi4usa on 2010-10-06, 01:48:25
-
I hope someone can help. I have the RRC-1258 MKII and the RRC-Micro that I'm trying to get to work with a Kenwood TS-480. I am using Windows XP 32-bit. The software installed fine and I have com 8 - 10 created as virtual ports by the software. I am able to connect to the sip fine. My baud rate on the radio is set to 57,600. What I'm not able to do is to use the com ports to get cat data for Ham Radio Deluxe. What am I doing wrong?
I am assuming that com0 is used for the rrc-1258 to communicate to the RRC-Micro. Should I put cat control on com1 or com2. I have tried both with no success. Ham radio deluxe just will not connect to the com port. I am connected to the sip fine. You can try to connect on your own at wi4usa.dyndns.biz. There is no password at this point until I can get it working. Has anyone done this configuration and got HRD to get cat info from the serial port? Can someone please, please send me all of your settings.
By the way, I also own the control portion of the RRC-1258 as well and I am able to control the radio through the remote head no problem. So I know the wiring is correct. I just can't get the serial port working when using the RRC-Micro.
Someone please help!
73 de wi4usa
Thom
thomas.jw.baxter@gmail.com
-
You don't say anything about CATcable. You need a serial cable from Radio-RRC/Com2 to Radio CAT port. See Kenwood in general. HRD can not handle the Control panel protocol.
73 de mike
-
I have a standard serial cable from com2 on the interface to the radio.
-
Hi
I don't think there are standard cables which fits check http://www.remoterig.com/schema/Kenwood-cable-K15-2.pdf
first try with the RS232 cables direct from the PC to the radio, connect them toghether without the RRC:s, if it works then you can try with the RRC:S
de mike
-
All is well now. The release of the RRC and the micro client made my TS-480 connect and play with HRD today. Great job with the latest Beta guys. I really appreciate it!
73 de wi4usa
Thom
-
Thom,
Could you please give the settings you used to make this work?
I installed the new beta and 2.27, but it still doesn't work.
Thanks & 73,
Mitch DJ0QN / K7DX
-
Mitch, tried with the new software today and all except PTT is working,
PTT only works 2 seconds and then release the connection,
PTT didn't work in previous releases also.
BTW for HRD to work you can not go higher then 38400 baud !!!
so the TS480 comport and HRD should not be set higher.
Guy ON4AOI
-
Guy,
I still can't get it to work after lowering the baud rate. I must be missing
some setting. It would be great if you and Thom were to provide a list of
correct settings.
Thanks & 73,
Mitch DJ0QN / K7DX
-
Guy,
I still can't get it to work after lowering the baud rate. I must be missing
some setting. It would be great if you and Thom were to provide a list of
correct settings.
Thanks & 73,
Mitch DJ0QN / K7DX
I might have lost track of what your problem is, so asking what is that that doesn't work? The audio, HRD, something else?
-
I didn't report a problem and try it out earlier, since the
forum reports were that it didn't work with the TS-480.
Then I read that the new version works, so I tried it out and can't
get it to work, so that's why I am asking for the settings from the
other guys.
The instructions are not all that clear to me, and my radio RRC-1258
COM2 setting doesn't allow it to be set in logical parallel with COM0, it
goes back to inactive. I understood that this setting is necessary
to allow HRD to access the TS-480 and the 2nd com port on the Micro
Client. I assume that I misunderstood something.
73,
Mitch DJ0QN / K7DX
-
Which "Hardware" version do you see on the "Info" page? Which "Program mode" are you using?
-
Hardware is version 5.
"Program Mode" is 5 - TS480.
-
I am not 100% updated myself when it comes to all possible combinations of settings. But I do know that if you set "Program mode" to 5, then setting Com 2 to parallel isn't allowed, and that is why you see it go back to inactive. I would think that you should have Com 2 in mode 4 and match that with similar settings in the PC program. Mikael isn't here for the moment, so if this doesn't help then we have to wait for him.
-
Ok, thanks, Jan.
Also, hopefully the other guys will mention how they got it to work.
73,
Mitch DJ0QN / K7DX
-
It is a weird problem
running XP home --- RRC-CLIENT + HRD works ok except that I only have PTT for 1-2 seconds
and this is everytime I try
running vista home RRC-CLIENT + HRD works perfect even the PTT is acting normal just after you first installed it BUT rebooting or restarting rrc-client (remains ok) and HRD is not working anymore even with administrator rights, HRD cant get connection with the TS-480 anymore.
reconnecting to the xp home pc and all is ok again except for the PTT
Guy ON4AOI
-
Guy,
I meant the settings on the radio RRC and in the PC Client,
not the operating system. It would be good to compare.
Thanks & 73,
Mitch DJ0QN / K7DX
-
What is the symptom of HRD not being able to connect? Can you check Window's Event Viewer, Application/System, and see if the virtual com port logs something there(Source "1274Serial")? And finally, run a session with the PC Micro Client's debug option set, close the Micro Client and send the created log file to me? (jan.andersson at microbit.se)
-
Ok MItch, I know what you meant but I think it is OS related
here we go
RRC-RADIO
5-TS480
com0 = 57600/8/1/OFF
com1 = mode-3, 9600/8/1/OFF rts/cts=YES , term=0d
com2 = mode-4, 9600/8/1/OFF, term=0d
RRC-CLIENT
com0 = inactive
com1 = inactive
com2 = 4 - kenwood via microbit serialUDP (com5) install only com2 when setting up, Term=3B
HRD
Kenwood
TS-480
com5/9600/8/1 rts and cts high
above works ok with xphome except the ptt drop after 1-2 seconds
above works also with vista-home with perfect PTT this time but after a reboot/restart
HRD can't communicate with the rig anymore
Guy ON4AOI
-
Hi Jan,
the vista laptop is from my wife and I only tried it out yesterday
because Mike asked me to, she needs it for here job so dont wanna
screw up that system,
all my other PCs (VISTA-& WIN7 Ultimate versions) refuse to install the
microbit serialUDP ports because they have conflicts with the eltima virtual
ports from my microham equipment.
I sended a list with all the software that is installed on the eeepc(xphome)
to Mike this morning to check if something is causing the PTT drop after 1-2 seconds
because it needs only to work on that PC and not on any other system I have,
Mike told me that they (maybe you) tested also on eeepc and didnt have the PTT problem
so .............
Guy ON4AOI
-
Hi Jan,
the vista laptop is from my wife and I only tried it out yesterday
because Mike asked me to, she needs it for here job so dont wanna
screw up that system,
all my other PCs (VISTA-& WIN7 Ultimate versions) refuse to install the
microbit serialUDP ports because they have conflicts with the eltima virtual
ports from my microham equipment.
What are the symptoms of "refuse to install"?
I sended a list with all the software that is installed on the eeepc(xphome)
to Mike this morning to check if something is causing the PTT drop after 1-2 seconds
because it needs only to work on that PC and not on any other system I have,
Mike told me that they (maybe you) tested also on eeepc and didnt have the PTT problem
so .............
Guy ON4AOI
That's right, we don't see that PTT behaviour on our EEPC. Therefore the log I asked you for is even more important.
/Jan
-
They install Jan
But
IN
Device manager
Ports
The microbit Serial UDP driver doesnt look if the comport is allready in use or not
in my case they installed on com9-11-12 but they were allready assigned
since there is no way to change the serial udp comport settings you get the following
result
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Click 'Check for solutions' to send data about this device to Microsoft and to see if there is a solution available.
look at the picture attached
Guy
-
Guy(ON4AOI)
We have a new version of the PC client that might fix the problems you see with PTT on XP. There was an issue that didn't show up every time, and not on all computers, not even of same type.
As for the virtual com ports not being installed correctly it seems strange. We are relying on Windows' installer functions to assign a valid and free number for the com port. That is, we don't have control over which port numbers get assigned. Though somehow it obviously fails in your case.
I have scanned the registry and found that the com port numbers are stored under keys like this:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\PORTS\0000\Device Parameters]
in a parameter called "PortName". If you have more than one port there should be one:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\PORTS\XXXX\Device Parameters]
per port. (XXXX=0000, 0001 etc)
Changing the "PortName" to something free might solve your problem temporarily. (Note that the port will still have the same name in Device Manager) Be also warned that messing with the registry might damaged your OS ;)
-
Guy(ON4AOI),
I have made a small Windows Console program which enumerates Windows' com port database and prints out info about numbers in use. It would be valuable if you ran that on your "multiple virtual ports" computer(s) and provide us with its printouts. It needs to be run as Administrator in Vista/Win7. You can find it here: http://www.remoterig.com/downloads/Win32SerialPortTest.zip (http://www.remoterig.com/downloads/Win32SerialPortTest.zip)
-
Duh!!
Just found out that it is indeed possible to change com port number from within the Device Manager!
In Win 7(and most likely Vista): Right click the com port, select "Properties", go to the tab "Port Settings" and click "Advanced". ;)
-
Jan,
ASAP that I have time today I will test out new version
and other things you sended
BTW I know how to handle with regedit hi
will look at the properties but as far that I remember it
didnt have a advanced tab in vista ultimate
Guy ON4AOI
send from IPAD
-
Jan,
in vista-ultimate there are no Port Settings available
otherwise I would have changed them myself.
see attached screen dump
-
Does that apply to the other working com ports too? Maybe it isn't there because the port isn't up and running?
-
No,
real comports have the port settings
virtual ports dont have that because they are setup by the software.
Difference between microham virtual ports and PC client ports setup
is that the user can asign the portnumbers for the eltima drivers
and pcclient does it for you (in my case wrong), in the meantime I know why
I run your serialporttest a few times and found out that if a port is not in use
at the present time the installer try to setup on that portnumber even if it is in your
system/hardware/portlist
see the attached screendump,
on the left you see that comport 9 is reserved for FSK, comport10 for PTT, Comport11 for footswitch
and not visible is comport12 that goes to my prosistel
comport 15 isnt seen in the test but was active (cat)
comport 16 was not in use but detected as it was in use
I think it would be better to compare with what is actually in DEVICE MANAGER/PORTS
instead of checking what is not in use at the time of installation
btw couldnt resist to test out directly so drove home to get some updates for you
Guy ON4AOI
-
Let me clarify a few things:
1/
The small program I sent you is based on API functions, exposing a "COM port database", provided by Windows for programs that explicitly want to know which ports are available and free to use. Calling those APIs isn't something we explicitly do when installing the com ports.
2/
As mentioned, our com port installer doesn't make the decision which com port number to use, Windows does that, obviously based on the information it keeps track of using the mentioned APIs as our com ports want to install the first one as COM9 which the test program also detects as first available port.
So my theory is that it's your other ports which install themselves somehow "directly", for ex. by modifying the registry, skipping the use of the mentioned APIs of which there is one function which "claims" a port and marks it as used. Doing so means that other programs which directly(using the APIs) or indirectly(as our com port drivers most likely do when installing them) use those APIs will be fooled into thinking there are free ports which actually isn't that. At least that is what it looks like based on the info we now have.
Great that you are eager to test and provide us with feedback! :)
-
Jan,
First test with what you sended me is not OK
HRD doesnt communicate with radio (eeepc on winxp)
Guy
trying a different way now
-
Jan and all other
IT IS WORKING NOW !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
RRC-1258MKII remote to RRC-1258MKII radio , was perfect allready
RRC-Micro PC client to RRC-1258MKII radio + HRD controlling
ALL is working now just the way it should be.
First attempt didnt work see previous posting
How I solved it after installing the new firmware.
and HRD didnt found the rig
Unplug the RRC client
Restart windows xp (maybe not needed but it doesnt arm)
Plug in the RRC client
BUT very important is to restart the RRC-1258 MKII at the radio side
it is easy done.
Now HRD will startup/work with the radio,
restarted 20 times now and all is still working stable
Guy ON4AOI
-
Jan,
concerning your message
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\PORTS\0000\Device Parameters]
in a parameter called "PortName". If you have more than one port there should be one:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\PORTS\XXXX\Device Parameters]
per port. (XXXX=0000, 0001 etc)
This can be done easy and after a reboot the 3 UDP serials are installed ok in system, (with wrong comportnumbers but that we are aware of)
RRC-client to RRC-RADIO is OK but now with Vista-ultimate PC noway you can get HRD connecting the radio
Maybe others that have the problem with wrong serial numbers have more luck in vista
This PC is to complex with to many communication setups (programmers-virtual ports etc) that It might never work due installed software and drivers.
Most important was the XP-home eeepc PTT problem that has been solved with the latest (not public) release,
will check this weekend on vista laptop, when not needed for my wifes job.
Hope for a release that works with the ARCP-480 software from Kenwood, tried with different virtual port setups because arcp-480 cant connect to com2 since it is in use by the RRC-CLIENT also tried with a bridge and splitter between them didnt solve the problem
Guy ON4AOI
-
RRC-client to RRC-RADIO is OK but now with Vista-ultimate PC noway you can get HRD connecting the radio
And what are the symptoms of this failure? What does HRD show?
Have you checked Windows Event Log "Application" for records with source "1274Serial"? The "System" log might also show something. Suggest you clear the logs first, then attempt using the ports.
See attached image for what it might look like.
/Jan
-
Jan I will check this evening
cant stay home again hi
Guy
-
Hello Guy and Jan ,
1st posting here.
Reading with much intrest the writings about the COM Ports problem and there obviously high portnrs.
After purchasing only clients as we have servers on post I als, discovered that when installing a virtual port the SW
gave it a number somewhere around 15 or so. As I wanted to use the whole system within N1MM and with a remote prosistel rotor , and only have 1 COMport(PCI)in the "old" PC , I had to use a USB based serial adapter.
Within the configuration menu I could assign a lower nr than "9" as N1MM only uses 8 ports (as yet).I was aware that apparently all "ports" between 1 and 15 where "in use", hi.But choosing one in the single digits group e.g.8 was not creating a conflict and worked marvels.
Only my 5 EU cents ,hi.
Tnx Guys and Guy for the great input here,
Best of luck and I'll keep reading,
73 de Jim ON5UM/OP5T ;
-
Forgot to mention that the OS was Windows 7 .
Bye