Talon SRX Firmware 2.0 Problem Encountered

[sraque]

Are you using the standard Talon VI's or your custom ones? I know you had a folder of your own custom VI's in the code release.

[ozrien]

Hey All,
Bringing this thread to a close: root-cause is the LabVIEW team project had forked implementations of some Talon-centric VIs, but not all. The VIs were forked for performance reasons. So updating to 2016 meant the application used some old (forked) VIs and some new VIs, effectively breaking Talon-use.

I generally recommend to teams to always use the stock Talon VIs - BUT, if you REALLY need to make changes to be successful, you should kit all related VIs so future RIO updates don't lead to a mixed bag of things.

[pribusin]

Originally Posted by ozrien

Hey All,
Bringing this thread to a close: root-cause is the LabVIEW team project had forked implementations of some Talon-centric VIs, but not all. The VIs were forked for performance reasons. So updating to 2016 meant the application used some old (forked) VIs and some new VIs, effectively breaking Talon-use.

What do you mean by 'forked VIs'? I'm not familiar with that term.

[Arhowk]

Originally Posted by pribusin

What do you mean by 'forked VIs'? I'm not familiar with that term.

It meant that OP copied over the source code of the can talon.vi and edited It.