Accelerometer M956 failing w Sender
-
I have a working LIS3DH that appears to work just fine launching from DWC, but I can't execute from Openpnp as the sender.
sending M956 P123.0 S1000 A1 from the Openpnp GCode console results in Openpnp Console responce;> M956 P123.0 S1000 A1 Error: M956: Accelerometer not found ok
in Openpnp Log/Trace responce
2025-02-24 17:36:48.746 GcodeDriver DEBUG: [tcp://192.168.2.1:333] >> M956 P123.0 S1000 A1, 5000 2025-02-24 17:36:48.748 GcodeDriver$ReaderThread TRACE: [tcp://192.168.2.1:333] << Error: M956: Accelerometer not found 2025-02-24 17:36:48.748 GcodeDriver$ReaderThread TRACE: [tcp://192.168.2.1:333] << ok 2025-02-24 17:36:48.748 GcodeDriver TRACE: [tcp://192.168.2.1:333] confirmed M956P123S1000A1
Im not sure if this related to Openpnp to 6HC being connected via tcp/ethernet of not, but I can run same code from DWC just fine;
Thanks for any help on this!
-
@wayneosdias said in Accelerometer M956 failing w Sender:
2025-02-24 17:36:48.748 GcodeDriver TRACE: [tcp://192.168.2.1:333] confirmed M956P123S1000A1
this is not valid:
M956P123S1000A1P123 isn't a valid accelerometer address, P123.0 is
looks like the sender is changing part of the gcode command string
-
@T3P3Tony ...duh, Thanks Tony. I forgot about the GCode compression asd missed the missing '.' in the log. Changing the command to include the escape character has it all working now;
M956 P123\u002E0 S1000 A1
2025-02-25 07:08:15.399 GcodeDriver DEBUG: [tcp://192.168.2.1:333] >> M956 P123\u002E0 S1000 A1, 5000 2025-02-25 07:08:15.450 GcodeDriver$ReaderThread TRACE: [tcp://192.168.2.1:333] << ok 2025-02-25 07:08:15.450 GcodeDriver TRACE: [tcp://192.168.2.1:333] confirmed M956P123.0S1000A1
Thank you
-
undefined wayneosdias marked this topic as a question
-
undefined wayneosdias has marked this topic as solved
-
@wayneosdias thanks for confirming that