Teacup incorrect response to M105 command

Hi,

My Teacup firmware has the following behaviour:

I send: M115
Teacup sends: ok FIRMWARE_NAME:Teacup FIRMWARE_URL:http%3A//github.com/triffid/Teacup_Firmware/ PROTOCOL_VERSION:1.0 MACHINE_TYPE:Mendel EXTRUDER_COUNT:1 TEMP_SENSOR_COUNT:1 HEATER_COUNT:1
I send: M105
Teacup ends: ok
T:317.75


Note that there is an endline between the "ok" and the "T:317.75". This is causing RepRap host to get confused, because the temperature should follow the ok on the same line.

Am I the first to observe this behaviour, or is it something anyone else has noticed?

Currently running: RAMPS 1.4 electronics
I'm just sending those commands directly over the Arduino serial monitor, but the same happens when I send them using RepRap host.

I've tracked this down in the code, and it looks like it was deliberately programmed for the case where REPRAP_HOST_COMPATIBILITY is less than 20110509. I guess the old RepRap Host software for some reason expected a newline there?

Yes, different hosts require different responses. Use Pronterface, which is satisfied with any response or adjust the response to what you need.

---

Generation 7 Electronics	Teacup Firmware	RepRap DIY

Ok, I've adjusted it to work with RepRap Host.

I may have now found another bug:


I say: G1 Y28.5 F3111.0
RepRap says: k
RepRap says: ook
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap: k (hex: 6b20) [411.463s/32824ms]
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap: ook (hex: 6f6f6b20) [411.463s/32824ms]
RepRap says: ok


It looks like there might be a typo somewhere?

Edited 1 time(s). Last edit at 02/19/2012 02:13PM by jbayless.