Mark Walker

I think the kicker is to make sure that MakerBot's firmware also does & 0x01 on the one byte operand and/or uses any non-zero value as "true".

Just checked. At least for Mightyboard's it looks ok: https://github.com/makerbot/MightyBoardFirmware/blob/207c6db181565dacba22a0d4cc271dbe71cfcd7a/firmware/src/MightyBoard/Motherboard/Command.cc#L420

Seems like we might want to just pass through the value as the byte instead of normalizing to 0-100. Mainly so that M106 S255 still works the same as before...

@header, @footer and @body were designed to ignore @macros in the header and footer for things like pauseatz since people often have a few Z moves in their header. As...

The time estimate includes a random guess about heatup. Your first request is just to remove that. The other implied request is to make the estimate more accurate and the...

If you're looking to modify source, you're looking for "accumulated.time"

I haven't ever tried this with a Thing-o-matic. It may be that GPX is generating new x3g opcodes that are incompatible with the s3g protocol that the TOM used. You...

I'm not sure what changed, but it looks like the Json parser returns something different when sent an 'undefined'. In any case, I think I may have this fixed in...

I'm guessing that the octoprint user doesn't have permission to write to ini location. (you meant r1d, right?). Perhaps you have a broken r1d.ini left around from before? Perhaps there...

I can't reproduce this issue. Are you installing onto a raspberry pi configured with the octopi image? If so, which version of that image did you use? I just tried...