Author Topic: RRC Winkey bug? / N1MM+ send incomplete message/callsign  (Read 11448 times)

yo3irm

  • Jr. Member
  • **
  • Posts: 50
    • View Profile
Hello,

I'm running the latest RRC firmware (2.87) and I've encounter a strange issue running N1MM+ with RemoteRig.
N1MM+ stop sending in the middle of the message, for example if I'm running in RUN mode F1 should send as per my CQ config file:

test yo3irm

but it send:

test yo3irm
test yo
test
test yo3irm
test y
.............

I've troubleshoot this with Steve from N1MM team and he found to be an issue with RemoteRig
See his comments below in the ErrorLog.txt from N1MM+

Quote
Here's what happened, with my comments.

- N1MM+ starts sending TEST YO3IRM to Winkey (RemoteRig). Good.

Thread # 29 @ 2015-12-21 19:53:43.735 PM
  PutChar T
Thread # 29 @ 2015-12-21 19:53:43.737 PM
  PutChar E
Thread # 29 @ 2015-12-21 19:53:43.739 PM
  PutChar S
Thread # 11 @ 2015-12-21 19:53:43.741 PM

- Winkey acknowledges that it has started sending. Good.

  Winkey HandleStatus = 4
Thread # 29 @ 2015-12-21 19:53:43.743 PM
  PutChar T
Thread # 29 @ 2015-12-21 19:53:43.745 PM
  PutChar
Thread # 29 @ 2015-12-21 19:53:43.746 PM
  PutChar Y
Thread # 29 @ 2015-12-21 19:53:43.748 PM
  PutChar O
Thread # 29 @ 2015-12-21 19:53:43.749 PM
  PutChar 3
Thread # 11 @ 2015-12-21 19:53:43.750 PM

- Winkey starts echoing back characters as they are sent. Good.

  Winkey HandleChar = T
Thread # 29 @ 2015-12-21 19:53:43.752 PM

- Final characters sent to Winkey. Good.

  PutChar I
Thread # 29 @ 2015-12-21 19:53:43.754 PM
  PutChar R
Thread # 29 @ 2015-12-21 19:53:43.756 PM
  PutChar M

- Winkey reports that it has stopped sending. Bad. It has not finished echoing characters back to N1MM+. It should not report that it has stopped sending until after all characters have been sent, and the echo characters have been sent back to N1MM+. Receiving this prematurely also starts the CQ repeat timer prematurely, leading to the next CQ starting too soon.

Thread # 11 @ 2015-12-21 19:53:43.757 PM
  Winkey HandleStatus = 0

I see this pattern throughout the log file. It needs to be fixed by RemoteRig.

73,
Steve, N2IC

Any suggestion ?
Could be something on my RRC configuration ?

Thank you


Jan (Microbit)

  • Software Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 1796
    • View Profile
    • Email
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #1 on: 2015-12-22, 09:50:57 »
We will not be able to look into this until sometimes after the holidays. Meanwhile it would be great if some other Winkey/N1MM+ user could share their experiences about how it works.
Always include type of hard/software and version when asking for support.

yo3irm

  • Jr. Member
  • **
  • Posts: 50
    • View Profile
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #2 on: 2015-12-22, 15:23:51 »
Thank you Jan.

Can someone share please his working configuration for: TS-480 & RemoteRig & N1MM+ ?
This is my configuration for
RRC Control

Radio SettingsSerial Settings

for RRC Radio

Serial Settings

Device Manager Port config:



N1MM+ config


Thank you for any suggestion !


yo3irm

  • Jr. Member
  • **
  • Posts: 50
    • View Profile
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #3 on: 2016-01-07, 16:13:38 »
Hello and Happy New Year!

Is there someone with TS-480 using N1MM+ as a contest software?
Can you share please your setup config ?
I've tried different settings combination but I have the same result, in RUN mode, N1MM+ does not sent the entire message, it stops/restart randomly.
My setup is working ok with win-test or winwarbler from DXLab.
I've checked also with http://k1el.tripod.com/WKdemo.html as suggested by KD0PO and I see no issues so it should be something with N1MM+ / RemoteRig / TS-480 combination.

Thank you

