[BUG] X2 and X3 stops extruding on first layer on Jan build both are N32 boards

[motleycrue76]

Did you test the latest release build?

Yes, and the problem still exists.

Bug Description

hi, the speed seems ok, but it stops extruding on the first layer and keeps going. the extruder motor stops completely, but continues to try and print. help

Printer Model

Voxelab Aquila

Model Type

X2 X3

Your Mainboard

Aquila N32

Other Mainboard Type

No response

Add-ons that could be involved

CR touch for the X2, Inductive for X3

ProUI-EX | Extra Features?

No (formerly NoPro)

Bed Leveling

UBL - Unified Bed Leveling

Did you include your own configuration files?

• A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

No response

[motleycrue76]

im somewhat new to all this, but with "Alex's" firmare on my X2 i have 4000 hours of prints all worked just fine. i tried to upgrade to to the Jan 2025 firmware and it all went wrong. i dont know how to edit or compile firmware myself, so your help would be great. the X2 has the added CR touch, while the X3 is all stock out of the box (inductive sensor)

[classicrocker883]

I suggest try using PROUI_EX version. otherwise, an older release should work like 2.1.3f-10 (October).

If it is the non-ProUI-EX that is the issue that will help narrow it down and I'll look into it.

[motleycrue76]

Hi, thanks for responding.   I failed to mention the machine is an X3 Plus.  300x300x300.  I did flash with the Oct. PROUI_EX version and the same happened.  Prints the perimeter fine, when it goes to fill in, it stops extruding but keeps going as if it was. Sent from AOL on Android On Sat, Feb 8, 2025 at 6:28 PM, ***@***.***> wrote: I suggest try using PROUI_EX version. otherwise, an older release should work like 2.1.3f-10 (October). If it is the non-ProUI-EX that is the issue that will help narrow it down and I'll look into it. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[classicrocker883]

having it stop extruding after first layer is an odd issue. is there anything in your Gcode file that has M111 S8? it seems as if the printer is doing a Dry-Run mode.

search into your Gcode print file for M111, if you do see one or not add M111 S0

if you like attach/send the Gcode file you are using and I can take a quick look.

edit: also, for the Plus version that must use the ProUI_EX because you need to change the physical size of the printer through Advanced Settings

[motleycrue76]

hi, yes i did use the ProUI_EX (Oct 2024, build) and changed the bed size to X=300 and Y=300. Also set the max X an Y travel to 300 did not make a difference when i set it to do bed mesh leveling. only scanned 230x230. i flashed back to the stock firmware and printed the same file 4 times fine. the g-code(pasted below) unless theres new code in Marlin, it does not load the mesh leveling data for the bed. trying to remember think its M420 /S or something like that. i will have to add the correct code into Voxelmaker slicer. i really appreciate all your help!!!! if you need the whole file let me know.

;generated by ffslicer 1.30.3 02/08/25 01:11:49
;right_extruder_material: PETG
;layer_height: 0.2
;perimeter_shells: 2
;top_solid_layers: 5
;bottom_solid_layers: 3
;fill_density: 15%
;fill_pattern: hexagon
;base_print_speed: 70
;travel_speed: 100
;right_extruder_temperature: 240
;left_extruder_temperature: 0
;platform_temperature: 75
;right_extruder_temperature_raft0: 0
;left_extruder_temperature_raft0: 0
;right_extruder_temperature_reset:
;left_extruder_temperature_reset:
;start gcode
M140 S75 T0
M104 S240 T0
M104 S0 T1
G90
G28
G1 Z50.000 F420
G161 X Y F3300
M190 S75 T0
M109 S240 T0
M109 S0 T1
G92 E.0000
;layer_count: 32
M108 T0
G1 X122.16 Y155.25 F6000
;preExtrude:0.20
;preExtruder0
G1 Z.200 F420
G1 X122.16 Y155.25 F6000
G1 X122.16 Y35.25 E15.1666 F1200
;raft
;layer:0.31
;shell
M106 S255
G1 E10.1666 F2700
G1 Z.310 F420
G1 X130.76 Y43.85 F3000
G1 E15.1666 F2700
;extrude_ratio:1.03158
G1 X130.76 Y43.85 F3000
G1 X140.79 Y43.85 E15.6734 F1200
G1 X140.79 Y53.85 E16.1786
G1 X140.79 Y63.85 E16.6838
G1 X140.79 Y73.85 E17.1890
G1 X140.79 Y83.85 E17.6942
G1 X140.79 Y192.65 E23.1911
G1 X130.76 Y192.65 E23.6978
G1 X130.76 Y43.85 E31.2155
G1 X130.36 Y43.45 F3000
G1 X141.19 Y43.45 E31.7626 F1200
G1 X141.19 Y193.05 E39.3208
G1 X130.36 Y193.05 E39.8679
G1 X130.36 Y43.45 E47.4260
;infill
;extrude_ratio:1
G1 E42.4260 F2700
G1 X140.08 Y44.19 F3000
G1 E47.4260 F2700
;extrude_ratio:1.03158
G1 X140.08 Y44.19 F3000
G1 X140.45 Y44.56 E47.4525 F1200
G1 X140.45 Y45.12 E47.4808
G1 X139.51 Y44.19 E47.5476
G1 X138.95 Y44.19 E47.5759
G1 X140.45 Y45.69 E47.6830
G1 X140.45 Y46.26 E47.7118
G1 X138.38 Y44.19 E47.8597
G1 X137.81 Y44.19 E47.8885
G1 X140.45 Y46.82 E48.0768
G1 X140.45 Y47.39 E48.1056
G1 X137.24 Y44.19 E48.3346
G1 X136.68 Y44.19 E48.3629
G1 X140.45 Y47.96 E48.6322
G1 X140.45 Y48.53 E48.6610
G1 X136.11 Y44.19 E48.9711
G1 X135.54 Y44.19 E48.9999
G1 X140.45 Y49.09 E49.3504
G1 X140.45 Y49.66 E49.3792
G1 X134.98 Y44.19 E49.7700
G1 X134.41 Y44.19 E49.7988
G1 X140.45 Y50.23 E50.2304
G1 X140.45 Y50.79 E50.2586

