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 - Gerryb

Pages: [1] 2
1
General discussion forum / Re: Latency and Starlink
« on: 2024-08-19, 10:40:52 »
Thanks… and for looking back to 2015!  that long ago.

I will experiment when next back at the remote location that has starlink

To get past fibre, 4g 5g and Starlink’ CGNAT, instead of  paying for a fixed IPv4 I use reverse tunnels. IPV6 rollout allows direct connection with pinholes so my use of reverse tunnels is reducing. iPv6 to IPv4 I use SOCAT. All these solutions need a raspberry Pi which in someways defeats the object of RRC 1258, but I find RRC but better that any software to control the radio

Starlink has IPV6, and as yet

2
General discussion forum / Latency and Starlink
« on: 2024-08-17, 19:29:28 »
I would like fire my twin on a remote location with my Yaesu 857D.   I know long latency times stop this working using the older control of the 857.    The latency I get with Starlink is 40ms, but they say can reach 100.  Once I attempted to reach australia. before Starlink and and that did not work with a ping of 300ms!   What is the max ping time that it could tolerate?

Gerry

3
How to use Remoterig and get CAT control for an FT857D when one has a tuner attached.... my simplified question.

It seems I will have to make up at least once serial cable to attach tuner to RPC and then one the 857D to the RPC.  One can be a CT-62.

I was trying to use the feature of CAT over the MIC port using the adapter at the home control end.   I had missed out the menu 57 on the 857 which shows NOR and CAT as microphone options which needed setting to CAT. CAT meaning in addition to MIC, but still could not get it to work even if I turned off the other menu tuner options at set the machine to CAT.   I suspect I am trying to be too clever as running this with a reverse VPN over 4g and introducing too much latency.

Gerry


4
Problem:  Remote Working for Digital Modes using FT857D

I have managed a remote setup using RRC-1258 MkII twin via reverse tunnels on RaspberryPi 4g dongle and 4g Network, and all is working with detached head at home control site.

I need a tuner so it is attached currently to the 857D’s CAT port on remote site.

But I need CAT controls as VOX does not seem to trigger when attempting FT8 tones in USB mode.  (FT8 works if I press PTT every 15 seconds!!)

It would nice to control the rig via such WSJTX (later I will tunnel the digital DATA plug via the Raspberry pi)

CAT controls can be via the microphone plug ("Undocumented feature").   I have the Windcamp T8x7 adapter at the control home site, which has a CAT port from the Microphone connection and can plug into the PC but that fails, I assumed because I cannot provide 64,000 baud the Microphone interface needs.  WSJTX and windows nor Linux do not offer the 64,000 baud rate which I assume is a fixed rate when using the microphone interface.    Or is that when using CAT for a tuner there is no CAT via the microphone port?

I am in a complete muddle with this as well, as how to use the Com1 2 ports to achieve this with tuner in place:

"You can use the RRC as a CAT kind of server. If you connect com2 via a CT-62 to the 897 then you can connect the antenna tuner to COM1 and set com1 to mode 7. The messages from the tuner will then be forwarded to/from com 1 together with the message which goes from Control-RRC to com2"     
"Connect antenna tuner to COM1" seems to require a mini din to MALE Serial plug which is not the current CT-62 cable (female). 
I am not keen on soldering up a mini din... Or is it simpler than this?    Am I making a mountain out of a molehill?   There seems to be too many ways to kill a CAT

Gerry G3WIP





5
Sorted much to my embarrassment.  Wrong protocol used in Radio setup.

6
RRC-1258 MKII   I had has a problem connecting with RRC-micro so brought  the remote radio home and connected on the LAN  to test.

The 857 connects on the LAN from the "home"1258, the detached  857 front panel lights up, all digits and frequency correct. Alas, this only last three seconds and the "remote" 875 clicks off.  I can turn back on again and it occurs again.

So far:

1 The 857D works as normal with panel attached.
2  All plugs sockets OK
3  Separate powers supply for RPCs changed anyway in case a power supply problem.
4  Reset RPCs and even put firmware back update.

 857 connects  but after 3 seconds clicks off.

What am I missing? its there some silly setting I am missing or not got incorrect?

Gerry