yo3irm

  • Jr. Member
  • **
  • Posts: 50
    • View Profile
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #4 on: 2016-01-10, 01:51:59 »
Can someone help?
It seems it is not only a N1MM+ problem.
I've recently installed win-test, the latest version and it doesn't work at all.
The error message is: "Winkey Device Init Error"
If I try to send CW it will send only the first character then will stop, at this point you cannot send anything else. If I hit "Esc" it allows to send again only the first character and then it stops.

Strange is that I've used the Win-Test 4.16 Demo version and it works ok but after that I've installed the registered version, 4.19 and it has the described behavior.
I've tried to uninstall the new version and install the old demo version but from this point on I received the same erorr message "Winkey Device Init Error" and the same behavior, even after an OS point in time restore.

Running the test tool from k1el, sometimes works ok, sometimes display the error message:
openComm:Success
Attach WK: Echo Mismatch (or Attach WK: No Echo)

N1MM+ works ok in S&P mode but it stops sending randomly in RUN mode.
No problem using the paddle attached to RRC Control and also no problem with CAT control or audio

I ran out of ideas so any help will be appreciated.

Thank you!

W1UE

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
    • Email
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #5 on: 2016-01-10, 15:04:00 »
What other programs do you have on your computer to create/manage virtual com ports?  Is there are Microham virtual com ports, or VSP virtual Comports, or any other program that manages virtual comports?  These programs sometimes conflict with each other, and you get funny things happening.  One of the common things I see happen when there is a virtual comport conflict is that information is conveyed one way (to the Winkey from the computer) but information is not conveyed the other way (from the Winkey to the Computer).

The solution is to start deleting programs that may conflict.  It is somewhat a trial and error method.  I don't know that this is your problem, but if there are virtual com port programs that you no longer use, try deleting them and then retry the app.  You also don't have to have any virtual com ports identified on your computer from the program; if it loads when you start your computer, then it may cause problems.

Dennis W1UE

yo3irm

  • Jr. Member
  • **
  • Posts: 50
    • View Profile
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #6 on: 2016-01-10, 22:46:41 »
Thanks Dennis, I'm using only VSP Manager but not in the same time with contest software running.
N1MM+ or Win-Test are connecting directly to the com port provided by remoterig for CAT and to WinKey port also provided by RemoteRig.
I don't have microHam or other virtual ports installed.

Strange is that in the same conditions, DXLab-Winwarbler is working without any issues, also tried DXLog as a contest software and is working in RUN mode and S&P mode without any issues.
I will try to remove VSP Manager and check again.

W1UE

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
    • Email
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #7 on: 2016-01-11, 02:40:42 »
I have had problems with the Microbit USB drivers and the VSP USB drivers in the past on some computer systems.  It might not fix the problem, but I'd definitely try removing VSP, reboot, then try it again.  GL!  UE

Jan (Microbit)

  • Software Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 1796
    • View Profile
    • Email
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #8 on: 2016-01-11, 10:42:06 »
We have added a new FAQ entry found here:

http://www.remoterig.com/wp/?page_id=3200

that might help finding out if there are problems with installed Com ports.
Always include type of hard/software and version when asking for support.

yo3irm

  • Jr. Member
  • **
  • Posts: 50
    • View Profile
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #9 on: 2016-01-11, 11:27:09 »
Jan, thanks for this checking software,
I've run MicrobitDeviceManager as per instructions, see below the quoted output, see also my actual env
Environment:
vspMgr - started, 2 COM pairs defined but not used by any software at this point


Device Manager configured to show all hidden devices:


Quote
Mon Jan 11 12:10:31 2016:
Starting MicrobitDeviceManager v1.4

