|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
Talon SRX Labview Coding
We are a rookie team and don't know much about coding but we have set up 4 Talon SRX motor controllers on our robot and all are wired correctly using the CAN and daisy chaining them. I believe the error is in the code, we referred to the software manual to make this and we are getting various errors. Initially we have 2 motors on each side of our drive train so we are going to use the "slave method" for the second motor on each side. Once enabled we have two motor controllers LEDs light up solid orange and the other two alternate orange. In the manual it says there is damaged hardware but i think this is improbable. here is the code and the drive station error
https://www.dropbox.com/s/s1mz0oq0py...81%29.png?dl=0 https://www.dropbox.com/s/ek5xmqjr88...82%29.png?dl=0 |
|
#2
|
||||
|
||||
|
Re: Talon SRX Labview Coding
First of all, You are opening your motor controllers in Teleop, which constantly designates the motor controller positions every 10 ms, instead of in begin, where it is only designated once. I would recommend moving the code where you opened the Talon SRX's to begin, so that way you are designating the robot's software location only once.
What's currently happening is that your master motors are opening, but your slave motors do not know that they are slaved, and therefore aren't opening. Solid orange states that the motors are being designated in teleop, while flashing states that they are undesignated in code. Once they are all solid orange, you have opened all motors in code. |
|
#3
|
||||
|
||||
|
Re: Talon SRX Labview Coding
Quote:
Last edited by Coach Seb : 30-01-2016 at 10:23. |
|
#4
|
||||
|
||||
|
Re: Talon SRX Labview Coding
Have you addressed the Talon SRX's in the NI MAX web address? If not, you need to open a web browser with microsoft silverlight and type in your Robo-Rio's IP, and then select the Talons and set their locations.
|
|
#5
|
|||||
|
|||||
|
Re: Talon SRX Labview Coding
Any particular reason that you aren't starting with the default project?
It does everything you need except you have to change "Open 2 motors" to "Open 4 Motors" in Begin.vi |
|
#6
|
||||
|
||||
|
Re: Talon SRX Labview Coding
Do you mean make them have individual IDs because I have done that?
|
|
#7
|
||||
|
||||
|
Re: Talon SRX Labview Coding
Quote:
Section 16.3 in the Talon SRX Software Reference Manual has a suggestion for why your Talon is blinking orange instead of solid-orange. Instructions for assigning device IDs and firmware-updating (must do both) are in Section 2 of the Talon SRX Software Reference Manual. Ids must be unique (Section 2.2). Also there are FRC examples here... https://github.com/CrossTheRoadElec |
|
#8
|
||||
|
||||
|
Re: Talon SRX Labview Coding
yeah but we have a CAN network not PWM, how would you change that?
|
|
#9
|
||||
|
||||
|
Re: Talon SRX Labview Coding
Quote:
So in the roboRIO web-based config, there are a total of four Talons with IDS 1,2,3,4 then? |
|
#10
|
||||
|
||||
|
Re: Talon SRX Labview Coding
Quote:
|
|
#11
|
||||
|
||||
|
Re: Talon SRX Labview Coding
Works for me - I posted a quick example as a sanity check (I used slightly different IDs).
https://github.com/CrossTheRoadElec/...ollowerExample |
|
#12
|
||||
|
||||
|
Re: Talon SRX Labview Coding
Quote:
|
|
#13
|
||||
|
||||
|
Re: Talon SRX Labview Coding
The LabVIEW_CANTalonFollowerExample folder contains a complete LV project. The sibling folders contain other LV, Java, and C++ projects, they are not involved.
You should consider trying this proven example (after adjusting the IDs), if the issue goes away then better study the differences. if the issue is still present, then you've ruled out software. |
|
#14
|
||||
|
||||
|
Re: Talon SRX Labview Coding
Quote:
|
|
#15
|
||||
|
||||
|
Re: Talon SRX Labview Coding
It sounds there is something in your LV app that is referencing PWM. Maybe the default ArcadeDrive control is still referenced somewhere. Or some test code somewhere. This is why I suggested using the known-working-example first to determine the root-cause of the first issue you mentioned. It sounds like there are multiple problems.
If you post a screenshot, that might help determine what the PWM error is about. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|