Would anyone happen to know how to create a long loop of a gcode file to play out? Looking to test out our new pivot joints by running it at high speed (non printing moves) doing a circle in mid air for 24hrs.
Any ideas how to go about this?
Are G2 and G3 moves an option?
Copy/paste seems to be the obvious solution.
N100 G0 Z10 (Safe height)
N110 G0 X0 Y50
N120 G02 X50 Y0 R50
N130 G02 X0 Y-50 R50
N140 G02 X-50 Y0 R50
N140 G02 X0 Y50 R50
N200 GOTO N100
Not sure if your printer understands the GOTO statement. Might need a WHILE with an infinite condition (WHILE 1=1 or something).
I always just copy/paste my burn-in code. Takes about a minute of 1-2-4-8-16 etc copying to get a day’s worth of motions. No firmware gcode parsing feature dependency that way.
To get the circle to start with, just pull the skirt gcode for a cylindrical print.
If copy/pasting, how would we know how long it will run for? I guess we can copy/paste a bit and then time it. Any other ideas?
@Alex_Wiebe I’m not familiar with GOTO command or N command for that matter. Does not seem like standard printing commands.
Reversing cycle count is probably more important than runtime, no?
To get a count, either use the document line count, or put a gcode comment at the start of each circle motion you copy/paste, and then use a text editor to find how many times that comment appears.
Or you could write or hack a gcode tool that will do this. People with self aligning bushings will be pleased.
Do a short copy paste chain of let’s say 100 circles. Time it. Now you know the duration for 100. Some simple math would tell you the number of instances needed for 24hrs.
Of course the larger the sample size of the initial run, the higher the accuracy you’re going to get to exactly 24 hours
Oh, a thought… make your gcode like a million cycles and then power the printer through a lamp timer so the power shuts off when the time is up 
@Ryan_Carlyle why do you have to go and find the simple solution
You know, a power timer isn’t such a bad idea. In smoothieware you can save files as on_boot.gcode so it runs right on power up. A physical power timer would make sure it keeps running.