I received my 6300 today and connected it directly to my computer (no switch). I could not get SmartSDR to recognize the radio. I finally connected it to a switch which is connected via WLAN to my LAN router/switch in another room. That connection worked fine. I called FLEX and they said the direct connection should work just fine and sure enough the direct connection started working as we spoke on the telephone. (Magic voice I guess). About an hour later the connection died again and I had to go back to using the switch. I saw where someone else had the same problem and it was listed as resolved with no more comments allowed. I wonder what their resolution was?
Posted 5 years ago
Tim - W4TME, Customer Experience Manager
Jay -- N0FB, Elmer
Mike, a couple ideas. Some Ethernet cards can be configured to be manually set for speed and duplex (full or half) or it can be set for auto-negotiation. Chances are, it is set for auto-negotiation and is usually the best setting for most occasions. As a test, you might try setting the Ethernet (if possible) to 100 Megabit and Full Duplex on your PC. The radio will no longer need to try to negotiate the link speed and the link may then "just become reliable".
The reason that you are not having the problem when connected to the switch, each port on the switch is doing its own negotiation with each device. It works out any differences between the connected devices internally.
(Edited)
Also check the power/performance setting to make sure that your computer isn't powering down the Ethernet hardware (and USB port, if you are using FlexControl Knob) as part of the power saving routine. Things can get wonky that way, too. This is important whether you are on a switch or not.
Lee, Elmer
Try updating the Ethernet drivers to the latest hardware specific drivers (ie not windows stock drivers). I agree setting the speed to a fixed speed is also a good idea
Good to hear from you Zeke! Hope you are well. Welcome to Flexlife
73 W9OY
Good to hear from you Zeke! Hope you are well. Welcome to Flexlife
73 W9OY
Hi Lee
I'll probably just leave things as they are (using the switch). I was thinking earlier that there might have been some negotiation problems. Shoulda called Shatner.
The only reason I wanted a direct connection was for a gigabit link which probably wouldn't make any difference and I get an internet connection with the switch.
I used to follow your blog about the 5000 and wondered what happened. I guess you got hit by lightning. The same thing happened to Gary's (W9BS) 5000. He gave up and moved to a condo in Ft. Myers. No radio no mo.
73 de Mike (Zeke)
I'll probably just leave things as they are (using the switch). I was thinking earlier that there might have been some negotiation problems. Shoulda called Shatner.
The only reason I wanted a direct connection was for a gigabit link which probably wouldn't make any difference and I get an internet connection with the switch.
I used to follow your blog about the 5000 and wondered what happened. I guess you got hit by lightning. The same thing happened to Gary's (W9BS) 5000. He gave up and moved to a condo in Ft. Myers. No radio no mo.
73 de Mike (Zeke)
Lee, Elmer
Hit by lightning..built a surgery center practice..2 kids in high school etc etc. Now slowing down a bit and having a blast with this 6300
Received my 6300 yesterday and no success connecting direct to my computer.
I have tried 2 other computers all with win7 but no luck.
I have tried 2 other computers all with win7 but no luck.
Does the 6300 need a crossover cable for a direct connect. I go through a switch all is great
Mike
Mike
(Edited)
No crossover cable needed...I have my 6300 direct with no issues.... it may take a few minutes for it to show up..Did you run the CD that came with it to make sure all the drivers for the 6300 were installed. I too am running win7 Good luck
John
John
(Edited)
Using the cable supplied and the CD supplied but dont have a lan router system to plug into.
I gave up on a direct connection and used a $15 wireless router which is "talking" to another wireless router in a different room.
Mike W9OJ
Mike W9OJ
I travel a bit and one of the reasons I bought this unit was to be able to work portable so I do not want to carry a router with me. Has anyone who has had problems with direct connections ever resolved the problem. Thanks for your comments Mike.
Tim - W4TME, Customer Experience Manager
Sid - Please open a HelpDesk support ticket if you are still having issues with communicating to the radio.
New to SDR so not sure how to open helpdesk support ticket
Tim - W4TME, Customer Experience Manager
This link will tell you how to open a HelpDesk ticket
http://helpdesk.flexradio.com/hc/en-us/articles/202118688-How-to-Submit-a-Request-for-Technical-Supp...
http://helpdesk.flexradio.com/hc/en-us/articles/202118688-How-to-Submit-a-Request-for-Technical-Supp...
Thanks Tim will check it out.
Lee, Elmer
KY6LA - Howard, Elmer
The issue is caused by the fact that somehow your radio is losing IP address and picking up a new IP on a different subnet
Best possible solution. Do not use direct connection. But rather connect your radio thru a router so that it always gets a routable IP address. This should solve your problem.
Best possible solution. Do not use direct connection. But rather connect your radio thru a router so that it always gets a routable IP address. This should solve your problem.
Is it possible to set a static ip in the radio or view it's network configuration?
KY6LA - Howard, Elmer
Not easy with a direct connection
Through a router u can use the MAC address to fix the IP.
Through a router u can use the MAC address to fix the IP.
KY6LA - Howard, Elmer
U can view the IP in SmartCAT
Windows will assign a class B IP address to the PC's NIC if there is no DHCP. How does the flex radio assign it's IP address when there is no DHCP?
Larry,
You might want to read this thread.
https://community.flexradio.com/flexradio/topics/direct_ethernet_connection_for_flex_6500
Jon...kf2e
You might want to read this thread.
https://community.flexradio.com/flexradio/topics/direct_ethernet_connection_for_flex_6500
Jon...kf2e
Lee, Elmer
If you can force the nic into the same subnet as the radio it will fix itself without dchp servers and all that. The problem is if windows doesn't know what to do it forces a 169.xxx.xxx.xxx address and if your radio is not on that subnet communications won't be estsblished. You probably want the nic on 192.168.0.x 255.255.255.x or 192.168.1.x 255.255.255.x. You can just empirically assign your nic port to a IP address in one or the other of these subnets and its likely your radio will fire up. Its triviasl to return the nic to dchp if bit doesn't work
73 W9OY
73 W9OY
My 6300 connects directly at 169.254.9.212, the wireless happens to be at 192.168.5 as assigned by the router. What I don't understand is why his radio would not be on the correct subnet assigned during initial negotiation when powered up for a direct connection. The stack works fine both on Win7 and Win8.1.
Lee, Elmer
It has to do with the way windows handles multiple NIC ip addresses in the same machine. Windows networking has always been a pita since the days of 3.1
It has been well documented in many post that going through a router is the way to connect, but people still try and go direct no matter what....
KY6LA - Howard, Elmer
The radio and laptop will be traveling and i'd like to find a solution that doesn't involve a router. I'm fine with the forums recommendation on adding a home network. If I discover a stable solution for direct connection I'll share it with you all. Cost is not an issue
(Edited)
I wish that I had a solution for you Larry, all I can tell you is that I plug the radio directly into my laptop and it works, I plug it into my desktop and it works flawlessly. Nothing special on either computer, both have functioning wireless connections that connect automatically on power up. Win 7 and Win 8.1, sorry.
Just to rub salt in the wound, I tried no WiFi, Ethernet to the radio first, radio powered up before plugging in Ethernet, and during lightening storm...could not get it to not connect. Truly plug and play.
So far enabling windows 8.1 internet connection sharing (ICS) is allowing the direct connect to work. Have been on for three hours and no lock-up of SSDR and I can see that the radio is getting an IP address from the ICS DHCP that is on the same subnet as the computer's NIC. I was also able to upgraded the radio to SSDR v1.3 using this setup. I did notice that the radio sometimes configured itself with a link local address in the 169.254/16 range and when this happened, it was also in the same subnet as the PC's port which also uses the same method to assign a link local IP in 169.254/16 (note - ICS not enabled at this point). The radio operates for a while in this configuration and then SSDR display hangs and the radio no longer appears in the radio chooser. Anyway, ICS seems like a viable solution for direct connections, YMMV. Sending my WireShark captures that contain the moment of the freeze and you can see the traffic from the radio stop.
(Edited)
Lee, Elmer
Tim - W4TME, Customer Experience Manager