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.


Topics - VE6WZ

Pages: [1]
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
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

4
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

5
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.

6
My wife and I will be spending 2 months in Australia this winter and I am wondering if its worth bringing the RCC-Micro and other peripherals to connect to my remote?
Any one have experience with working a NA remote site from VK?
I have done a few random ping tests to Australia servers and I'm getting some pretty bad latency numbers...often 200 ms plus.
I'd rather not take all my hardware if its likely to be un-workable.

de steve ve6wz

7
I did a search and I could not find any info on this but I'm sure its been discussed before.

Can I have two independent RCC-1258 units sharing the same remote IP addy?
My plan is two have a choice of using my K-3 twin set-up, or a Yaesu radio with its own RCC unit.

I am assuming that perhaps it is simply a matter of configuring the ports properly? Maybe use SIP port 13003, RTP/UDP 13004 and CDP 13005???

Before I commit to this idea I want to be sure I'm not missing something that is problematic.

de Steve ve6wz

8
General discussion / Can't control radio with TRX
« on: 2016-09-18, 00:57:02 »
Any help out there?

K-3s twin setup at rural remote location 100km from home.
Remote works perfect with rrc-1258 units and K3s mini.
Also have full remote access via Teamviewer to remote shack.

Just order and rc'd Micro-1274B dongle direct from Microbit
Have loaded the RRC-micro 1.10 beta client
Have configured the client and I can connect to remote with good rx audio from radio via the computer speakers.
Use Com2 virtual port
Using TRX manager have selected K3s radio and com 2 port, but can not get radio control...will not update.
Have also tried HRD and no communication on com 2.
I'm sure this is operator error....any ideas.

Using W10 machine.

de steve ve6wz

Pages: [1]