My Flex6500 has been running now for about 5 days. IE since its last fresh restart. I knew I was going to Denver for a day or so and I purposefully quit SSDR on my desktop next to the radio.
Before I left I ran SSDR from my laptop and there was the radio. I connected and listened for a bit then quit SSDR, packed up and left.
Last night I connected with my VPN and SSDR did not show my radio. I tried a few times but it didn't find it. So I remote desktop to my desktop, same thing. So clearly my 6500 is offline but I have no idea why.
Obviously not a huge program as I'll look at it when I get back. But what do you remote pros do? Do you have tools to reset the radio? I seem to remember in the documentation there is some input to the back of the radio to do power on.
Anyway I think it would be a wonderful thing is some of you guys that remote all the time would write up a quick list of the tools you guys use to keep things running when you are remote.
Today I had a new issue. The Flex showed up on the SSDR connect screen but I could not get it connect. It would timeout and give me a message to try to restart the radio.
I also notice some audio receive and transmit drop outs from time to time. Sometime it work without issues and sometime not.
Maybe some of the more experienced VPN user can provide some troubleshooting hints?
Regards, John K3MA
You need to be able to remotely reboot your computer, radio and power supplies
I use 3 WEMO remote switches to restart 110V to each device
If you search this community you will find lots of details on Remoting.
In fact, Remoting right now from my iPad.
i do have the same problem with my 6500 in my local network.the 6500 is not found regulary after one and max 5days.i had to switch down for a moment the pws of the 6500 and to restart.i am using win 7.i do have this problem up from the beginning 3 month agao.i have asked flex comp what to do.they did not know
vy 73 per dk7lj
As I sit here reading this string, I too cannot log into the remote 6500 radio. Is this a global issue??? Now it has dropped out a few times over the last few months, but never was able to point out the cause. Now in Team Viewer to check things out, and all of the auxiliary equipment is up and running from the remote computer, so this means that there was no power outage during the night. Hmmmm. The subnet IP to the local computer is good, and I see the IP for the 6500 is OK too. I just ran the remote computer SSDR with no connection to 6500. So there is an issue of why no connection. My camera is pointing at all of the Auxiliary equipment because those devices twinkle and have numbers that count up / down, but not pointing at 6500 for it status. Cycle power is easiest option right now. I only live a few minutes from the remote site, so a drive there is no big deal. But when the snow hits, I want to have my remote switch working!! Thanks Howard for product info.
I got back today to find my radio powered on as well. My laptop on our local LAN was not getting discovery data from the radio. I didn't think to look at the router to see if the IP was set or not.
I ended up restarting the radio.
I then opened the desktop computer to find Windows10 had done a massive update. This I knew was coming but I wished I could have removed SSDR before it happened.
So now I join the ranks of Win10 users with the DAX driver error. Yes Howard I know... I should have stayed with an earlier windows. However my desk computer was on Windows 8 which I hated. I'm considering taking it back to Win7 but I think it pretty much means a format and reload but perhaps that is worth it while I have the time off.
There are things about Win10 I do like so I wish the DAX issue would be solved as I'd rather not do the Win7 down grade and also I have a laptop on Win10 so I'd be out of sync there too.
Sigh... always something it seems.