Thread: Finding Distance From Driver Station
View Single Post
  #3   Spotlight this post!  
Unread 26-05-2010, 16:40
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
  
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,710
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Finding Distance From Driver Station
I don't follow what useful data you are looking to collect.

Are you looking for the latency of the robot's wireless bridge to FMS Access Point to derive the robot's distance from the AP?
Sounds like a step towards Zigbee triangulation...

All the rest of the communications are over a wired network with near-identical lengths of Ethernet cable, regardless of the Driver Station physical location. They'll all be at identical (wired) distance from the field Access Point, so I don't see that data as being useful.
It seems like any single ping (FMS or DS) would produce the same information, i.e. distance to AP or maybe length of the field Ethernet cables, speed of the network switches, frequency of collisions if you stretch it...
Assuming network collisions and retransmitted TCP/IP packets don't mess up your timings entirely...
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle
Last edited by Mark McLeod : 26-05-2010 at 17:08.