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

Pages: [1] 2
1
General discussion forum / Random connection problem
« on: 2018-05-20, 22:25:08 »
I have had flawless performance from my remote K3 twin setup for two years. Virtually never a connection issue.
Over the last week I have started having a new problem connecting to the remote.
This is a RANDOM issue...sometime I can connect with no issue, other times I cannot establish a SIP connection. Yesterday I was able to connect on and off repeatedly with NO problem. Now, again today I am having the issue again.
I am almost certain this is NOT a problem with the RCC units. I expect it may be an issue with my WISP at the remote.

I am asking here to see if anyone else has had a similar problem and discovered a solution. Here is the detail:

1.) When I power up the K3 mini at the control, the remote radio will not respond and I get the dreaded "two-tone" connection error sound. (I have remote cameras at the station and can see that the radio is not coming on).
2.) I know it is not an IP problem because I can access the RCC 1258 Radio GUI, and have rebooted the RCC remote unit, but this does not seem to help.
3.) I reboot the control RCC and this doesn't seem to help.
4.) I have tried to connect using the rcc mini dongle using my laptop, and cannot connect that way either. Probably not a problem at the control end.
5.) Occasionally when I do a reboot of the remote WISP router (I can access the remote station LAN via Teamviewer) it will help and I can then connect, but not always. It seems sometimes after a few reboots it will work. It seems like randomly the SIP connection has a problem initializing.

I have talked to my WISP tech people and they assure me there have been no hardware or network changes in the last few days. It seems like it might have something to do with my LAN or WISP router, but NOTHING HAS CHANGED in the last week since this problem started. I have experience flawless connection for 2 years.

Anyone else experienced this?

de steve ve6wz.




2
General discussion forum / Audio Hiss Solved
« on: 2017-10-23, 17:34:00 »
Using both K3 twin and Yaesu FTdx-9000d radios with RCC1258 units for a long time I have had a bad audio hiss even with the volume turned to zero.

Solution: Do NOT use audio CODEC with 12 bit. I now use audio quality 2 which is 16 bit.
I found that even higher quality settings using 12 bit will cause audio hiss. 16 bit all ok.

I'm posting this in case others have the same problem.

de steve ve6wz.

3
Update...I have been on holidays in VK now for 3 weeks and have had great success controlling my remote in VE6.

I am only using the 1274B dongle connected to a very cheap Dell notebook.
So far all QSO's on CW, and I am CW keying the radio using my L32 logbook program AT THE REMOTE by logging into the remote via TeamViewer and using keyboard cw. I have not even tried using paddles to send CW from my laptop, because I am doubtful it would be reliable.

Numerous DX qso's on 80m and 160m including working some DX-peditions using split. Many QSOs with VK stations....very strange to be working a VK station in Melbourne, using my home station in VE6 western Canada, while I am sitting on the coach in my hotel room in Melbourne!

Also, while in Tasmania (VK7) I did not have Wifi, but had complete and solid control of the remote while tethering my 4G data plan from my cell phone to the laptop. 100% solid audio and control.

I thought others would like to know that the significant latency introduced from VK to NA does not present a problem with the remoteRig setup. Quite amazing indeed.

de steve ve6wz.

4
Feature Requests / Re: Increase Audio Quality choice
« on: 2016-12-01, 17:29:39 »
Mitch,

Are you sure you can change the quality on the RCC-Micro dongle??
On the RCC micro settings page I see no option to change Audio quality. Only Jitter size, Jitter Delay and Buffer size.
I thought I had read that the default is set for Quality 0, Alaw 8kHz on the Micro dongle.

5
Feature Requests / Increase Audio Quality choice
« on: 2016-11-30, 18:39:25 »
Is there a possibility to be able to choose Quality 7 linear? or quality 4, or even 2??

Using the existing low audio quality Codec default on the Micro makes weak signal CW difficult. This especially a big problem with high noise.

thanks,  de steve ve6wz

6
General discussion forum / Re: CW sending screwing up!
« on: 2016-11-08, 18:57:21 »
I was having a similar problem with random gibberish on my CW, and like you LfDelay and Key delay helped little.

When I changed my RX Jitter delay and Buffer size in Advanced settings it fixed my problems.
I use Buffer 12, and Jitter 10.
My latency is only about 32 ms which ins't bad, but increasing these values cured my problem.

I would like to here what others suggest.

de steve ve6wz

7
General discussion forum / Lf Delay Key delay defined
« on: 2016-11-03, 17:06:23 »
Can someone please explain the exact difference between Lf Delay and Key Delay in the Control Keyer settings? One is buffer and one is TX power inhibit after PTT?

I have read the manual and tried to search the forum but I am still not sure what the difference is.

I have my K3 twin set-up and working well for CW being sent from N1MM and the paddle using the Winkeyer emulator on Com3 (extra).

The concern is at the remote site I have numerous switching relays that need to engage for TX antenna switching changes from RX to TX. I need to prevent hot-switching. To accommodate this I have already set a tx INHIBIT time in the K3 radio to account for this. Now adding more "delay from PTT to power applied" will be cumulative could be a problem?

