Some observations and needed walk throughs (for me anyway) for the next firmware release/how to use video/manual:
How do I program the macros and use the offsets? (since it appears I cannot program them through a text file as of now). Identified Here
Is there a way to observe the current feed rate, not just a percentage? Can there be?
When I start up the machine, I can’t set a work zero. I have to home the machine first. This could be problematic if I have to pause a carve overnight or finish one path and need to shut it down to leave. Normally I just return to zero and leave it. That does not appear to be the case here… Unless I’m missing something.
Potentially… create a quick set button that allows me to return to the last set work zero with date/time stamp? Just make sure there’s a safety prompt… because I know I’d mess that up quick.
Is there a way to dial in the machine; X and Y? For instance, I carved a 3” square and circle, yet they both came out at 2.97” and 2.98”. It would be handy if there were settings within the controller that I could really dial these in on…
Has there been any other reports of the controller going black for a few seconds during a carve, then back on? I planed my spoil board and it did this a few times. When it said “Program Complete",” I was unable to click the OK button, and had to restart the whole controller.
I hope this helps the folks at Onefinity & Redline, as well as others! This thing is a huge step up from universal gcode sender off a surface pro.
Any gcode file on the controller can be assigned as a macro. You can assign them using the “Edit” button on the macro tab. The offsets can be viewed on the OFFSETS tab on the MAIN screen. You can edit the offsets directly in the table and click on the offset name (i.e. G55 to load them immediately). Setting the WPOS or zeroing the WPOS on the MAIN screen should also update the current WCS values.
The controller will remember the last WCS offsets and should automatically restore them after homing. This should allow you to continue from where you left off.
The motor resolution is adjustable in the CONFIG menu, but it should be accurate if you use the defaults for your machine. The inaccuracy could be mechanically related (i.e. backlash, loose hardware, etc). I will let the OneFinity team comment further.
We have seen this happen in cases of extreme static discharge. I will let the Redline team comment further. Are you using a vacuum or dust collection system?
RTCNC, Thanks for the pointers! Definitely going to have to play with those recommendations to see if I’m able to do all those. This is the first time I’ve had an actual controller. Is there any reading material or videos that are planned for release sometime soon?
I think I figured out the offest. I just have to type in G54 X0 Y0 Z0 to move it back to that original work zero. I’m guessing won’t return on it’s own?
I have a dust collection system nearby, and attached via the SuckIt dust shoe. Is there a specific way I should be grounding it to avoid this issue?
Yes. We are working on the manual for the RTCNC controller right now. It will be available first on our website and then the plan is to integrate it into the software.
OneFinity and Redline will likely produce videos as well.
These buttons will give you the option to automatically move to the machine position (MPOS) origin or the work position origin (WPOS). You can use the WPOS origin to move instead of having to type in movement commands manually.
Absolutely. Let me check with Redline and OneFinity to see if they have specific recommendations. Otherwise, I can provide some guidance. Back to you shortly.
Any update? With these machines now in the wild and getting setup it is a problem that is looking for a solution (mine is to disconnect the ShopVac from the Suckit dust boot when using MDF as that’s when my Redline controller dies).