----- Installed devices info -----

      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL02\7&2BC48FAE&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL02\8&8D6FFB0&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL03\7&2BC48FAE&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL03\8&8D6FFB0&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL04\7&2BC48FAE&0&0003
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL04\8&8D6FFB0&0&0003
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL01\7&7ED51EC&0&0000
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL01\8&209A8BF5&0&0000
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL02\7&7ED51EC&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL02\8&209A8BF5&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL03\7&7ED51EC&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL03\8&209A8BF5&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&COL01\8&2D40388&0&0000
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&COL02\8&2D40388&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2010&WI_01&CLASS_0000001A&COL02\8&18DA8134&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2010&WI_01&CLASS_0000001A&COL03\8&18DA8134&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_01&CLASS_0000001A&COL02\8&359D6A58&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_01&CLASS_0000001A&COL03\8&359D6A58&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_02&CLASS_0000001A&COL02\8&36DDFC06&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_02&CLASS_0000001A&COL03\8&36DDFC06&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_4024&WI_04&CLASS_0000001E&COL03\8&541994D&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_4024&WI_04&CLASS_0000001E&COL04\8&541994D&0&0003
MB      HIDClass   RRC 1258         HID\VID_1E3B&PID_1258&MI_00\8&2DDCA83A&0&0000
      HIDClass   ----------         USB\VID_046D&PID_C077\5&1BF0BA15&0&5
      HIDClass   ----------         USB\VID_046D&PID_C077\5&1BF0BA15&0&6
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_00\6&215F4E70&0&0000
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_00\7&16873459&0&0000
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_01\6&215F4E70&0&0001
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_01\7&16873459&0&0001
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_02\6&215F4E70&0&0002
MB      HIDClass   RRC 1258         USB\VID_1E3B&PID_1258&MI_00\7&20D2F81F&0&0000
MB      Ports   RRC1258 COM2 (COM3)         USB\VID_1E3B&PID_1258&MI_01\7&20D2F81F&0&0001
MB      Ports   RRC1258 COM0 (COM4)         USB\VID_1E3B&PID_1258&MI_03\7&20D2F81F&0&0003
MB      Ports   RRC1258 COM1 (COM5)         USB\VID_1E3B&PID_1258&MI_05\7&20D2F81F&0&0005
MB      Ports   RRC1258 COMExtra (COM6)         USB\VID_1E3B&PID_1258&MI_07\7&20D2F81F&0&0007
      Ports   ELTIMA Virtual Serial Port (COM10->COM11)         VSBC7\DEVICES\0000
      Ports   ELTIMA Virtual Serial Port (COM11->COM10)         VSBC7\DEVICES\0001
      Ports   ELTIMA Virtual Serial Port (COM12->COM13)         VSBC7\DEVICES\0002
      Ports   ELTIMA Virtual Serial Port (COM13->COM12)         VSBC7\DEVICES\0003
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_2010&WI_01&CLASS_0000001A\7&7ED51EC&0&01
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_01&CLASS_0000001A\7&7ED51EC&0&01
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_02&CLASS_0000001A\7&7ED51EC&0&02
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_400A&WI_03&CLASS_00000004\7&7ED51EC&0&03
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_4024&WI_04&CLASS_0000001E\7&7ED51EC&0&04
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_4031&WI_01&CLASS_00000004\7&7ED51EC&0&01
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02\7&7ED51EC&0&00

----- Com port database Info -----

Maximum ports available: 256
Ports in use:
COM3
COM4
COM5
COM6

----- Com port matching -----
Number   Inst.   Com Db   Action
3   X   X   None
4   X   X   None
5   X   X   None
6   X   X   None
10   X       None
11   X       None
12   X       None
13   X       None


Thanks

Jan (Microbit)

  • Software Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 1796
    • View Profile
    • Email
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #10 on: 2016-01-11, 12:02:24 »
It seems there are no overlapping Com ports even though the Eltima ports are not marked 'in use' in the Com port data base. You could follow the instructions how to make them marked in use, but I do not think it will solve your current problems, only future ones as it helps avoiding creating overlapping ports.
Always include type of hard/software and version when asking for support.

yo3irm

  • Jr. Member
  • **
  • Posts: 50
    • View Profile
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #11 on: 2016-01-11, 15:02:14 »
OK I've complete remove vspMgr, followed this plan:
1. vspMgr - delete COM Pairs
2. reboot PC
3. vspMgr uninstalled
4. reboot PC
5. N1MM+ check - same result, see also the error received from N1MM+


6. unpluged RRC Control from USB port
7. unistalled all Microbit devices with MicrobitDeviceManager (see result)
Quote
Starting MicrobitDeviceManager v1.4

