Remote Rig
RRC-Micro PC Client in English => General discussion => Topic started by: PY1KN on 2012-06-01, 04:53:29
-
Helllo
I am finally using my Micro PC client. I have version 1.5.4, under windows 7 with Kenwood ARCP-410 (new version 1.10).
I programmed the CW macros to work pile-ups (F1=PY1KN; F2= PY1KN PY1KN; F3=5NN TU). I have worked a few stations this way.
I have noticed that quite a few copied my call with an extra N in the end, as PY1KNN. At first I thought it was due to QRM or something else, but it hapenned more than once and again today with A5A. KL2A is too good an operator to make such mistake (I corrected my call a few times).
Since I have no sidetone in RRC-Micro PC Client, I am intrigued, as the software might be including an extra N at the end of my call.
Has anyone observed a similar problem?
Thanks
Marcelo, PY1KN not PY1KNN
-
Hi Marcelo
I have tested with the the F1 macros as you described and can't repeat the problem.
If you connect at serial port terminal program such as SecureCRT to the RRC-box and
turn on debugging by hitting 'd' and then '+', you will see what CW keys are received
and sent. Here is an example of me sending "PY1KN;"
The lines with Queued is CW-keys received and stored for sending.
The lines with Sending is CW-keys sent.
R-> Sending keep-alive FF 0D
R-> Sending keep-alive FF 0D
R-> Sending keep-alive FF 0D
R-> Sending keep-alive FF 0D
keyerAsciiAck: CharAck, Type:5, Seq:36, Free:9
keyerAsciiRxEvent: Queued P, seq 36, new index 1
keyerAsciiAck: CharAck, Type:5, Seq:37, Free:8
keyerAsciiRxEvent: Queued Y, seq 37, new index 2
keyerAsciiRxEvent: Sending P as .--.
keyerAsciiAck: CharAck, Type:5, Seq:38, Free:8
keyerAsciiRxEvent: Queued 1, seq 38, new index 2
keyerAsciiAck: CharAck, Type:5, Seq:39, Free:7
keyerAsciiRxEvent: Queued K, seq 39, new index 3
R-> Sending keep-alive FF 0D
keyerAsciiAck: CharAck, Type:3, Seq:36, Free:5
keyerAsciiRxEvent: Sending Y as -.--
R-> Sending keep-alive FF 0D
keyerAsciiAck: CharAck, Type:3, Seq:37, Free:6
keyerAsciiRxEvent: Sending 1 as .----
R-> Sending keep-alive FF 0D
keyerAsciiAck: CharAck, Type:3, Seq:38, Free:7
keyerAsciiRxEvent: Sending K as -.-
R-> Sending keep-alive FF 0D
keyerAsciiAck: CharAck, Type:3, Seq:39, Free:8
keyerAsciiRxEvent: Sending N as -.
keyerAsciiAck: CharAck, Type:3, Seq:40, Free:9
keyerAsciiRxEvent: Sending ; as -.-.-.
R-> Sending keep-alive FF 0D
keyerAsciiAck: CharAck, Type:3, Seq:41, Free:10
R-> Sending keep-alive FF 0D
R-> Sending keep-alive FF 0D
R-> Sending keep-alive FF 0D
R-> Sending keep-alive FF 0D
-
Hi Roland
Thank you for the reply. I am not sure how to set up SecureCRT. I run it on my control PC (where RRC-micro lies) and connect to my remote RRC?
If you want to check, I can send you my remote connection data in pvt.
Marcelo
-
Thanks to Mike.
It seems the problem was my RRC firmware that was too old.
I'll check later today, but I am sure this is the problem.
Thanks for a great product and support.
Marcelo, PY1KN
-
Hello Marcelo,
since a long time, (client rel. 1.2.1) I'm facing the problem of duplicate CW characters (random and not only the last one) using the stored messages or the keyboard.
This prevent me from using the RRC Client in CW. I have reported the problem to Roland and we did together several tests, but till now he was not able to replicate the problem and no solution found.
At the moment I'm using the CW section of TRX-MANAGER that is now working quite well with my TS-480.
The keyer of the old version 1.2.1 of the client did'nt have the problem, but all the following releases does.
I'm very interested to see if you can find the reason of the promblem. I'm also using W7.
Best regards and 73
I4GAD Enrico
-
Hi Enrico
Sorry for taking so long, I was travelling.
I solved my problem updating the RRC firmware to the latest revision. That shoud work.
73 GL
Marcelo, PY1KN
-
I have similar problem with extra characters with latest software. Any suggestions?
-
I have similar problem with extra characters with latest software. Any suggestions?
Latest RRC firmware, RRC Client software or both?
-
Client software. I haven't seen place to find to update RRC firmare. If you can direct to the appropriate page that would be great.
-
Client software. I haven't seen place to find to update RRC firmare. If you can direct to the appropriate page that would be great.
Sure. Check that you have latest version
http://www.remoterig.com/wp/?page_id=79
We start from there and lets see what happens.
Cheers
-
Roland,
I thought we are talking about RRC-Micro firmware.
For RRC-1258 I have 2.65 firmware.
-
Roland,
I thought we are talking about RRC-Micro firmware.
For RRC-1258 I have 2.65 firmware.
Okay.. Sorry for the confusion.
Here is the latest RRC Client 1.6.1
http://www.remoterig.com/wp/?page_id=93
-
I had all new software and firmware. As I bought RRC-micro a while ago I thought that you mean to update firmware of RRC-Micro. It sounds logical and I was looking it on the Download area. I didn't find it because it doesn't exist.
So know we all on the same page. Being updated I have extra characters sent. It can be more than one.
For instance it can send cq cqq eyy8mmmm instead of the text cq cq ey8mm
Using XP environment. Audio In and OUT works flawlessly.
-
Will have a look at this.
Could you turn debug on and run a session which leaves some characters out
and the exit the program. Send the file Documents\RRCMicro\mblog.txt to me.
Thanks
-
Roland,
Any news please?
-
Roland,
Any news please?
Hi. I can understand that you are asking.
I actually has been occupied with other work and has not been able to get into this until now.
Sorry about that. I actually had a look at it to day but could not find any direct errors in the log-file I got from you.
So I guess this needs more investigations. Will set up as test rig tomorrow afternoon and make some stress tests
and see if I can repeat the problem. You are two individuals having (as to my knowledge) having the same problems
so finding what happens is really in everyone's interest.
-
Same behaviour here.
CQ DE OE1TKW , K and W doubly sent.
checked with two remote RRCS ( one for K3, one for FT-2000)
when sending,
the chars CQ DE OE1T turn white immediately, sending begins, ( sent chars turning black )
during transmission K and W individually turn white ,
and these are sent twice.
( what does the white colour mean?)
if the string is longer, all chars after "CQ DE OE1T" are sent twice.
I believe some buffer problem within the PC client.
OS is Windows Vista.
Will debug as described in the thread.
73
Helmut, OE1TKW
-
Hi. Yes we have found some strange behavior and is working on the problems.
Thank's for your patience.
-
Hi Guys.
Have a beta that might solve this.
You can test it by downloading http://www.remoterig.com/firmwares/RRCMicro_1.6.4_BETA.zip (http://www.remoterig.com/firmwares/RRCMicro_1.6.4_BETA.zip)
It contains both RRC firmware and the RRC Client
Install both and tell the result
/roland
-
Hi Roland
Beta version 1.6.4 seems to work fine for me. No missed or double sent characters now.
Thanks
/Göran
-
I installed both.
1. Can't hear my CW sending except last dot in transmittion.
2. Port assigned to CI-V seems like not working. At least TRX-manger could not see radio any more.
-
you have select the the COM ports in the Profile again.
-
the beta fix works prefect for me.
Thanks !
Helmut, OE1TKW
-
Managed to make it work. To operate I was needed to remove all previous versions and Virtual ports. It started to work after this.
I did on air testing with some guys and CW sending is perfect now. No problem at all. I send number of test messages on different speed with no errors. Only one thing that I was not able to fix that I can't hear my CW sending. Only one last dot when switching from TX to RX. Hope it will be resolved too.
So far progress made by Microbit team is superb!