Re: New Talon Speed Controller
 

I see the isochronous mode for the Motor Control Set, but nothing else.
I also see that Read Status sets a timeout of 0 for messages continually transmitted, but could also do a transaction (with 10ms timeout) if requesting something on-demand.

Everything else is still blocking (set parameters require Ack, read parameters are synchronous).

Really, CAN is designed to never care if a message is received, and to transmit everything continuously (with less important information at a slower rate). Having an Ack message makes no sense to me.

Edit: Motor Set defaults to synchronous mode, and the Isochronous input is not in the help. I'm guessing many teams still run in synchronous mode. It should default to isochronous mode, IMO.

Re: New Talon Speed Controller
 

Is it possible to revert a Talon to factory calibration?

Re: New Talon Speed Controller
 

No it is not.

Re: New Talon Speed Controller
 

Mike, could it be done with a PWM signal generator which generates a known pulse width accurate to 0.001 ms ?

Re: New Talon Speed Controller
 

Mike, our last Beta update included a new class for the Victor 888's. I haven't seen one for the Talon yet.

Is one going to be released? If not, what's the recommended class to use? We haven't had any problems using the victor class with it at all.

Re: New Talon Speed Controller
 

We're not in the beta, but I changed my plugin source to the beta channel to ensure compatibility with older code, and as per today's update:

Re: New Talon Speed Controller
 

Figures. We're now one update behind because we had our seminar and didn't want to break our code by updating a day or two before the seminar. It's probably in there.

Re: New Talon Speed Controller
 

No. Joe's questions was regarding factory calibration. These settings are what the firmware saves to flash when the Talon is first programmed. These settings are over written once the user performs a successful calibration.

A user calibration could be performed to obtain values that are are close or even the same as what's saved during initial programming. But there would be no way for the user to confirm this.

We did not feel the ability to restore factory calibration was necessary since the procedure would not be much different than performing a user calibration. And a user calibration will yield the best performance.

Re: New Talon Speed Controller
 

FRC 422 just received the first 8 of our Talons! They are far smaller than we imagined them to be.

Re: New Talon Speed Controller
 

Team 2410 put four on our mecanum demo robot and man do they drive like a beauty! Makes driving off of our app so much smoother and easier. Me gusta mucho.

Re: New Talon Speed Controller
 

Compared to what? (also, what does "off of our app" mean?)

Re: New Talon Speed Controller
 

Compared to previously having 4 victors. Off our app means we put one of the robot open shields on it and one of our programmers wrote an app too driver the demo bot off a phone with

Re: New Talon Speed Controller
 

Were you driving the Victors "off the app" too? ... so that you were comparing apples to apples?

Re: New Talon Speed Controller
 

Yeah we were driving the Victors off the app as well. The Talons just seemed more responsive. I will admit it was not a blind study so maybe its just the hyper behind the Talons that makes it seem so

Re: New Talon Speed Controller
 

I'm thinking it's probably the linearity of the Talons which made the difference you noticed.

But as you said, it would be most interesting to conduct a blind study.