View Single Post
  #1   Spotlight this post!  
Unread 11-02-2013, 19:14
mikets's Avatar
mikets mikets is offline
Software Engineer
FRC #0492 (Titan Robotics)
Team Role: Mentor
 
Join Date: Jan 2010
Rookie Year: 2008
Location: Bellevue, WA
Posts: 667
mikets is a glorious beacon of lightmikets is a glorious beacon of lightmikets is a glorious beacon of lightmikets is a glorious beacon of lightmikets is a glorious beacon of lightmikets is a glorious beacon of light
Re: NetConole replacement

Both netterm and netconsole use UDP. By definition, unlike TCP, UDP doesn't guarantee no packet loss. So if you overwhelm the network with packets, it is possible to lose some. It is just the nature of UDP for higher performance. Netterm allows you to switch to TCP but communication protocol must be agreed on both sides. So if you want to use TCP, both side must be using TCP. Unfortunately, the cRIO side is designed to use UDP only. So this doesn't help you. In any case, if you overwhelm the network with packets, you should reconsider how you do printf's. Printing lots of stuff in a tight robot loop is normally discouraged. This will drastically slow down your robot and may cause the "Watchdog not fed" warning so the robot may hesitate. If you want to see the value of some variables, there are many alternatives than using plain printf's in a loop. If you really want to do printf's in a loop. Do it once every 10 or 20 loops or so. You can also use the SmartDashboard to monitor variables.
EDIT: After reading your post again, you seem to have a network dropout issue. You may want to reposition the wireless router on the robot. If the network drops out intermittenly, UDP will also drop packets.
__________________

Last edited by mikets : 11-02-2013 at 19:18.
Reply With Quote