Here is April 11th:
April 11th does not work.
Okay, here is another April11th release, I called it Apr_11b, or refer to the commit hash e9f483b4:
Apr_11b (e9f483b4) works.
Just out of curiosity, I have this topic marked as “Watched” and I have the preference
“Email me when I am quoted, replied to, my @username is mentioned, or when there is new activity in my watched categories, tags or topics” set to “always”
but I’m not getting any emails when you update this topic (which should be new activity). Any thoughts on why this doesn’t work?
We are getting close! Here is another firmware to test:
I’ve noticed other issues with the forums, such as an error when uploading files, which no longer works. I’ve sent and e-mail to @jcustenborder which was managing the site to see if he can help.
April 11th C is working.
Okay, let’s give this one a try.
April 11th D (8c0ae93d) is working.
Okay, April 11e. This last one should allow me to identify the exact commit that causes the problem:
April 11th E fails. Let me know the commit and what the plan is. Do we (you) need to open an issue against Marlin to get it fixed in the current repository?
Great! I was already reviewing the two commits and this confirms my hypothesis. Take a look at this commit and the note I left for Scott Lahteine
Is it worthwhile to do a build with the debugging stuff turned on? I’m not sure where the debugging output goes.
Looks to me like that is the cause of the failure. I’ll be available to test the fix once you figure it out.
Thanks for the effort to find the problem.
The debugging goes to serial port. May be useful for certain things, but when we know a commit introduced a bug, a binary search like we did is usually the best approach.
I have one final test. This is essentially DO release 62 with the patch to the problem applied. This will test whether the fix holds on more recent versions of Marlin.
Do you want to try the binary search approach with the issue of the Archim noisy steppers? Just comment on that thread with the two closest DO releases where it works and where it does not work.
Probably should ping @gregket1 as he is the guinea pig with the Archim controller.
TEST_FINAL works:
Changing monitoring state from "Offline" to "Opening serial connection"
Connecting to port /dev/ttyACM0, baudrate 250000
Changing monitoring state from "Opening serial connection" to "Connecting"
Connected to: Serial<id=0x6a4c66f0, open=True>(port='/dev/ttyACM0', baudrate=250000, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0*125
Send: N0 M110 N0*125
Recv: start
Recv: Marlin bugfix-2.1.x
Send: N0 M110 N0*125
Recv: echo: Last Updated: 2023-08-14 | Author: (Drunken Octopus Marlin)
Recv: echo: Compiled: Sep 4 2023
Recv: echo: Free Memory: 1905 PlannerBufferBytes: 1360
Recv: echo:DIGIPOTS Loading
Recv: echo:DIGIPOTS Loaded
Recv: echo:DIGIPOTS Loading
Recv: echo:DIGIPOTS Loaded
Recv: echo:V88 stored settings retrieved (615 bytes; crc 29079)
Recv: //action:notification Stored settings retrieved
Recv: //action:prompt_end
Recv: echo:SD card ok
Recv: ok N0 P15 B4
Changing monitoring state from "Connecting" to "Operational"
Send: N0 M110 N0*125
Recv: ok N0 P15 B4
Send: N1 M115*39
Recv: FIRMWARE_NAME:Marlin bugfix-2.1.x (Sep 4 2023 10:41:45) SOURCE_CODE_URL:https://github.com/marciot/drunken-octopus-marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:TAZ 6 EXTRUDER_COUNT:1 UUID:845f003c-aebd-4e53-a6b9-7d0984fde609
---------------------------------------------------------------------------
Your printer's firmware is a development build of Marlin (build date
20230904). It might be more unstable than a release version and should be
kept up-to-date.
Learn more at https://faq.octoprint.org/warning-firmware-development
---------------------------------------------------------------------------
Recv: Cap:SERIAL_XON_XOFF:0
Recv: Cap:BINARY_FILE_TRANSFER:0
Recv: Cap:EEPROM:1
Recv: Cap:VOLUMETRIC:0
Recv: Cap:AUTOREPORT_POS:0
Recv: Cap:AUTOREPORT_TEMP:1
Recv: Cap:PROGRESS:0
Recv: Cap:PRINT_JOB:1
Recv: Cap:AUTOLEVEL:1
Recv: Cap:RUNOUT:1
Recv: Cap:Z_PROBE:1
Recv: Cap:LEVELING_DATA:1
Recv: Cap:BUILD_PERCENT:1
Recv: Cap:SOFTWARE_POWER:0
Recv: Cap:TOGGLE_LIGHTS:0
Recv: Cap:CASE_LIGHT_BRIGHTNESS:0
Recv: Cap:EMERGENCY_PARSER:1
Recv: Cap:HOST_ACTION_COMMANDS:1
Recv: Cap:PROMPT_SUPPORT:1
Recv: Cap:SDCARD:1
Recv: Cap:MULTI_VOLUME:0
Recv: Cap:REPEAT:0
Recv: Cap:SD_WRITE:1
Recv: Cap:AUTOREPORT_SD_STATUS:0
Recv: Cap:LONG_FILENAME:0
Recv: Cap:LFN_WRITE:0
Recv: Cap:CUSTOM_FIRMWARE_UPLOAD:0
Recv: Cap:EXTENDED_M20:0
Recv: Cap:THERMAL_PROTECTION:1
Recv: Cap:MOTION_MODES:0
Recv: Cap:ARCS:1
Recv: Cap:BABYSTEPPING:1
Recv: Cap:EP_BABYSTEP:0
Recv: Cap:CHAMBER_TEMPERATURE:0
Recv: Cap:COOLER_TEMPERATURE:0
Recv: Cap:MEATPACK:0
Recv: Cap:CONFIG_EXPORT:0
Recv: ok N1 P15 B4
Send: M851 Z0.27
Recv: ok P15 B4
Send: M500
Recv: echo:Settings Stored (615 bytes; crc 11598)
Recv: //action:notification Settings Stored
Recv: ok P15 B4
Send: M155 S5
Recv: ok P15 B4
Send: M876 P1
Recv: ok P15 B4
Send: M20
Recv: Begin file list
Recv: TEMPTEST.GCO 95
Recv: CURATA~1.GCO 2178
Recv: End file list
Recv: ok P15 B4
Recv: T:25.00 /0.00 B:23.67 /0.00 @:0 B@:0
Recv: T:25.00 /0.00 B:23.56 /0.00 @:0 B@:0
Recv: T:25.13 /0.00 B:23.60 /0.00 @:0 B@:0
Recv: T:25.13 /0.00 B:23.74 /0.00 @:0 B@:0
Recv: T:24.97 /0.00 B:23.53 /0.00 @:0 B@:0
Recv: T:25.09 /0.00 B:23.74 /0.00 @:0 B@:0
Recv: T:24.94 /0.00 B:23.49 /0.00 @:0 B@:0
Recv: T:25.00 /0.00 B:23.56 /0.00 @:0 B@:0
Recv: T:24.88 /0.00 B:23.49 /0.00 @:0 B@:0
Send: G28
Recv: T:24.91 /0.00 B:23.53 /0.00 @:0 B@:0
Recv: echo:busy: processing
Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: T:25.00 /0.00 B:23.91 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: T:24.84 /0.00 B:23.49 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: T:24.94 /0.00 B:23.53 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: X:-19.00 Y:258.00 Z:16.00 E:0.00 Count X:-1900 Y:25800 Z:0
Recv: ok P13 B4
Send: M113 S2
Recv: ok P13 B4
Recv: T:24.94 /0.00 B:23.49 /0.00 @:0 B@:0
Recv: T:24.94 /0.00 B:23.60 /0.00 @:0 B@:0
Recv: T:25.06 /0.00 B:23.74 /0.00 @:0 B@:0
Send: G29 V4
Recv: G29 Auto Bed Leveling
Recv: Probing mesh point 1/4.
Recv: T:24.94 /0.00 B:23.49 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: T:24.94 /0.00 B:23.74 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: T:24.91 /0.00 B:23.46 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: Bed X: -10.00 Y: -9.00 Z: 2.30
Recv: Probing mesh point 2/4.
Recv: T:24.88 /0.00 B:23.53 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: T:25.00 /0.00 B:23.74 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: T:24.91 /0.00 B:23.49 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: Bed X: 289.40 Y: -9.00 Z: 2.18
Recv: Probing mesh point 3/4.
Recv: echo:busy: processing
Recv: T:24.91 /0.00 B:23.46 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: T:24.94 /0.00 B:23.56 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: T:25.03 /0.00 B:23.60 /0.00 @:0 B@:0
Recv: Bed X: 289.40 Y: 292.50 Z: 2.09
Recv: Probing mesh point 4/4.
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: T:25.00 /0.00 B:23.70 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: T:24.91 /0.00 B:23.60 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: Bed X: -10.00 Y: 292.50 Z: 2.04
Recv: Bilinear Leveling Grid:
Recv: 0 1
Recv: 0 +2.299 +2.184
Recv: 1 +2.041 +2.094
Recv:
Recv: X:-10.00 Y:292.50 Z:3.72 E:0.00 Count X:-1000 Y:29250 Z:8000
Recv: //action:prompt_end
Recv: ok P15 B4
Recv: T:24.94 /0.00 B:23.53 /0.00 @:0 B@:0
Recv: T:25.00 /0.00 B:23.77 /0.00 @:0 B@:0
Good point. I got confused about who reported what, lol.