Topics created by vernon1xx

Hello,

Thank you, I concur! I will make the changes accordingly..

I was wondering about that myself... I inspected all the fuses, and they all look good. Also, I cannot see any physical damage to the board. In the beginning the board was completely dead. I took a few minutes of sitting to get the lights to come back on... Initially, after the lights returned, the ethernet was working. After several times of off/on while running tests, it stopped lighting up..

You should probably upgrade to the latest 1.21.x or 2.x releases for all your firmware as there were a few bug fixes that may be affecting you. You're also on release candidates and it's a good idea to upgrade to the full release once it's out.

https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md

Namely from 1.21.1

If G30 was used to set an accurate Z height after mesh bed probing or loading a height map, if bed compensation was then cancelled then any Z offset from the height map remained. One consequence of this was that if bed probing was run again, the original height map Z offset was carried through to the new one, but the sign of the offset was reversed.

https://github.com/dc42/RepRapFirmware/releases

Any endstops that are not configured for use with visible axes using M574 are assumed to be active high in the Machine Properties report. This means that they show as triggered when nothing is connected to them (LED off), and as not triggered if the outer 2 pins of the connector are shorted together (LED on).