----- Installed devices info -----

      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL02\7&2BC48FAE&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL02\8&8D6FFB0&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL03\7&2BC48FAE&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL03\8&8D6FFB0&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL04\7&2BC48FAE&0&0003
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL04\8&8D6FFB0&0&0003
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL01\7&7ED51EC&0&0000
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL01\8&209A8BF5&0&0000
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL02\7&7ED51EC&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL02\8&209A8BF5&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL03\7&7ED51EC&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL03\8&209A8BF5&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&COL01\8&2D40388&0&0000
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&COL02\8&2D40388&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2010&WI_01&CLASS_0000001A&COL02\8&18DA8134&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2010&WI_01&CLASS_0000001A&COL03\8&18DA8134&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_01&CLASS_0000001A&COL02\8&359D6A58&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_01&CLASS_0000001A&COL03\8&359D6A58&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_02&CLASS_0000001A&COL02\8&36DDFC06&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_02&CLASS_0000001A&COL03\8&36DDFC06&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_4024&WI_04&CLASS_0000001E&COL03\8&541994D&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_4024&WI_04&CLASS_0000001E&COL04\8&541994D&0&0003
MB      HIDClass   RRC 1258         HID\VID_1E3B&PID_1258&MI_00\8&2DDCA83A&0&0000      UNINSTALLED!!!
      HIDClass   ----------         USB\VID_046D&PID_C077\5&1BF0BA15&0&5
      HIDClass   ----------         USB\VID_046D&PID_C077\5&1BF0BA15&0&6
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_00\6&215F4E70&0&0000
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_00\7&16873459&0&0000
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_01\6&215F4E70&0&0001
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_01\7&16873459&0&0001
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_02\6&215F4E70&0&0002
MB      HIDClass   RRC 1258         USB\VID_1E3B&PID_1258&MI_00\7&20D2F81F&0&0000      UNINSTALLED!!!
MB      Ports   RRC1258 COM2 (COM3)         USB\VID_1E3B&PID_1258&MI_01\7&20D2F81F&0&0001      UNINSTALLED!!!
MB      Ports   RRC1258 COM0 (COM4)         USB\VID_1E3B&PID_1258&MI_03\7&20D2F81F&0&0003      UNINSTALLED!!!
MB      Ports   RRC1258 COM1 (COM5)         USB\VID_1E3B&PID_1258&MI_05\7&20D2F81F&0&0005      UNINSTALLED!!!
MB      Ports   RRC1258 COMExtra (COM6)         USB\VID_1E3B&PID_1258&MI_07\7&20D2F81F&0&0007      UNINSTALLED!!!
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_2010&WI_01&CLASS_0000001A\7&7ED51EC&0&01
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_01&CLASS_0000001A\7&7ED51EC&0&01
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_02&CLASS_0000001A\7&7ED51EC&0&02
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_400A&WI_03&CLASS_00000004\7&7ED51EC&0&03
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_4024&WI_04&CLASS_0000001E\7&7ED51EC&0&04
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_4031&WI_01&CLASS_00000004\7&7ED51EC&0&01
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02\7&7ED51EC&0&00

----- Com port database Info -----
COM3 released successfully
COM4 released successfully
COM5 released successfully
COM6 released successfully

Maximum ports available: 256
Ports in use:

----- Com port matching -----
Number   Inst.   Com Db   Action

8. reboot
9. checked with MicrobitDeviceManager (see result)
Quote
Starting MicrobitDeviceManager v1.4

