ahhhh yes the screws on the stepper drivers! I forgot about them.
Great!
As far as the moment being incomplete.
It’s within the web application. The top section where the Farmbot gives you a response after commands have been input.
For example:
"[FILTERED] 10:48 am TreeGrowth Completed movement: (-200, -1100, -200) 10:42 am TreeGrowth’s arduino says: stopped 10:42 am TreeGrowth’s arduino is busy. 10:42 am TreeGrowth’s arduino is busy. 10:42 am TreeGrowth’s arduino is busy. TreeGrowth’s arduino says: stopped"
ive gotten the bot to move from left to right on the Y axis 100 across the length of the track so that has been fixed at this point.
The next step for me is to make sure the X axis motors work with full movement.
I never bothered with turning off for turning the screws. No idea with direction, I just fiddled until it worked. But in the new version, the z axis is always powered, so adjusting the Z might be a bad idea when turned on.
I can’t comment on the messaged on the controls. I use g-code directly for testing purposes mostly.
I’m also having problems with the connection, the IT department at the company needs the port that they need to set open because normally everything is blocked. it could also have something to do with the wpa2-personal/work thing but they are not sure. I hope you could help me out!
Farmbot OS uses https for the backend systems and NTP for the time synchronization. Hence they’ll need to open the following ports for outgoing connections:
tcp 443
udp 123
Never the less we should open a ticket in github to add proxy support in the future. Can someone please do this? I’m still waiting for the approval of my employer to sign the CLA ^^
When booting from a fresh 3.1.5 for the first time, both configuration and connection through the web app work as expected. I can move the bot and everything. After poweroff and restart, however, the bot is reported to be offline.
Similarly, the bot is reported as offline after a emergency stop. And after a reboot triggered through the web app.
EDIT
I have tried to further narrow down the problem, and it seems that the pi does not reconnect to the wifi. Using the app ‘LanScan’, the pi initially appears in the list of devices on the network, but after reboot, it no longer does.
Tim; I reinstalled the 3.1.4 sd and did a reconfigurator. I was then able to reconnect through the console to the farmbot. I was able to run my sequences and vacuum pump and the version shown was 3.1.4.
I will monitor the forum and see what is up with 3.1.5.