Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Jan (Microbit)

Pages: 1 [2] 3 4 ... 121
16
General discussion / Re: Virtual coms under Win 7
« on: 2016-05-26, 13:32:40 »
RTP/UDP audio status: Error (0)
UDP cmd status : Error (0)

means that neither audio, nor command data is received by the radio RRC. Since it worked from here it must have something to do with your configuration(correct ports?), your network connection, etc.

17
General discussion / Re: Virtual coms under Win 7
« on: 2016-05-26, 11:39:09 »
It works from here using HRD. What do you see for RRC statuses when attempting to connect/start HRD? ->

Connection status XXX
SIP status XXX
Last SIP error XXX
RTP/UDP audio status XXX
UDP cmd status XXX

?

18
General / Re: Beta versions available
« on: 2016-05-26, 10:21:58 »
Thanks for your feedback.

How the rotary wheel "feels" seems to be very much dependent on the device used. It seems Android devices have a very broad range of response time for displays for example. Some of them are fast, while others are slow. Others have a variable response time. I assume you are using the wheel so that when you start rotating it you have the finger on the wheel and while rotating moving your finger in a bigger circle outside the wheel?

19
General discussion / Re: Virtual coms under Win 7
« on: 2016-05-25, 17:18:38 »
Hmm.. Could you email or pm me connection info for the radio RRC so I can try to connect from here?

20
General discussion / Re: Virtual coms under Win 7
« on: 2016-05-25, 13:42:48 »
Seems OK. And correct baud rate too?

21
General discussion / Re: Virtual coms under Win 7
« on: 2016-05-25, 13:29:08 »
A common problem is to not use the correct "RRC COMx" in RRC-Micro matching the radio RRC's serial port configuration. Are you sure you have configured that part correct?

22
General discussion / Re: ftsprapi.dll error in Win7Pro
« on: 2016-05-24, 22:02:13 »
No problem! Glad that you are up and running!  ;D

23
General discussion / Re: ftsprapi.dll error in Win7Pro
« on: 2016-05-24, 16:41:06 »
Aha, the RRC is using its COM2 for the radio communication. Then you need to use the "RRC COM2" serial port, "Mode 4" in RRC-Micro, not "RRC COM0". Assign "RRC COM2" to one of the three Microbit Virtual Com ports you have(COM2, 3 or 4) and config PCC-2000 to use that com port.

24
General discussion / Re: ftsprapi.dll error in Win7Pro
« on: 2016-05-24, 15:59:58 »
Not using any resources is probably not a problem. You emailed Mike some screen dumps from the RRC and RRC-Micro settings before, but I did not see any "Serial Settings" screen dump from the radio RRC? That would show if the RRC-Micro configuration is matching the RRC's.

25
General discussion / Re: ftsprapi.dll error in Win7Pro
« on: 2016-05-24, 15:12:13 »
Aha, you was writing a new post while I was doing that too!

Do you see the virtual Com ports in Device Manager? (See an example in the attached picture)


26
General discussion / Re: ftsprapi.dll error in Win7Pro
« on: 2016-05-24, 15:08:00 »
Steve,

I am not following what you mean ;) You started with saying that the installation failed and now you say that it worked? So now your (new) problem is with the use of the virtual COM ports?

27
General discussion forum / Re: TS-480HX won't power up
« on: 2016-05-24, 09:48:41 »
Powering the different devices can be done in any order, but obviously when attempting to connect the radio RRC/radio must be turned on(have power).

28
General discussion / Re: ftsprapi.dll error in Win7Pro
« on: 2016-05-24, 09:44:55 »
You also could include any logs found in the My Document's sub directory "MicrobitLogs".

29
General discussion / Re: ftsprapi.dll error in Win7Pro
« on: 2016-05-24, 09:41:20 »
Hi,

It seems the virtual com port installation fails and so ftsprapi.dll is not available when the ComOn program needs it.

Which version of RRC-Micro are you trying to install? Have you tried to run the installation as "Administrator"? (Not the same as your user account belonging to the Administrator group)

There should be a log file named either "MicroComInstall32.log" or "MicroComInstall64.log" in a sub directory to the installation folder called "drivers". If so then attach it for me to see,

/Jan

30
I have found what caused the error. It was a default value for the new Keyer settings that was invalid. You should be able to get the program running using this version:

http://www.remoterig.com/firmwares/RRCMicro_1.10.1.zip

(It was the "Weight" setting on the new "Keyer" tab that has a valid minimum value of 25, but was set to 20)

Pages: 1 [2] 3 4 ... 121