----- Installed devices info -----

      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL02\7&2BC48FAE&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL02\8&8D6FFB0&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL03\7&2BC48FAE&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL03\8&8D6FFB0&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL04\7&2BC48FAE&0&0003
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL04\8&8D6FFB0&0&0003
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL01\7&7ED51EC&0&0000
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL01\8&209A8BF5&0&0000
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL02\7&7ED51EC&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL02\8&209A8BF5&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL03\7&7ED51EC&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL03\8&209A8BF5&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&COL01\8&2D40388&0&0000
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&COL02\8&2D40388&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2010&WI_01&CLASS_0000001A&COL02\8&18DA8134&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2010&WI_01&CLASS_0000001A&COL03\8&18DA8134&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_01&CLASS_0000001A&COL02\8&359D6A58&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_01&CLASS_0000001A&COL03\8&359D6A58&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_02&CLASS_0000001A&COL02\8&36DDFC06&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_02&CLASS_0000001A&COL03\8&36DDFC06&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_4024&WI_04&CLASS_0000001E&COL03\8&541994D&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_4024&WI_04&CLASS_0000001E&COL04\8&541994D&0&0003
      HIDClass   ----------         USB\VID_046D&PID_C077\5&1BF0BA15&0&5
      HIDClass   ----------         USB\VID_046D&PID_C077\5&1BF0BA15&0&6
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_00\6&215F4E70&0&0000
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_00\7&16873459&0&0000
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_01\6&215F4E70&0&0001
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_01\7&16873459&0&0001
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_02\6&215F4E70&0&0002
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_2010&WI_01&CLASS_0000001A\7&7ED51EC&0&01
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_01&CLASS_0000001A\7&7ED51EC&0&01
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_02&CLASS_0000001A\7&7ED51EC&0&02
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_400A&WI_03&CLASS_00000004\7&7ED51EC&0&03
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_4024&WI_04&CLASS_0000001E\7&7ED51EC&0&04
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_4031&WI_01&CLASS_00000004\7&7ED51EC&0&01
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02\7&7ED51EC&0&00

----- Com port database Info -----

Maximum ports available: 256
Ports in use:

----- Com port matching -----
Number   Inst.   Com Db   Action

10. uninstall Microbit Setup Manager (although perhaps not necesary)
11. reboot

At this point I should have a clean system

12. Downloaded the latest Setup Manager version 1.30
13. Install Setup Manager (as Admin) (is this ok or should be installed as a normal user ?)
14. reboot
15. Plug RRC Control USB -> automatically devices installed successfully
16. Check with MicrobitDeviceManager (see results)
Quote
Starting MicrobitDeviceManager v1.4

----- Installed devices info -----

      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL02\7&2BC48FAE&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL02\8&8D6FFB0&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL03\7&2BC48FAE&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL03\8&8D6FFB0&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL04\7&2BC48FAE&0&0003
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_01&COL04\8&8D6FFB0&0&0003
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL01\7&7ED51EC&0&0000
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL01\8&209A8BF5&0&0000
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL02\7&7ED51EC&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL02\8&209A8BF5&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL03\7&7ED51EC&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&MI_02&COL03\8&209A8BF5&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&COL01\8&2D40388&0&0000
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&COL02\8&2D40388&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2010&WI_01&CLASS_0000001A&COL02\8&18DA8134&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2010&WI_01&CLASS_0000001A&COL03\8&18DA8134&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_01&CLASS_0000001A&COL02\8&359D6A58&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_01&CLASS_0000001A&COL03\8&359D6A58&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_02&CLASS_0000001A&COL02\8&36DDFC06&0&0001
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_02&CLASS_0000001A&COL03\8&36DDFC06&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_4024&WI_04&CLASS_0000001E&COL03\8&541994D&0&0002
      HIDClass   ----------         HID\VID_046D&PID_C52B&REV_1203&MI_02&QID_4024&WI_04&CLASS_0000001E&COL04\8&541994D&0&0003
MB      HIDClass   RRC 1258         HID\VID_1E3B&PID_1258&MI_00\7&2DDCA83A&0&0000
      HIDClass   ----------         USB\VID_046D&PID_C077\5&1BF0BA15&0&5
      HIDClass   ----------         USB\VID_046D&PID_C077\5&1BF0BA15&0&6
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_00\6&215F4E70&0&0000
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_00\7&16873459&0&0000
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_01\6&215F4E70&0&0001
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_01\7&16873459&0&0001
      HIDClass   ----------         USB\VID_046D&PID_C52B&MI_02\6&215F4E70&0&0002
