Controller won't connect to Accel function

[sistamatik5583]

Perhaps like this?
(Also, thank you so much for helping out! We really appreciate it!)

[Mark McLeod]

You did it right, but it didn't do what I'd hoped for.
It turns to code, but still pulls this year's Accel Open from this year's library.

I'd suggest just removing the controller input and use the Accel Open with only the Accel Range as an input.
I can't imagine what useful purpose the controller would have served anyway.
The internal accelerometer just sends back what it senses. There's no controller input.

[sistamatik5583]

Okay, thank you so much! This was incredibly helpful!

[Greg McKaskle]

Once upon a time, the roboRIO was a cRIO. It had modules that plugged into slots that read a specific I/O type, and you could plug in multiple modules. The subVIS for Open commonly took a channel # and slot # as input parameters.

When first ported to the roboRIO, this slot # input parameter was changed to controller, to let you choose which roboRIO. The implementation was never finished and the parameter was later removed.

Greg McKaskle