Page MenuHomeAleph Objects Inc

Make production averages for backlash and offsets the firmware defaults for TAZ Pro
Closed, ResolvedPublic

Description

This is a request to make the averages of the backlash and offsets the firmware defaults. The build log for Pro is here: http://devel.alephobjects.com/ao/manufacturing/documents/master_build_log_TAZ_PRO.ods

Event Timeline

kent created this task.Jul 2 2019, 2:26 PM
kent triaged this task as Normal priority.
kent created this object with edit policy "LulzBot Hardware Products (Project)".
kent claimed this task.Tue, Jul 23, 2:32 PM
kent added a comment.Mon, Jul 29, 9:41 AM

Here are the averages for all the printers on .135 fw

Z offsetX nozzle offsetY nozzle offsetZ nozzle offsetX backlashY backlashZ backlash
-1.102297297297344.57567567567570.09575675675680.0050.25209459459460.18337837837840.0751351351351

This is for Quiver, correct? Do we wish to leave all other printers with a default of zero?

kent added a comment.Mon, Jul 29, 10:15 AM

@marcio yes, this request is specific to quiver. For now, I recommend leaving all other machines' default values as-is.

kent renamed this task from Make production averages for backlash and offsets the firmware defaults to Make production averages for backlash and offsets the firmware defaults for quiver.Mon, Jul 29, 10:16 AM
karrad renamed this task from Make production averages for backlash and offsets the firmware defaults for quiver to Make production averages for backlash and offsets the firmware defaults for TAZ Pro.Mon, Jul 29, 10:20 AM
Steven reassigned this task from Steven to marcio.Tue, Jul 30, 9:49 AM

@marcio when this is in a build ready to test can you please assign this back to @kent and note which version to test?

@Steven: The latest version, .148, will have the fix. However, if we do not want upstream changes in the next release, then we will need a new release-candidate branch for the .144 release.

@Steven: You may want to review this document with the draft FW release process https://code.alephobjects.com/diffusion/MARLIN/browse/devel/docs/lulzbot_marlin_development_process.odt

If we had been following this process, there would already have been a release candidate branch for 144 which we could have applied this one fix to. We can create it retroactively if you don't want to jump to .148

@Steven We have removed the "update EEPROM" checkbox by default for redgum and quiver. This should help prevent customers from clearing calibration data, and would not make this as pressing of a release as current changes.

We will defer to R&D about what firmware to test and implement, we have a CO staged for this change here: https://code.alephobjects.com/T9157

marcio closed this task as Resolved.Tue, Aug 20, 2:06 PM