MB      HIDClass   RRC 1258         USB\VID_1E3B&PID_1258&MI_00\7&20D2F81F&0&0000
MB      Ports   RRC1258 COM2 (COM5)         USB\VID_1E3B&PID_1258&MI_01\7&20D2F81F&0&0001
MB      Ports   RRC1258 COM0 (COM6)         USB\VID_1E3B&PID_1258&MI_03\7&20D2F81F&0&0003
MB      Ports   RRC1258 COM1 (COM3)         USB\VID_1E3B&PID_1258&MI_05\7&20D2F81F&0&0005
MB      Ports   RRC1258 COMExtra (COM4)         USB\VID_1E3B&PID_1258&MI_07\7&20D2F81F&0&0007
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_2010&WI_01&CLASS_0000001A\7&7ED51EC&0&01
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_01&CLASS_0000001A\7&7ED51EC&0&01
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_2011&WI_02&CLASS_0000001A\7&7ED51EC&0&02
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_400A&WI_03&CLASS_00000004\7&7ED51EC&0&03
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_4024&WI_04&CLASS_0000001E\7&7ED51EC&0&04
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02&QID_4031&WI_01&CLASS_00000004\7&7ED51EC&0&01
      HIDClass   ----------         {A3535E08-EB26-49A9-8AE0-786ED1242812}\VID_046D&PID_C52B&REV_1203&MI_02\7&7ED51EC&0&00

----- Com port database Info -----

Maximum ports available: 256
Ports in use:
COM3
COM4
COM5
COM6

----- Com port matching -----
Number   Inst.   Com Db   Action
3   X   X   None
4   X   X   None
5   X   X   None
6   X   X   None

17. reboot
Starting Win-Test ->
Winkey Device Init Error - and it send only one character then stops, no other characters were send if you use any key, F1, F2 ...
If I press ESC then again if I hit F1 or other key, just one char is sent.

Sometimes, not always, starting DXLog after Win-test I have the same strange behavior also for DXLog.
Reboot PC - start DXLog -> same behavior, only one char sent
close DXLog and start WKtest from K1EL (as per K1el"WKdemo is a very useful diagnostic tool to determine if your Winkeyer is working properly. It will work with WK1 or WK2.") and I received the following "No echo" message:


Recycle power for for RRC Control - no effect
!!! - RRC Console restarted from web interface - DXLog start working correctly.
Running WKdemo after closing DXLog, returns Echo Mismatch, win-test & N1MM+ not working, same behavior



What I'm thinking now:
1. could try to reinstall setup manager and driver for com ports as a normal user, not admin
2. could be something in RRC Control & RRC Radio that is not configured correctly
3. win-test & N1MM+ use some features not implemented in RRC WinKey
4. issues with my hardware, although I've also moved the USB connection to other USB port on the back of PC, same result, anyway because DXLog and DXLab are working ok and N1MM+ and Win-test not, I don't think it is PC hardware related

Thanks

yo3irm

  • Jr. Member
  • **
  • Posts: 50
    • View Profile
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #12 on: 2016-01-11, 18:29:30 »
Used MicrobitDeviceManager to uninstall all microbit devices and reinstalled all as a normal user, not admin.
Same behavior, when I start N1MM+ I receive the mesage with too many bytes received...



Is there any way to enable a log for RemoteRig where I can search for errors ?

Thank you

yo3irm

  • Jr. Member
  • **
  • Posts: 50
    • View Profile
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #13 on: 2016-01-11, 19:20:30 »
Reset RRC Control to factory default but no joy, same behavior, N1MM doesn't work correctly, same Too many bytes received error

Jan (Microbit)

  • Software Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 1796
    • View Profile
    • Email
Re: RRC Winkey bug? / N1MM+ send incomplete message/callsign
« Reply #14 on: 2016-01-11, 19:59:36 »
You are truly amazing at digging deep in order to find out what is going on with N1MM+(it's + I assume?) and the RRC! Thank you!  :)

Just before I left work today I had a similar system like yours up and running, and guess what, it seemed to work! There were some initial issues when N1MM+ did not send anything it at all, but I suspect it was a case of me not knowing enough about how N1MM+ works... There is at least one difference to your set-up, I used 19200 baud to communicate with the radio.

Tomorrow I will make sure it's still working ok and if your system still does not work we will have to figure out what else to do. One thing would be for you to connect an RS232 cable to the control RRC's COM1 and use a serial terminal program set at 38400,8,N,1 with the right kind of debug printouts enabled, like menu "d" followed by "3" + "w".
Always include type of hard/software and version when asking for support.