I also notice that in N1MM under the Settings tab for my Winker Com port that there is a "PTT Delay" setting which appears to be another "power inhibit sequencer".
Is this N1MM PTT delay "in addition" to the RCC keyer delay, or is it independent of the RCC unit?

Hopefully this question is clear. I want to fully understand what my sequencing delays end up being out at my remote radio from the time PTT arrives and power starts being generated.

de steve ve6wz

8
General discussion forum / Re: FTdx-9000d TRX manager
« on: 2016-11-02, 16:09:43 »
Thanks Mike.

Yes I see the connect and disconnect button on the status page.
For now, I will use that. It is easy to use.

I will contact TRX-Manger support and see if there is a setting in their program to tell RCC-control unit to start a connection.
Is there no one else out there using TRX-manager with remote rig not had this problem??
Maybe just me??
Or is this just the way it is done when using PC control with remote rig?

de steve ve6wz.

9
General discussion forum / Re: FTdx-9000d TRX manager
« on: 2016-11-02, 02:41:26 »
I have established connection.

The RCC manual under stetting for the Yaesu General (FT-2000) does NOT say to have AUTO connect on, but that is the only way for me to establish connection to the radio RCC.
With Auto connect ON I have full control of the FTdx-9000 with TRX-manager program, audio, Mic and power on-off.

However....

Now, if I go back to my Laptop and try to access the Yaesu with the RCC-Micro dongle, it says "Busy". It seems like even with the radio turned off, there remains a SIP connection to the control RCC box. Perhaps with Auto Connect on, the session remains open between the two RCC units, but this is the only way I can get communication.

This does not happen with my K3s twin set up. I can access the remote from either the K3/0 or the Micro Dongle.

The manual says to have Auto connect off, but that does not work for me.

Does this provide any clues about my problem???? Perhaps the TRX manager program does not tell the RCC control box to open a connection to the radio??

Steve

10
General discussion forum / Re: FTdx-9000d TRX manager
« on: 2016-11-01, 16:48:18 »
Actually it is set for: Mode 4 Kenwood, Yaesu, Elekraft
I don't see a setting for FT-2000 ?
Both RCC units have been updated with latest firmware 2.91
All CMD, Audio and SIP ports checked and agree with Radio RCC.

11
General discussion forum / Re: FTdx-9000d TRX manager
« on: 2016-11-01, 16:34:22 »
Yes. This is what I used. "Yaesu General (Ft-2000)"

12
General discussion forum / FTdx-9000d TRX manager
« on: 2016-11-01, 16:28:08 »
I have been unable to get my FTdx-9000d to connect using the RCC-1258 boxes using TRX manager.

Here is the background:

1. I have the K3s twin setup working perfectly at my remote station 100km north of me (CQWW ssb contest was a flawless operation)
2. Recently I purchased from a local Ham another RCC-1258MkII set of boxes so that I can set-up a second Yaseu station at my remote. This will NOT be the twin set-up, I plan to use PC control with TRX manager at the control end.
3. All strapping and jumpers were check and set for the Yaesu FTdx-9000 settings.
4. The RCC radio unit was connected to the radio, and over my LAN using the RemoteRig MICO DONGLE on my laptop, I established connection and complete control of the FTdx-9000 using TRX Manager. So...all working ok.
5. Now I want to use the RCC control box instead of the Micro Dongle. LAN IP address of the radio RCC was input to the Control RCC as SIP addy. Full LAN access to the control unit WEB page.  I cannot connect to the radio using TRX manager on my other PC.
6. At my first attempt to connect, TRX manager locked up, but I discovered this is only when RTS/CTS is enabled in TRX manager (handshaking problem?) With rts/cts off, manager dose not lock up, but no comm to radio.
7. To confirm COM port on PC is good, I connected the radio direct to the PC and TRX manager has complete control of radio even with rst enabled...power on off all ok.

I have purposely NOT indicated my Serial port settings on the Control RCC since I have been working on this for 3 days I think I have tried every possible combination of settings for com 1 or 2.
I think I can conclude the radio RCC is configured correctly since all works perfect with the rcc dongle.
Surely I have not set things up right for PC control.

Any help?

de Steve ve6wz.

13
Great news. Thanks for that info Andrew.
I will definitely be taking a laptop and the RCC-Micro now.

steve

14
Thank you Palle !!

Very good information which I will use on my travelling.
Maybe we will QSO VE to OZ when I am in VK !

73, steve, ve6wz

15
This problem has been resolved here.

 ***Make sure you have DMZ disabled***

I spoke directly with Mike and he indicated that this problem appears to be random, not common and not hardware related.
He indicated that I should try and disable port forwarding to the RCC web port because perhaps there is "junk" trying to access the RCC unit from the the internet...maybe via bots etc.

-I disabled port forwarding on my router for the Web access, but continued to have the same problem.
-I then realized I had activated DMZ for the the RCC device (ip .170). Perhaps opening up the RCC unit to web access was allowing "junk" to mess-up the unit?
-I disabled DMZ in the router (You don't need it activated when you are port forwarding the correct ports) and now the RCC remote unit had been stable for the last 5 days with solid access.

good luck....I hope this helps others with this issue.

de steve ve6wz.

Pages: [1] 2