I had my son create a WRL account on my ‘puter. Went fine. Had him open the Cat Control widget and connect the radio. Went fine. I had him create a new log (Pota templet). Went fine. Had him click on “Spotting with Pota and 20m selected. Starting on 40m, when he clicked on the the 20M spot, the radio did not do its typical dance and just stayed put. Had him switch bands and dial in the contact and then click on the contact which then populated in the contact section. Made his contact. Tried clicking on the next spot but again, the radio did not do the dance. The green “DOT” is lit. He dialed it in and the log did follow the radio (freq). After he left, I logged back into my account and the radio danced each time I clicked a new spot. I am a premium memeber, he is basic, not that that matters. So, the log follows the VFO, but the radio did not follow the log. I did cycle the radio. Got me scratching my head. I’ll have him try again later but was just wondering if it’s “account” related. I Integrated on my account the Cat control. I looked at the integration page under his account and it allows for a DL but I assume it is alrady downloaded. The app recognizes the radio, his log follows the VFO, so, I’m… stumped. Any suggestions would be appreciated.
@N0LAF When you initially launch the cat control app you have to login to your account so at that point the cat control app is connected to the account you logged in with. Make sure you have the cat control account connected to your account and not his.
Also make sure you have your COM port settings set properly per the below and that the CAT Time Out Timer (this is a radio setting) is set to 100Msec and not 10msec.
-
Important Notes (For Windows Users):
-
Go to ‘Device Manager’ –> ‘Ports (COM & LPT)’ and right click on your COM port for your radio, then click ‘Properties’
-
Under the ‘Port Settings’ Tab, make sure you have set the baud rate under the ‘Bits Per Second’ drop down that you’ve set inside your radio settings (do this for both COM ports for your radio, if you have more than 1).
-
If you have a ‘Power Management’ Tab make sure to uncheck/disable the two options here that say “Allow the computer to turn off this device to save power” & “Allow this device to wake the computer”
-
It sounds like the cat control app is logged into his account instead of yours maybe.
Thanks & 73
Brad K4AZE
Thank you so much Brad. Next time he comes over I will see about login the cat control app into his versus mine and see if it works. That all makes sense if I can’t figure it out from there I’ll just cry. Or maybe reach out again but hopefully between him and I will figure it out. Again thank you very much.
@N0LAF No worries, let me know what he find out and if you are still running into trouble just shoot a reply here we’ll get it worked out for you.
So the son came over and we tried again. I will admit, I missed the Cat time-out note and have changed it to 100ms. after he left. Same computer, same radio (FT-710), same connections. As we started out, turning on the computer and radio, we logged me out both Cat Control and Logger and retarted. Nothing. Logged him out/me in on both and nothing. Last time (last night) I used it it worked great. Went to integrations and saw a new version, downloaded and tried. Mine worked as expected. Logged me out of both and him back into both and nadda. Logged me back in both and, nadda. I shut off the radio, unplugged the USB, shut down the CC and logger then brought it back online. Everthing worked good for me (N0LAF). Switched it back over to his account (KR4BAO), both CC and logger and did not work (no radio dance). I wanted to shut it all down like I did when I had an issue but he had to leave. I’m not sure (because I have no clue) if this is an issue caused by the time out setting but when I get it working on mine it’s great. Just switching over the operator to his account and then back seems to be the issue. Another question. I had him hit the Cat Control on the integrations page under his log to see if that was needed, but I’m thinking that shouldn’t be needed? It didn’t change anything, though it did DL it again.
Lastly, as a brag, my son just bought his first radio and is patiently waiting its arrival. FTX-1 Optima.
@N0LAF So if I’m understanding correctly what I think might be happening is that the com ports that the computer is assigning to the two radios are different (which would make sense) but when your opening the cat control app and logging out and logging in between accounts your probably using the same com port in the WRL cat control app drop down.
Which would explain why one radio is working and the other isn’t when swapping between the two because logging out and logging in under a different account shouldn’t have any effect.
What would be different is each radio is assigned a different com port in device manager (or two com ports per radio at least for the 991a and dx10 (not 100% sure on the 710 but i would assume it creates two com ports like the 991a and dx10 does - one for the enhanced com port and one for the standard com port) ).
So when your swapping the radios and logging out and logging back in your still selecting the same com port from the WRL Cat control com port drop down, so one radio works and the other doesn’t.
I think that would explain what is happening……IF I’m understanding correctly.
Thanks & 73
Brad K4AZE
No sir, I’m not explaining it well.
One computer. On Radio. One USB connection.
I log out of the browser and close cat control. He opens and logs in via cat control with his call sign and password.
The only physical difference is me moving away from the computer and him moving in front of it.
@N0LAF Ohhh ok I understand now. Sorry wasn’t following. IDK this is a new one. Let me reach out to the team and get their feedback on this one.
Thank you sir. Next time he comes over we will try it again. And if I can get his to work by shutting everything down and bring it back up I’ll let you guys know that.
@N0LAF ok no worries. we’re looking on our side as well and checking logs. i’ll reach back out after we’ve dug into it a bit.