voxelab-64 / aquila_x2 Goto Github PK

Printer is heating the extruder and bed, but not starting a print (after 30 min. waiting).

PETG, Extruder 240; Bed 70;

TEST_2.zip

Eclipse 2021-12 I have the following errors when compiling ...
Description Resource Path Location Type
fatal error: core_cm4.h: No such file or directory hc32f46x.h /Sources/main/hdsc32core/common line 232 C/C++ Problem
Invalid arguments '
Candidates are:
void loop()
' main.cpp /Sources/main line 58 Semantic Error
Invalid arguments '
Candidates are:
void setup()
' main.cpp /Sources/main line 56 Semantic Error
make: *** [main/hdsc32core/common/subdir.mk:34: main/hdsc32core/common/system_hc32f46x.o] Error 1 Sources C/C++ Problem

The file core_cm4.h is listed in the project under the Include folder. I tried resolve any unresolved includes but that did not help.

Error when compiling with Bltouch.
.. \ Sources \ Marlin \ src \ HAL \ STM32F1 \ Servo.cpp: 37
missing pwm.h

In FW v5.1.8 the runout sensor is not working as intended when using Octoprint 1.7.3.
Sending M412 to the printer, via Octoprint terminal, yeilds this response.
"Send: M412
Recv: echo:Unknown command: "M412"
Recv: ok P15 B3"

I proprose a change on line 1238, to allow for HOST_ACTION_COMMANDS
From
#define FILAMENT_RUNOUT_SCRIPT "M600"
To
#define FILAMENT_RUNOUT_SCRIPT "M412 H"

And also change
//#define HOST_PROMPT_SUPPORT
to
#define HOST_PROMPT_SUPPORT

These two changes should enable filament runout support in octoprint and make use of custom GCODE scripts for handling runout situations e.g change extruder temp, move gantry to a safe position, resume etc.

Octoprint states that printer reports "G2/G3 bad parameters". This seemingly happens at random since the last five attempts have failed at different layer heights regardless if gcode contains any g2 or g3 moves. I've tried with and without arc welder plugin enabled.

100mm_i-type_40x40-Body_v3_with_arc_weld.zip