[classicrocker883]

you did mention you tried the recent latest release? because someone else who uses 400x400x400 Aquila Max says they have no issue now.

ill take a look at your code and even try printing and see if I get the same issue.

[motleycrue76]

hey, i flashed it to tonite... Aquila_N32_IND_UBL-ProUI-EX-01-30.bin if that is not the correct one, please link it for me. i did take the same G-code file and put it in my X2 and it prints fine. on the X3 plus it still prints the perimeter and then stops on the infill, and at the same time i noticed the "hot end" heater shuts off. but the bed stays heating.
i did find the bed size issue, after resizing the bed, you have to go resize the mesh inset settings. i did not know that, now i do.

[motleycrue76]

ive tried a few versions, so i could not remember. none worked though, i did just notice the heater shutting off when it goes to infill tonite.

[classicrocker883]

that file should be correct one with Induction Probe.
so everything is working fine on the X2 now, but still issue with X3? could it be possible there is something with the wiring connection?

[motleycrue76]

The X2 is back on the old Alex firmware.  I tried last night flashing the X3 and it did the same as before.  I just noticed that when it's printing the perimeter and switches to do the infill on the first layer, it stops extruding and shuts the hot end heater off, but keeps trying to print.  If I then shut it off and flash it back to stock, and set it to print the same file, it prints fine.  I was just testing to make sure it wasn't something with the slicer.  I'm gunna take the cover off the motherboard and get a couple photos of it.  The X3 plus is brand new.  Wondering if they changed something on it. Sent from AOL on Android On Fri, Feb 14, 2025 at 11:07 AM, ***@***.***> wrote: that file should be correct one with Induction Probe. so everything is working fine on the X2 now, but still issue with X3? could it be possible there is something with the wiring connection? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***> classicrocker883 left a comment (classicrocker883/MRiscoCProUI#197) that file should be correct one with Induction Probe. so everything is working fine on the X2 now, but still issue with X3? could it be possible there is something with the wiring connection? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[motleycrue76]

I think I found the problem.  Running the 1.30.bin firmware as soon as it starts to print it shuts the hot end off.  If I go into the tune menu and turn the hot end right back up, it's printing fine.  Hope this helps.  Sent from AOL on Android On Fri, Feb 14, 2025 at 11:07 AM, ***@***.***> wrote: that file should be correct one with Induction Probe. so everything is working fine on the X2 now, but still issue with X3? could it be possible there is something with the wiring connection? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***> classicrocker883 left a comment (classicrocker883/MRiscoCProUI#197) that file should be correct one with Induction Probe. so everything is working fine on the X2 now, but still issue with X3? could it be possible there is something with the wiring connection? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[motleycrue76]

hey, been messing with things today. and think i nailed it down. i copied the start of the G file below. i think its a slicer issue. 3 lines down after the "start gcode" M104 S0 T1 seems to be the problem. if i edit the code and after it add "M104 S240 T0" it prints fine. was this something changed in marlin 2.0? also since ive got it mostly working, the updates even to the old "alex" firmware are amazing!! THANKYOU!!!

