Fri, Aug 9
Wed, Aug 7
@hanna , Merged to master.
Tue, Aug 6
Updated, tested, and ready to be merged!
@Steven we have a few
My apologies, this ticket should have been merged to T8849. We are going to need a new production tag unfortunately.
@DaniAO Are you aware of any other Mini 2 changes in process? ^^
@karrad yeah, we would need to make another production tag. Any other changes in process worth completing before we make the tag?
@Steven Do we need another production tag to get this on download? Right now we have 22.214.171.124 in the 2.0.6 tag:
Mon, Aug 5
The drawing has been updated for AS-CB0075 but has not been signed off on yet.
@kent let's discuss this tomorrow when you are here and brainstorm the best scenario for moving forward.
Fri, Aug 2
Thu, Aug 1
who is they?
Let me know if you have any other questions about this request.
I think they are asking about the files in the assembly parts directory mini-hibiscus/production_parts/assemblies/assembly_parts. They are requesting drawings for these:
@Steven Thank you, I will get this tied to the CO and close it out.
@marcio Was there anything changed in marlin that could affect how the printer performs its autocal or utilizes its z offset between the 2 editions.
@kent assigning back to you until there is further clarification as there is not enough information here that is actionable.
@kent @sherylb the fasteners we purchase are made to a standard. Why not confirm the supplier is meeting a specific standard and then QC is done to those standards? I agree with @samantha and see no reason we should be generating drawings for every fastener we use. These are not custom parts and so we would need to accept whatever standard the supplier is already using.
@kent what assemblies are you requesting drawings for? every sub assembly? complete machines/tool heads?
@kent I don't see making drawings for every commodity screw and washer to be a very reasonable request. I think instead we could capture all of the information for that inside of a BOM in an assembly drawing such as the one requested in T9251, or through another means of declaring the standards that apply instead of making custom drawings to global standards for 32 commodity parts.
Wed, Jul 31
I have a machine here that I can not get within spec on fw version 126.96.36.199 but was able to get it in spec with fw version 188.8.131.52. The other interesting thing was when I flashed back and fourth between the 2 firmware versions I noticed that I needed a different z offset or else my print would come out squished.
@kent I don't think that would have had any sort of effect on how we built it if the drawing itself wasn't incorrect.
@draubach @guadalupe we made an update to the drawing for the mini case fan assembly AS-CB0075. There was a conflicting rev letter in the file name, I don't know if that was causing any confusion or not for you all. It's just a clarity change, not an actual change to the design or the parts.
There is no other error shown and it will update except that I seem to need to change the z offset anyways because later firmware seem to be handling something differently.
@oliver Just to test, will you flash a Mini 2 with 184.108.40.206 and see if there is an error thrown?
@oliver When the customer connects to Cura LE, it will prompt them that they have the wrong printer connected and ask them to update firmware. When updating, it also prompts them to write down Z offset and E steps to re-enter at a later date.
@karrad I think this is still an issue for Cura. Since we are flashing with an older firmware that no longer shares the name with the toolhead, it is going to wipe away any calibration data that we have done and affect the customers first print. Even if we get the firmware updated in the CO, there is still going to be a lot of Mini 2s out there that will have an older firmware that registers as a improper toolhead.
@paulette There is currently a change order opened currently for changing the x-belt to be adjustable here, T3450.
@oliver The current version of Cura LE flashes 220.127.116.11, and will explain why you are getting the error. This not only checks tool head names, but firmware versions. Once the CO is complete you will stop getting this error (I have also updated the CO with the proper firmware version)
@oliver What version of the firmware are you currently flashing?