I’m trying to set up a custom bot, in particular it has a custom size and uses a RAMPS V1.4 board with TMC2130 stepper drivers in SPI mode.
To achieve this, I’ve made slight modifications to the farmware based on the current head on github:
In particular I added the disjunct “defined(RAMPS_V14)” to all the #if pragmas that were relevant to driving the TMC2130s and I have added the appropriate SPI pin numbers to the pins.h file for RAMPS_V14 as well as the chip select pins for each individual TMC2130. The SPI busses have also been appropriately wired to the RAMPS board.
This results in apparently functional farmware:
if I connect the Arduino to my laptop via USB and send the codes “F22 P2 V1 Q0” to approve the
configuration, then some G00 command, the farmbot’s motors move it to the appropriate position.
Note that I have not tested any other codes,
however, as my changes only pertained to driving
the TMC2130s, which appear to work, I imagine
the rest still works.
However, when I connect the Arduino to the raspberry pi 3 running v9.2.2 of farmbot os for rpi3 and after connecting it to the internet, the farmbot web interface indicates that it is unable to connect to the Arduino (error 30).
When connected, the LED on the Arduino lights up and it is quite clearly powered.
However, the interface also notifies me that the rpi is undervolted (due to it being powered by a rather poor quality usb power supply). Could this possibly be the cause of the rpi being unable to detect the Arduino?
When powered by the raspberry pi, the Arduino still appears to function as it usually does before the configuration is approved when powered by my laptop, i.e. by locking up the z-axis motor. Could it alternatively be the case that my changes to the farmware have caused this problem, despite the fact that it appears to accept commands as normal when powered by my laptop?
Any thoughts or advice on what could be causing this would be most welcome.