When Printipi detects an invalid gcode command (attempt to set a nonexistent fan, etc), there's not much it can do to communicate this error to the host. It can either:
Reply with "!! ", which indicates a non-recoverable error and suggests that the machine will shut down. But this is overkill for a trivial, recoverable error like an attempt to access an invalid fan.
Reply with "ok" and then follow up with "// warning:", which indicates that no error has been detected, but gives us the opportunity to insert some extra information that shouldn't impact operation. This is misleading, because it suggests that the attempt to set the invalid fan was successful.
Unfortunately, these are the only valid response codes besides a "resend" request, according to the Reprap Wiki. Option 2 is still better than just logging the error to the console, but I'm not sure if all hosts would accept a line starting with "//". Therefore, since this extra information doesn't actually produce any effects, it should be possible to disable it for hosts that don't support it.
When Printipi detects an invalid gcode command (attempt to set a nonexistent fan, etc), there's not much it can do to communicate this error to the host. It can either:
Unfortunately, these are the only valid response codes besides a "resend" request, according to the Reprap Wiki. Option 2 is still better than just logging the error to the console, but I'm not sure if all hosts would accept a line starting with "//". Therefore, since this extra information doesn't actually produce any effects, it should be possible to disable it for hosts that don't support it.