|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Control System Issues
Quote:
I am curious about what situations they failed in not to mention where they are placed on the robot. |
|
#2
|
|||
|
|||
|
Re: Control System Issues
The last reported and confirmed DS memory leak was from 2010 beta. The changes between the '13 versions only have to do with info being logged to the DS files.
What dashboard was being used? Could that have contributed? Without more information, my suspicion is that the OS itself wanted a reboot. I occasionally awaken a laptop from sleep and see that all sorts of stuff is bogging it down. Do you have any idea what was running? What OS version? My recommendation would be to reboot it each morning of a competition. I don't know that I see a need to do it before each match. I'm sure there are teams that reboot it once or twice before each match. Whatever works for your team. Greg McKaskle |
|
#3
|
|||||
|
|||||
|
Re: Control System Issues
We boot our Driver Station netbook at the beginning of a competition and shut it down after the end.
![]() |
|
#4
|
||||
|
||||
|
Re: Control System Issues
DS:
We were using the regular dashboard. It is a Win7 machine. We use it as programming laptop and our driver station. It is a pretty beefy machine with a SSD harddrive. Windriver and the DS were probably the only thing running at the time, but I can't say for sure. We did have interesting issue that day. We use C++. The students tried reverting the code in wind river. The deleted the project, but they didn't delete the files from the file system. They then imported old code with the same project name. Who knows what happens as far as the class files on the system and how it produces the .out file from that point. It may have been possible to trigger from that, but I am skeptical. I am going to try to recreate this scenario sometime and see if we can recreate the issue. Sidecar: Our sidecar is in the middle of our robot surrounded by lots of other robot stuff. If I remember at Alamo, I will try to take a picture and post. @Greg, yes it is like shooting in the dark with issues like this. Hopefully this will bring some awareness and others can take down more details if it happens to them. |
|
#5
|
||||
|
||||
|
Re: Control System Issues
We lost our KoP sidecar at Lake Superior and had to replace it with one from a previous year. The 5V LED went out, and we lost all PWM signal. I figured some metal shavings got in there and shorted something.
But if you want to talk about confusing control system issues... Last night we were at our build space to practice driving on last year's robot. While the driver was practicing, the programming team was working on getting another robot up and running again so we can have some more interaction in the practice. Well, they accidentally downloaded (over wireless!) to the wrong robot! We spent at least half an hour trying to figure out why it wasn't driving anymore (rebooting both the robot and driver station multiple times, opening up the robot to look at the electronics, etc) before we discovered why. |
|
#6
|
||||
|
||||
|
Re: Control System Issues
Quote:
However, 2 sidecars failing in one regional seems to be excessive if that's the cause unless it's mounted right next to or directly under a moving part, or you did a lot of drilling and filing without a vacuum nearby. |
|
#7
|
||||
|
||||
|
Re: Control System Issues
Of course there was some drilling being done and maybe that was the cause. We were very careful to cover up and use a vacuum though. This is the first sidecar we have ever lost.
|
|
#8
|
|||||
|
|||||
|
Re: Control System Issues
Quote:
|
|
#9
|
||||
|
||||
|
Re: Control System Issues
Thanks for the offer, I just hope we don't have to take you up on it.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|