7
General discussion / Re: Cannot get Com ports installed
« on: 2019-04-15, 21:48:35 »
 :)
I am not sure how this was resolved.   I new root hub update popped up which promptly I installed.  But before I started again I killed VMWARE other services that might have been blocking it, and not relying on the config programme to close them in time.   The ports are now there. 

 I will repeat on other machines. 

Not quite finished as I think I have a new problem with the remote RPC

8
General discussion / Re: Install does not setup com port
« on: 2019-04-07, 13:10:59 »
What was the solution!!
I have posted on RRC-client about this issue

9
General discussion / Re: Cannot get Com ports installed
« on: 2019-04-07, 13:07:16 »
Windows 10.    Ports not being installed.

Mikael kindly pointed me to http://www.remoterig.com/wp/?page_id=3200


But running that utility did not show any issues, other than the new com ports are not being installed in the first place by the RRCclient installation programme. This seems to be a new windows 10 issue   
Anyone one lses sufferering this?

Any solutions out there?


10
General discussion / Re: Cannot get Com ports installed
« on: 2019-04-06, 14:30:22 »
I have just attempted to install RRC micro on another modern laptop.  HP this time, and again it will not install the COM Ports.

My main machine has the ports, but I remember that I had inalled RPC micro some time back and as was OK, so I wonder if a new Window 10 update "feature" is now blcoking this.  A cmd black box flashes but no prompt for coms port installation come up, asking to install them.

Help!

Gerry

11
General discussion / Cannot get Com ports installed
« on: 2019-04-06, 01:09:19 »
My lenova Yoga 2 Pro Windows 10
Just got my RRc micro dongle.

Running RRC micro install I do see any propmts about com ports from Futura.  A black box flashes by, and no com ports are installed.  I have tried turning of my virus protection, turned off UAC, run as admin and still no joy.   The machine had a GPS on Com12  Serial over blootooth on ports Coms 7 and 8

On another machine I get further.  The com ports install OK but I am still not communicating with my 875D with HamRadio Delux  Cannot get frequency and fails no matter which ports and speeds I chose!  SIP is OK and green line.

RPC 1258 controlled can connect OK and is working fine with the Yaesu front panel.




12
Configuration, RRC 1258 / Nano App FT897 etc
« on: 2019-02-23, 14:09:52 »
I log in to Check if any change to this statememt
"The Yaesu App is only tested with FT-950 but it only uses the generic CAT commands so it will probably work with most modern Yaesu radios like FT-2000, FT-5000, FT-9000 and later models. It will not work with the FT-1000x and FT-8×7 models which uses the old version of Yaesu protocol, We plan to add support for them also later"   

The later bit seems a while now.
I remain ever hopeful...

13
Configuration, RRC 1258 / RRC NANO YAESU 875D 897
« on: 2017-05-24, 16:33:58 »
Only when I RTFM did I twig that that the Android App does not (yet) support the old CAT commands so cannot work with these "older" popular rigs.  I know you might have enough to do but that would be appreciated!!

Gerry  G3WIP/VK0GB

14
Thanks.  Yes aware of that issue, but using 2 different power supplies, and the 1258 supply is 1.5A
Tried 2 others.. To be double certain tried 13v batteries on each one.   I usually blame power supplies or connections...

15
Radcom RSGB magazine this month, i.e, June 2015, has my article which I wrote a over year ago about using RemoteRig_RRC1258-MkII twin in Antarctica as VK0GB.

Alas here in QLD Australia, tropical climate may have got to the same setup I used in the cold.   

I was back in the UK in April and tried to use the system from there to hear in Oz, but it turns out that the latency is just too long for front panel connection.   Now back in  Australia, testing it locally on the LAN and I find the 857D head does the same as it did when attempting to connect from the UK,  Flash, beep and nothing more.

All seems well, green steady lights and the units seem to see each other, but the radio end cannot hold the connection when I turn on from remote.  The remote end  857's head flashes and beeps but no connection.   The 857 clicks three times and stops.   I did factory resets, replaced firmware, changed power supplies.  No difference.   Any ideas?   It was working well on the LAN before I left for the UK.   The 857d connected with its head alone works fine.

Gerry
G3WIP/VK4BGL

Pages: [1] 2