I'm just testing version 1.55 with Smoothie and I have hit a bit of

3D Printing GCodePrintr
, ,
1

I’m just testing version 1.55 with Smoothie and I have hit a bit of a roadblock. It connects successfully, and I can issue commands and get results back. However all my printers are using M80 to switch a PS relay on (M81 = off). When trying to issue a manual command, when it works I see:

Send: M92

0: M92
Queued → M92
X:100 Y:100 Z:100 F:60 E:825
ok

When I try the PS on, I see:

Send: M80

Queued →
0:
(long pause)
Timeout waiting for printer response at line #0(12001ms)

Communication is ok because after the timeout I can still see the regular M105 requests. It is as if M80 is being eaten by something…do you have a bugtracker?

Once I can get the PS on, I’m confident it will work well with smoothie as everything else is working as expected. Currently using an edge compile from last month-ish of smoothie, once I get this working I can post further details.

2

I just realised there seems to be a filter on the output commands. M80/81 is the marlin/repetier standard for ATX on/off, at least according to http://reprap.org/wiki/G-code

If you’re implementing other codes, there is a list of smoothie’s custom codes here http://smoothieware.org/supported-g-codes These are generally a subset of the Marlin/Repetier codes with the exception of M907 which sets the digipot for current on the drivers (M907 X1.2 will set the X motor to 1.2A).

3

@Sean_Mitchell good feedback. I have to check why M80 doesn’t come through. there shouldn’t be a filter at all.

4

@Sean_Mitchell I found the bug. Looks like all unknown GCodes have been ignored. I’ll post an update soon.

5

btw. Github bug tracking can be used: https://github.com/dietzm/GCodeInfo

6

@Sean_Mitchell I just pushed the new beta V1.56 … it should appear as an update soon

7

@Sean_Mitchell did you had time to try the update ?

8

Not yet, tomorrow night I’ll be giving it a try and posting results

9

I just got a smoothieboard at MRRF this last weekend. Excited to give it a try using GCodePrintr.

@Sean_Mitchell Did you ever get a chance to test?

10

Yep it worked, posted a video too :). I usually use octoprint so the test was more to see if it worked, which it did. My android hardware is a stick without display, so not the optimal setup but it worked!