[Bug]: Doesn't work with Snapmaker 2.0 A350 about octoprint-eeprom-marlin

[cp2004]

The problem here is that the firmware has messed with the format of the response.

A typical M503 response looks like this:

Recv: echo:  G21    ; Units in mm (mm)
Recv: echo:  M149 C ; Units in Celsius
Recv:
Recv: echo:; Filament settings: Disabled
Recv: echo:  M200 S0 D1.7500
Recv: echo:; Steps per unit:
Recv: echo: M92 X200.0000 Y200.0000 Z400.0000 E415.0000
Recv: echo:; Maximum feedrates (units/s):
Recv: echo:  M203 X400.0000 Y400.0000 Z8.0000 E50.0000
Recv: echo:; Maximum Acceleration (units/s2):
Recv: echo:  M201 X2000.0000 Y2000.0000 Z100.0000 E10000.0000
Recv: echo:; Acceleration (units/s2): P<print_accel> R<retract_accel> T<travel_accel>
Recv: echo:  M204 P800.0000 R10000.0000 T2000.0000
Recv: echo:; Advanced: B<min_segment_time_us> S<min_feedrate> T<min_travel_feedrate> X<max_x_jerk> Y<max_y_jerk> Z<max_z_jerk> E<max_e_jerk>
Recv: echo:  M205 B20000.0000 S0.0000 T0.0000 X8.0000 Y8.0000 Z0.3000 E5.0000
Recv: echo:; Home offset:
Recv: echo:  M206 X0.0000 Y0.0000 Z0.0000
Recv: echo:; Unified Bed Leveling:
Recv: echo:  M420 S1 Z10.0000
Recv:
Recv: Unified Bed Leveling System v1.01 active
Recv:
Recv: echo:; Active Mesh Slot: 0
Recv: echo:; EEPROM can hold 3 meshes.
Recv:
Recv: echo:; Material heatup parameters:
Recv: echo:  M145 S0 H190.0000 B60.0000 F0
Recv: echo:  M145 S1 H210.0000 B70.0000 F0
Recv: echo:; PID settings:
Recv: echo:  M301 P19.0986 I1.3998 D65.1453
Recv: echo:  M304 P46.3000 I9.0700 D157.5700
Recv: echo:; Z-Probe Offset (mm):
Recv: echo:  M851 X-29.0000 Y1.0000 Z-1.9250
Recv: echo:; Stepper driver current:
Recv: echo:  M906 X1200 Y1200 Z400
Recv: echo:  M906 I1 Z400
Recv: echo:  M906 T0 E900
Recv:
Recv: echo:; Driver stepping mode:
Recv: echo:  M569 S1 X Y Z
Recv: echo:  M569 S1 I1 Z
Recv: echo:; Linear Advance:
Recv: echo:  M900 K0.0400
Recv: echo:; Filament load/unload lengths:
Recv: echo:  M603 L25.0000 U75.0000
Recv: echo:; Filament runout sensor:
Recv: echo:  M412 S0
Recv: ok P63 B31

The key difference is the missing echo: on your response. This is present in the mainline Marlin firmware, and I am hesitant to add support for other forks because it will get messy. You should probably ask the maintainers of the firmware you have mentioned not to mess with the gcode's output.

[cp2004]

@DavidKuhn136 did the above comment clear things up for you?

[cp2004]

I am considering this issue solved - if you have more questions please ask.