You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where is the documentation that maps all old labview functions to the replacement VI's? The online help inside labview is still very incomplete. (when I initially added this post, I clicked on the links on the CTR site and it only brought me to the github site; since then I clicked again and it downloaded the pdf manual which is much better but still doesn't seem complete).
Also there is no table that defines what all of the internal parameters that can be read are and how each functions (from labview perspective). I just need to read the current position and velocity in native units and I cannot find any documentation that describes what parameters to read.
Is there documentation that cross references all of the old parameters in the talon to the new names and describes the function/changes? Using the Get vi, I create a constant for the parameter and its difficult to determine which ones I want to use.
I've also implemented a master/slave control where I'm using a talon master and a talon slave as shown in the software user manual. (e.g. using the set vi, selecting follower mode, and putting the master can address in the input for "output")
The invert flag on the Open vi does not seem to do anything. I had to add another invert vi to invert the motor.
When using a master/slave configuration for 2 talons, I had to add 2 invert vi's, one for the master and one for the slave. Previously the slave just followed the actual output of the master.
I also noted that the red/green lights on the talons don't seem to reflect the actual output to the motors when using the invert vi. I think these previously reflected actual polarity on the wires. They now seem to follow the software output before the invert is applied.
I don't think the rollout of all of these changes was ready for 2018 season,,, should have been delayed until 2019 when everything was complete.
The text was updated successfully, but these errors were encountered:
Where is the documentation that maps all old labview functions to the replacement VI's? The online help inside labview is still very incomplete. (when I initially added this post, I clicked on the links on the CTR site and it only brought me to the github site; since then I clicked again and it downloaded the pdf manual which is much better but still doesn't seem complete).
Also there is no table that defines what all of the internal parameters that can be read are and how each functions (from labview perspective). I just need to read the current position and velocity in native units and I cannot find any documentation that describes what parameters to read.
Is there documentation that cross references all of the old parameters in the talon to the new names and describes the function/changes? Using the Get vi, I create a constant for the parameter and its difficult to determine which ones I want to use.
I've also implemented a master/slave control where I'm using a talon master and a talon slave as shown in the software user manual. (e.g. using the set vi, selecting follower mode, and putting the master can address in the input for "output")
The invert flag on the Open vi does not seem to do anything. I had to add another invert vi to invert the motor.
When using a master/slave configuration for 2 talons, I had to add 2 invert vi's, one for the master and one for the slave. Previously the slave just followed the actual output of the master.
I also noted that the red/green lights on the talons don't seem to reflect the actual output to the motors when using the invert vi. I think these previously reflected actual polarity on the wires. They now seem to follow the software output before the invert is applied.
I don't think the rollout of all of these changes was ready for 2018 season,,, should have been delayed until 2019 when everything was complete.
The text was updated successfully, but these errors were encountered: