View Single Post
  #6   Spotlight this post!  
Unread 04-02-2015, 10:37
ericomoura ericomoura is offline
Registered User
FRC #0383 (Brazilian Machine)
Team Role: Programmer
 
Join Date: Jan 2013
Rookie Year: 2012
Location: Brazil
Posts: 12
ericomoura is an unknown quantity at this point
Re: Robot traction system shutting down

Quote:
Originally Posted by Ether View Post
@ericomoura: what kind of computer are you using for the DS?


We use an Asus laptop running Windows 64-bit version.

Quote:
Originally Posted by Alan Anderson View Post
I have two questions.

1) Have you tried debugging the code to make sure that mov is what you expect when you call the MecanumDrive_Cartesian() function?

2) Why are you calling MecanumDrive_Cartesian()? You don't have a mecanum (or 45-degree omniwheel) drivebase. Since you're passing a constant 0 as the first argument, it seems to me that it would be more reasonable to call an ArcadeDrive function.
1) Yes, mov is behaving as I expected.

2) Just as I posted I realized how stupid that was and changed it to ArcadeDrive immediately. For some reason I didn't see it when I wrote this... It must've been late. Anyways, the issue is still there, no changes.


I also wanted to add that I recently tried deploying a default Arcade Drive example from the Eclipse examples and the error did still show up, which makes me think that the code might not be the only problem. Besides that, we bought an analog breakout for the Talon SRX, so we'll be using the closed-loop functions, which means a great part of that code (the hand-made P kind of thing) will go away. I'm hoping the problem is in there so it will magically vanish.
Reply With Quote