The new Redline Controller firmware 1.6.3 finally enables some important options. Among other things, it includes input signal inversion and infrastructure to support accessories—whatever that means. I haven’t tried it yet.
However, I miss the messages and subroutines that were possible with Buildbotics. tjp52, Tom, and Tgunr Dave Carlton have already pointed this out. For example, the three fields in Buildbotics settings: “on program start,” “on tool change,” “on program end”…..
I use an AutoDustBoot for my Onefinity Gen2 Redline. At least here, I have to raise the DustBoot before a ATC tool change and lower it again after the tool change. Please add support for calls, routines, and subroutines .
Yes, sure, that would work. But it’s not an elegant solution. I could integrate this into the postprocessor in the same way. That’s ungainly too.
I’m just wondering why the new Redline system, which was announced with great features, offers fewer options than the “old” BuildBotics system. There’s hope that Redline will improve with each firmware update. That’ll probably take some time.
Perhaps describing the Redline controller as having great features is correct, and different options rather than fewer than the BB might be more accurate.
It can be frustrating when the ones you really need or want are missing.
RealTimeCNC seems to be very quick to respond to user feedback, either solving issues or adding wanted features (certainly when compared to BB or Masso), so that can be viewed as a positive.
Improvements and additions may take less time than you think.
