+] Is it possible to obtain the WPILIB source for C++?
+] On another note, I have this motor connected through a Jaguar.
I’ve been able to control this motor using the ArcadeDrive function and a Joystick.
I want to control this motor independently, so I decided to use the Jaguar class instead and use the Jaguar::Set() function and Joystick::GetY() to control it,
as in
But it appears that it doesn’t do anything, and I’m pretty sure I’m specifying the correct ports.
Obviously I would have been able to resolve this problem if i had the WPILib source and checked out the ArcadeDrive function…
The WPILib source is distributed along with Windriver updates. For our team’s use on Linux, we host source updates on our own server here for convenience. This is revision 2993 released on January 8, and may become out of date, and is not intended to replace the Windriver updates.
Simple troubleshooting because A) I don’t have access to a robot to see if we are having the same issue and B) I’m pretty sure I ran into this last year, but I don’t remember how or even if we fixed it.
Joystick Port is determined by the driver station. Make sure the joystick is setup to be in the port you specify. This is done on the setup tab of the driver station.
I believe you can write the value of the axis to a float and then use it on a later line, and see if that does anything.
Anyone hear if there will be an update? The source files seem to be out of date. I was trying to demo windriver debugging and we were trying to debug into the joystick class, and the line numbers that we were getting to using single step, corresponded to comments.
This generally indicates that there is a mismatch between the source version that the debugger sees and the version that was used to compile the library.
Since I have not seen it elsewhere - here is how to use the wpilib source in wind river.
The source is stored in a zip file in the windriver folder. To allow workbench to see the source, so you can use the debugger and step into wpilib code, you need to put a copy of the wpilib source folder into your workspace.
The source in the zip file is in a folder called wpilib
I extracted the source folder and moved it into my workspace folder. I’m just using the default windriver workspace folder.
c:\WindRiver\workspace\WPILib\
When it is in your workspace, the debugger can find the source so you can see it when you debug into wpilib code. This is very helpful when you want to understand how wpilib does the stuff it does.