There is no log file setup at the moment… I would like to include it but I keep on postponing 
It is possible to create a .env file with some custom environmental variables that will log in the raspbian terminal the entire communication with the serial board… If you like you can try to have a look at the development section of the readme… I’m abroad for work this week and I cannot do any test on my marlin setup. I can do it during the weekend or next week probably. If in my setup it is still working correctly I will put in the logging thing so that you may try again.
1 Like
No rush here, I use octopi in the mean time, and I will take the time to test sandypi when ready 
1 Like
Hi!
I tried again in my build and everything is working fine. I’m running marlin 2.0.5.3 though, but there should not be that much of a difference I think (I do not have enough time to flash your version now, sorry).
I’ve just added the logging capability. You can pull the latest commit and the logs will be available in the “server/logs” folder. I also added a log for the installation process.
Let me know if there is something in there… I’m really interested in figuring this out! If you need help share the log files.
1 Like
Will do !
Hi there, Sorry I didn’t had time to test anything, I lost my job, find another one and have to move the whole family !
Good news I’m winning a huge workshop to test new setup and software, but not before one month, sorry about that.
Just wanted to let you know 
3 Likes
You don’t need to worry 
everybody has a limited amount of time for these projects… Happy to hear you will get some when you need I’m here
2 Likes
HELP WANTED!
Hello All. I have some trouble to install the sandypi img on a raspberry pi3 b+. Everything is going well on PI 4 4gb but not on 3b+!
when installing I have the message show on the log file bellow. As anyone the same problem? can someone test it?
thanks a lot for your help
install.zip (6.9 KB)
Hi!
The problem is with Node. It looks like there is a problem with the heap memory usage during the installation.
Not sure why I do not get it (Raspbian os on pi 3b+). I’m using Node v10… Maybe something related to the node version?
I’m not able to test anything at the moment… Maybe this can solve: https://stackoverflow.com/a/53443394
Let me know
1 Like
For anyone with the same issue: looks like the problem is indeed with the node version. V10 should work fine, above that is not guaranteed. Check the issue on github for additional infos
Hi y’all, I am just finishing a ZenXY build running SandyPi on a RPI4 using GRBL on a Arduino/CNC shield. Let me first say, this is awesome! Thanks for your work on this project! I have a question about the LED controls. I am running the alpha version 12a9442 of SandyPi. If I adjust LEDs before or after a drawing starts everything works flawlessly. If I turn the LEDs on and then start a drawing I can adjust the LEDs while the drawing is going. However, if I start a drawing before I turn the LEDs on and then try to turn them on while it is drawing, the drawing freezes and I can not restart or turn LEDs on or anything. Reboot required. Is there a way to turn the LEDs on upon boot up? Where would the default settings for boot up be located in the file system? Thanks so much in advance for your responses!
2 Likes
Hi! Happy to hear you like it!
That is for sure a bug… I will have a look at it for sure…
About the “auto-on” thing there is nothing at the moment but it make sense tu put it in, thank you for the suggestion.
In this period I’m really busy and the project is a little bit on hold but I will be back for sure as soon as I can (may be sometime during the christmas holidays)… I will let you know when this is fixed
1 Like
I’m about to jump on the SandyPi bandwagon to run the table I’m building.
What’s the current status? It’s been 7 months since anyone has commented on this feed, so it has me slightly concerned. lol
1 Like
Hi! I’m still on the project but with limited time due to my job requiring me to travel a lot. Since the last update on the forum I made some fixes and changes but I was not able yet to implement the feature requested by other users… The most important update recently was the introduction of docker to have a simpler installation. It is really quick and should also be really easy so you can at least try it out 
On github, it looks like the project is stuck because I’m working on some background features that are giving me headackes and I still need to fix some serious bug before pushing to the main branch. I will keep on the light by working on it in my free time even if it is very limited 
I was hoping to get somebody else involved in the project but atthe moment it is not big enough to be “appealing” probably… I will be happy to hear also some feedback if you manage to try it out
5 Likes
Just a quick question - I have the SandyPi installed on a PI4 and it loads up well enough. Does anyone have any advice on how to connect it to the GRBL CNC reader. Im using FluidNC on a ESP32.
Thank you,
Tim
1 Like
Hi! At the moment only the serial connection is compatible (probably in the future there will be also socket or telnet compability). That means you need to phisically connect the board to the pi for the moment… Once connected, open the sandypi settings, select the correct serial port and set the correct type of device. Hit save and connect and it should be communicating
2 Likes
Hi Luca,
First of all nice job on the software. Im excited to try it out. Can i ask like what is the best way to achive a serial connection between the boards? Is it through the usb or GPIO? Which pins? Do you have detailed instructions on the specifics of the connection for noobs like me?
Tim
Thanks! There are no detailed instruction for the moment… For the connection should be enough a usb cable connecting the esp to the pi. Connect the cable and then turn on the system. When you have access to the interface, go to the settings section and select the usb serial port (should be something like tty/usb0 I think). Then select the baudrate (which depends on the firmware you installed on the esp) and you should be able to communicate with the board. Set the firmware type to grbl and the type/dimensions of the table and it should work
Luca,
Thank you for the reply. I did all that and am making some progress. I made a quick video - I thought it would be easier to see what im doing. If you dont mind can you have a look and Im open to any suggestions or advice.
https://www.youtube.com/watch?v=OYvquoyjNtM
Thank you sir,
Tim
1 Like
It looks like you are almost there!
One thing that is not obvius with grbl is the feedrate (even though I’m more of a Marlin guy so this may not be the real problem)… If you do not set it explicitly, most of the time it starts from 0. I think in your case, by using only “X250” the board is using some kind of safe feedrate. The gcode from the drawing is using something like “g01x250”… Try to set the feedrate with the $110, $111, $112 commands and then try to write in the command line some g0 or g1 commands and see if like this it works. If it is necessary to set those command every time you can use the “before drawing” script in the settings. If you still have problems after this test, please open an issue on github and load also a screenshot of the settings you are using so that we can investigate further
1 Like
@timcallinan - here a list of things that came in handy for me when I started using grbl for CNC after having previously only used Marlin for 3D printing:
- Read through this page if you haven’t already. It spells out how to check status, set parameters, and what all the parameters do and what units they expect. Don’t get too hung up in the “mask” parameters to start with. They can be a bit confusing if you’re not used to the concept of combining bits for separate axis into one setting. I think this documentation does a good job, but it still might take a couple of readings to be able to digest it.
- The $$ command is very helpful. It will show you current settings for all the parameters the board remembers between sessions.
- There’s no separate action to “save settings.” All the $ parameters are persistent.
- I’ve used an experimental process to find workable acceleration ($120, $121, $122) and velocities ($110, $111, $112) across several machines now and it has served me well. For each axis, start with a known safe velocity, increase acceleration (e.g. $120 for X axis) until steps are lost, then back off 5-10% to establish a safety margin. Then, use the same process to find your maximum reliable velocity, increasing (e.g. $110 for X axis) until steps are lost, then backing off again. If you try to tune velocity before acceleration, you can’t know which is leading to lost steps.
- Once you have acceleration and velocity limits set in the parameters, you can bump them up higher than this in the gcode and the firmware will not let the machine go too fast.
2 Likes