You should not use beta or RC firmware versions once the corresponding stable release is available (2.02 in this case). As @resam said, there was a known bug in this area in some 2.02RC versions.
Thanks David ...
Lesson learned then. I wondered if I had changed something somewhere that may have caused it ... I had not had the printer up and working for over a month - and needed to get a friends parts printed ... asap. Didnt think to see if there was a new version before rockin and rollin. Lesson #2 learned 🙂
The Z probe X and Y offsets are measured from the head reference point (which in a single-nozzle printer is always the nozzle) to the probe. So if +X movement moves the nozzle to the right and the probe is to the left of the nozzle, then the X offset will be negative.
If you want mesh compensation to correct for the bed not being flat and level, then it's important that the measured height error is at the specified bed coordinates. So the firmware puts the probe at those coordinates to measure the height error, not the nozzle.
If on the other hand the bed is flat and level but the gantry that carries the print head isn't (for example, in the middle of the X travel the gantry sags a little under the weight of the print head), then you are better off setting the probe X and Y offsets to zero so that the firmware puts the nozzle at the specified XY coordinates.
According to http://reprap.org/wiki/Gcodes the M250 command sets the LCD contrast. So it's irrelevant to RepRapFirmware which doesn't support the cheap LCDs that frequently have contrast setting issues. There is probably an option in slic3r PE to not generate that command. Perhaps it in the default start script, in which case you can just remove it. Anyway, the command won't do any harm except provoke a warning message.
If movement is very slow, you probably have some of the maximum speeds or accelerations configured too low in config.g.
Check the gcode file if it contains 'M117' commands like 'M117 Printing… tw@L 120'. If it does you should check your slicer settings (layer change script for example) if there is something that will make the slicer add these.
Your M305 P0 command is for a 10K thermistor (T10000) but you have a 100K thermistor.
well that was famously embarrassing … TY ...
Let that be a lesson to ye kidz ... stay in school ... reading comprehension, and working on tiny connectors and reading small print tutorials off the web till yer eyes twitch - may cause you to make silly mistakes ...
Changed the T values for that heater H0 ... and viola' - room temp is reading at 21*C on cold bed [ H0 ]
Alrighty then … moved passed some my issues .. but a few small nagging items in this vain - left to resolve.
Z Max endstop with a Z probe ... Z max endstop registers in the software as working Active High / NC switch ... light on z axis clicks OFF when switch is activated ... however; when testing by doing a long z+ move ... say 100+ off the z home position, triggering the switch .... do NOT stop the Z+ axis movement... I suspect my config.g settings for both a Z probe AND a Max endstop switch or incompatible - but Im not finding docs on how to run both.
Z probe as min / low - endstop ? How...
Also, Im finding nothing useable in the area of how to determine the x/y horiz offsets between PROBE and Nozzle