Has anyone had any complications with the ethernet ports on the Driver Station?
I was loading code, from Labview, to the robot. The laptop was connected to the Eth 1 port and the Eth 2 port connected to the bridge.
Labview quit at around 50% and displayed an error message “Peer has disabled communications. Please retry.” (Not exact error message)
The LED on the DS next to ETH 1 went out after this point.
Further attempts to load code were met with “Can not locate the Real-Time client”, even after switching to different cables and computers.
If anyone has any experience or advice, it would be greatly appreciated.
I have no trouble updating code wirelessly. I think the setup should be (well, this is mine)
(Driver Station ∞ Router) & (Your Laptop ≈ Router)] ≈ Bridge ∞ cRio ∞ Axis
∞ denotes a wired connection
≈ denotes a wireless connection
Sorry this is confusing but what I mean is hook up your driver station wired to the router and then just connect wirelessly to your router network.
I can see my cRio fine, I can access Axis pictures fine, etc.
I can help you out further with Cisco configuration if that’s where you are having problems. I’m not sure if this setup is correct for the kickoff but that’s another worry for later =]
Edit: I messed up with the Laptop => Driver’s Station so fixed.
During the beta test, our ethernet port 1 got disconnected and had to be removed, I will tell people more knowledgable of the problem about this thread.
We also did all of our uploading wirelessly soooo… I would suggest trying that… Plus you don’t have to be right next to your bot… You fan just sit accross the room at some table…(yah lazy people!) … If you do that and you still get the lost conection error just wait(if wireless)
During the beta program our ETH1 port also broke; physically fell off the board (they have fixed that problem I believe).
We ran the entire beta time running using the wireless connection and wired to the router instead of the DS. So, you can run using a single port on the DS. There maybe some debugging advantages to using the second port, but we never needed to do that.
On that note, if you really think your ETH1 has failed and updating the DS doesn’t fix it then you may want to contact FIRST for a replacement.
Our ETH2 port has failed. I contacted kwikbyte and they said to send it to them for repair and they’ll send it back. They don’t seem to send you a replacement and have you send back your broken one like some companies do, so if you send it in you’ll be without a DS.
Although we can program fine with only one port, we don’t like this single point of failure and are thinking about purchasing a second unit and sending back the one we have for repairs. Then we’ll have two, just in case.
While trying to get output from the cRIO to the laptop via the DS, Eth2 knocked out (the one that connected DS to laptop). The LED refuses to light, the port refuses to connect, so we have to wire directly from cRIO to laptop to get output but have to reconnect to DS Port 1 to operate anything. It’s getting annoying.
Is this a problem that REQUIRES you to send the DS back to KwikByte?
Plug the laptop, the DS, and the cRIO all into the router. They don’t need to be connected directly. It’s an IP network so as long as the IPs are correct everything will work fine.
… If you do that and you still get the lost conection error just wait(if wireless)