Topics created by solarsamuel

Hey @solarsamuel,

this is not bad... i was like really confused why this doesn't work.

But now I understand. It's fairly simple you are trying to run a amd64 executable on arm32 processor.

Your raspberry pi needs different executables. This repository provides only binaries for common PC (amd64).

So what you have to do is to build it yourself.

Here check this tutorial, everything should be explained there.

https://www.digitalocean.com/community/tutorials/how-to-build-and-install-go-programs

But basically it should be something like:

# install your systems go package apt-get install golang-go cd PaneldueFirmware/Tools/gobmp2c go build ./gobmp2c

@deckingman you are a legend. Yes, that was it. Switched H0 to H1 and it's working now. Thank you 👍

@solarsamuel

You cannot control, via the slider, the speed of a thermostatically controlled fan, if that is what you were trying to do.

Glad to hear you are making progress.

Frederick

@solarsamuel As an aside, normally closed switches are usually better than normally open because if a switch fails, then the gantry will slam into the frame and the motors will continue to try and move it. But, the downside of using normally closed switches is that if a wire falls off, then it will appear to be open (as you have discovered), which will mean that the gantry is considered homed at a position which could be far away from it's true homing position. Strange or alarming things will then happen if you haven't noticed and try and run a print like that (this is the voice of experience talking) 🙂 .

So here is a little tip that you might find useful. Essentially check the state of the end stop at the start of homing and abort if it's already triggered. You need to find which end stop is for which axis but generally X=0, Y=1 and Z=2 (at least that's how it is on my machine). So to check the state of the Y end stop for example, before homing Y I use ......

if sensors.endstops[1].triggered abort "Y endstop already triggered at the beginning of the homing move - aborting"

Obviously the command for the X and Z axes would use ...endstops[0] or [3]) and the message would refer to the X or Z endstop.

HTH