[FRC Blog] Control System Update

[virtuald]

Originally Posted by Caleb Sykes

No, let's not do that. Leave the developers free to provide support for whichever languages they want, and leave the teams free to utilize whichever language they want.

I don't mind at all if teams use unique languages like Python, but if they start taking away resources from me because Python is not supported by many FRC Suppliers, then we have a problem.

Python isn't officially supported, so I doubt they would require a supplier to support Python. If they were to make such a requirement, it would probably only affect the officially supported languages: C++, Java, and LabVIEW.

It seems like such a requirement wouldn't be necessary -- there are a significant portion of teams using each language, so not supporting one of them would be leaving money on the table.

[adciv]

I think it depends on the component. It's not be a big deal for sensors. But for anything FIRST limits such as motor controllers...well, if CTRE didn't support one language for their Talons SRX, any team that typically uses it would be at a distinct disadvantage.

[Caleb Sykes]

Originally Posted by virtuald

Python isn't officially supported, so I doubt they would require a supplier to support Python. If they were to make such a requirement, it would probably only affect the officially supported languages: C++, Java, and LabVIEW.

I understand that, my point is that I think it is really cool that different teams use different languages, just like teams build their robots out of different materials. As a corollary, I've seen some really cool robots that are made nearly completely out of wood. If a team wants to make their robot out of wood, that is just fine, but they shouldn't try to mandate that no one use aluminum.

We program in Java, if I see a cool sensor out there that is only supported by Python, my first thought should either be:
Is it worth it to switch our programming language to Python in order to use this sensor?
Or
Can we somehow get this sensor to work with our existing programming language?
Not
Can we somehow ban this sensor so that no other team can use it?

[adciv]

Just a thought, but we have a Linux OS on the roboRIO which we have root access to. We can use this to our mutual advantage. POSIX interprocess communication from a sensor plug-in to C++/Java/LabView?

[scca229]

Originally Posted by adciv

located at about the middle of the field where the FTA is usually sitting.

Mostly correct on the rest of it (the driver stations plug into the SCC at each end of the field, which then carries it to the FMS), but....you've actually seen an FTA sitting!?!?! I'm going to have to stop listening to my step-count on my Band 2 At the AZ State Champs event this past weekend, 27900 steps on Friday Setup day, 25000 steps on Saturday event and tear-down day. I think my rear end hits a chair 2 or 3 times a day once I'm at the venue and one of those might be lunch if I'm lucky (mostly because I don't want to stiffen up and not be able to move again).

[adciv]

Ok ok, FTA is standing, kneeling, and troubleshooting the FMS, bending over it with the precision adjustment tool trying to get it working again. Although I have seen FTAs sitting for long periods of time. Typically when in discussion with HQ about why the #$^@#($ field is acting up again.