;generated by ffslicer 1.30.3 02/15/25 23:43:40
;right_extruder_material: PETG
;layer_height: 0.2
;perimeter_shells: 2
;top_solid_layers: 5
;bottom_solid_layers: 3
;fill_density: 15%
;fill_pattern: hexagon
;base_print_speed: 60
;travel_speed: 100
;right_extruder_temperature: 240
;left_extruder_temperature: 0
;platform_temperature: 75
;right_extruder_temperature_raft0: 0
;left_extruder_temperature_raft0: 0
;right_extruder_temperature_reset:
;left_extruder_temperature_reset:
;start gcode
M140 S75 T0
M104 S240 T0
M104 S0 T1
G90
G28
G1 Z50.000 F420
G161 X Y F3300
M190 S75 T0
M109 S240 T0
M109 S0 T1
G92 E.0000
;layer_count: 105
M108 T0
G1 X176.98 Y167.73 F6000
;preExtrude:0.20
;preExtruder0
G1 Z.200 F420
G1 X176.98 Y167.73 F6000
G1 X170.55 Y186.02 E2.4503 F1200
G1 X169.67 Y188.19 E2.7463
G1 X167.45 Y190.76 E3.1755
G1 X164.48 Y192.52 E3.6119
G1 X161.73 Y193.11 E3.9673
G1 X127.47 Y194.15 E8.2994
G1 X124.43 Y193.40 E8.6951
G1 X121.75 Y191.83 E9.0877
G1 X119.58 Y189.54 E9.4864
G1 X118.16 Y186.79 E9.8776
G1 X117.72 Y184.54 E10.1674
G1 X117.13 Y179.80 E10.7711
G1 X113.24 Y145.24 E15.1666
;raft
;layer:0.30
;shell
M106 S255
G1 E10.1666 F2700
G1 Z.300 F420
G1 X121.91 Y145.37 F3000
G1 E15.1666 F2700
;extrude_ratio:1.03158
G1 X121.91 Y145.37 F3000
G1 X122.00 Y144.73 E15.1982 F1200
G1 X122.30 Y144.09 E15.2328
G1 X122.71 Y143.61 E15.2637
G1 X123.30 Y143.22 E15.2982
G1 X123.92 Y143.03 E15.3299
G1 X124.63 Y143.02 E15.3647
G1 X125.25 Y143.19 E15.3961
G1 X125.85 Y143.56 E15.4306
G1 X126.28 Y144.03 E15.4617
G1 X126.59 Y144.67 E15.4965
G1 X126.70 Y145.30 E15.5277
G1 X126.58 Y146.36 E15.5799
G1 X127.60 Y147.53 E15.6558
G1 X128.15 Y148.15 E15.6963
G1 X129.68 Y149.82 E15.8071
G1 X131.58 Y151.74 E15.9391
G1 X131.58 Y155.95 E16.1450
G1 X131.58 Y165.95 E16.6339
G1 X131.58 Y175.95 E17.1228
G1 X131.58 Y178.66 E17.2553
G1 X131.47 Y179.45 E17.2943
G1 X131.18 Y180.16 E17.3318
G1 X130.56 Y180.96 E17.3813
G1 X130.49 Y181.56 E17.4108
G1 X130.91 Y182.43 E17.4581
G1 X131.02 Y183.06 E17.4893
G1 X130.94 Y183.76 E17.5238
G1 X130.68 Y184.36 E17.5557
G1 X130.24 Y184.90 E17.5898
G1 X129.70 Y185.28 E17.6221
G1 X129.04 Y185.50 E17.6561
G1 X128.39 Y185.52 E17.6879
G1 X127.71 Y185.35 E17.7222
G1 X127.15 Y185.03 E17.7537
G1 X126.66 Y184.51 E17.7886
G1 X126.37 Y183.94 E17.8199
G1 X126.23 Y183.25 E17.8543
G1 X126.29 Y182.60 E17.8862
G1 X126.56 Y181.92 E17.9220
G1 X126.97 Y181.26 E17.9600
G1 X126.15 Y180.28 E18.0225
G1 X125.82 Y179.58 E18.0603
G1 X125.68 Y178.83 E18.0976
G1 X125.75 Y178.06 E18.1354
G1 X126.01 Y177.34 E18.1728
G1 X126.44 Y176.71 E18.2101
G1 X127.04 Y176.21 E18.2483
G1 X127.72 Y175.89 E18.2851
G1 X128.48 Y175.75 E18.3228
G1 X129.27 Y175.81 E18.3616
G1 X130.27 Y176.08 E18.4122
G1 X130.27 Y158.54 E19.2698
G1 X130.02 Y157.64 E19.3155
G1 X129.34 Y156.92 E19.3639
G1 X128.40 Y156.58 E19.4128
G1 X127.41 Y156.71 E19.4616

[classicrocker883]

I'm unsure about Marlin Gcode T1/T0 that I can look into. however what slicer are you using? Voxelab Voxelmaker? I noticed that this slicer adds T1 or T0 into the Gcode. it is because I believe this slicer doesn't use Marlin 2.0 for Gcode, but something a bit different. I Have a Voxelab Aries and I noticed the same kind of thing where it adds T0 or T1. it is not needed for Marlin when having 1 single extruder. that's what it is trying to define in the Gcode - which extruder to use - T1 is one extruder T0 is another.

It's possible since Alex's firmware the updates have accounted for multiple extruders and thats why it would ignore T1 T0

[Mik-S-UMS]

This reminds me of a post from someone that was having problems with Voxelab CS and started to complain on Reddit. One of the things he was adamant on was the error message M104 Invalid extruder 1 showing up in the terminal and assumed this was the source of all their problems, only for the CS to say that was not the problem.

I assume this was here for those printers that have 2 extruders and makes sure the second one is turned off. Stock FW just gives that message and ignores it. I thought it was just in the test Gcode files on the SDcard but this may be generated by Voxelmaker by default. I know Cura does not do this, don't know about other slicers.

I don't know if Mriscoc (or Alex's FW) supports more than one extruder so they may just ignore the T flag for M104 and this would explain the hotend turning off.