|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Any ideas on a new computer for our driver station?
The computer is a quad-core amd a8 processor running at about 1.9-2 GHz with 6 GBs of ram.
|
|
#2
|
|||
|
|||
|
Re: Any ideas on a new computer for our driver station?
The DS "lockup" is generally caused by firewall such as McAfee shutting down mDNS to such a degree that the DS event loop is not running very often.
I'm not sure of the surgical way to modify McAfee to fix this, but turning it off fixed the laptop that I saw it on immediately. Greg McKaskle |
|
#3
|
||||
|
||||
|
Re: Any ideas on a new computer for our driver station?
Quote:
If your laptop has an RS232 port and you have a digital storage scope, download RTS_toggle and put a scope on the RS232 RTS pin. You'll see what's going on. Otherwise, download and run Win32 Process Scheduling demo, and it will display info in a command window. |
|
#4
|
|||
|
|||
|
Re: Any ideas on a new computer for our driver station?
To elaborate on this a bit.
The DS has many parallel loops running communicating to different field, robot, and PC elements. When mDNS was added, it was put into the timeout case of the primary UI loop. If it doesn't return for many seconds, the UI processing of clicks and such will be delayed. The other loops that communicate to the robot are still running on schedule. Soon the mDNS will also be in its own little cage, I mean loop, and if it misbehaves it will be reported on and will not interfere with the other stuff that needs to be done. I don't personally own McAfee, but wonder if there is a newer version that doesn't freak out when we ask robots to identify themselves via mDNS. Greg McKaskle |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|