I may be about to embark on yet another Mad Science Project. Or, perhaps, just a new Wild Goose Chase. They're so hard to tell apart beforehand....
Here's the thing: I have a legacy FTC application that I'd really rather not tamper with more than I absolutely have to, and I really don't have the time to reinvent the entire thing in my own RSI. But I need to add an additional Break Condition to the FCT app -- basically, I need to be able to trigger the Break from two different inputs, rather than just the one that stock FTC allows for.
Picking through the various FTC files, it looks like the Break Condition is controller by the STOP1_RCS object in the FCTtrl_T?RCSMon.RSI file. '?' because the template files keep spawning new copies every time someone creates a new FTC app, from what I can tell. It looks simple enough to add an extra DIGIN object to OR_RCS, but...
Once my testbed comes available, I'm going to have limited time to try this out experimentally, so I'm trying to cross the potential dead ends off my checklist in advance. Has anyone ever tried modifying the FTC Template files in order to customize their FTC app beyond what the menus allow? How did it work out for you? Were you attacked by a KUKAsaurus (https://xkcd.com/292/)?