…eferences. When they came out with the Rep 1 and its all-in-1 motherboard, they didn't fix up the handling of the extruder tool versioning. That left the tool version undefined and caused control panel / onboard preference items to not appear (e.g., enabling/disabling the extruder heat sink fan; set point for the extruder heatsink fan; HBP pid values; etc.
…mp revision to r33
…f lacks <offsets> and thus cannot be used with RepG 39 or earlier. No big loss since it's unlikely anyone with a Clone R1 would use RepG for a slicer anyway, let alone RepG 39. The <offsets> were only used when slicing dualstrusion models and only then by RepG 39 and earlier.
…y limited them to 0 - 127. 'Arbitrarily' in that their firmware already checked the range and limited it to 0 - 118. So, a limit in RepG was redundant and, since it didn't agree with the firmware somewhat 'arbitrary'. Now, for the Azteeg X3, the digipots have a range of 0 - 255. Thus this interest in changing the range. (Values in EEPROM are stored in a byte and thus 0 - 255 is now the full range possible.) Sailfish when built for a given set of electronics will appropriately limit the ranges to that applicable to the electronics at hand. It has always done that and will continue to do so.
…ne type menus; one for MakerBot-brand printers and an 'other bot' menu for all others -- that dated back to when RepG had machine type definitions for a lot of other printers.
…iting the wrong action. Simplified the error messages to all be identical: truncated file error.
…elp and enabling display of byte offsets. Disabling byte offset display will then aid in testing comparison of framed vs. unframed data generated by gpx.
…bidden; given a cookie to use; and then just getting forbidden again
…d for cloudflare; possibly used by cloudflare for avoiding ddos attacks.
…p chokes and dies when it sees a machine name of length 16 bytes. Spec actually allowed a name to be 16 bytes long with no NUL terminator. A NUL terminator was only needed if the length was less than 16 bytes. As of MakerBot Desktop, they changed (broke) things such that if a 16 byte long string with no NUL is encountered, then Desktop cannot connect to the bot over USB.
…call the line numbers 'command numbers'; output byte offsets; regularize the output style (sometimes colons were used as delimiters, sometimes parens, sometimes commas, etc)
…n ToM home axes calibration
…); remove ancient slic3r distribution but leave support in place