Working on a sensor pack that checks the temperature of each stepper driver and the TinyG2 (Due). (In the picture I was running a 4 axis job - So X, Y1, Y2, Z & A. The 6the driver (B) is connected, but with no stepper) Then reports the back to the RPi. If the MCU detects a driver running way too hot, it pulls and holds the reset button, then a local script on the RPi trigger and sends me a pushover notification. The goal is to create a ‘widget’ for chilipeppr and create a graph of all this. There is also a local 7" TFT touchscreen that shows the same info, but will also act as a DRO and pendant (WIP). (Still working on the SPJS part)
One quick thing to add, The MCU can PWM control the fans (via FETS) on each of the drivers. So if a driver gets hot- And it increase the fan speed and the temp is continuing to raise. It resets and holds the DUE.
That’s really cool. So, for the widget, you could mimic the laser solder widget where it binds to an Arduino via SPJS independent from the TinyG. Watch the laser solder video to see the approach I took with giving a pulldown of serial devices in the new widget so you can talk in parallel to the TinyG2 and your sensor pack Arduino. https://www.youtube.com/watch?v=T2h7hagVfnA
Is there a tutorial out there what shows how to test widgets with-in CP? This is a whole new deal for me. Kinda used to get directly editing what I need.
I don’t think the GPIO widget can handle data. I figured I could use the SPJS and hand the data over to a Monitoring widget (Which I still have to create)
I’ve got the hardware part done. Just need to get it to talk to CP.
My main thing is to get my DRO working again. Before I was able to connect to GRBL TX/RX pins and read inbound/outbound going to the GRBL and use the mega to ’spy’ on the traffic then read off the work/machine positions and populate the fields on the TFT. As for the pendant, I was using a Esplora which was connected to the mega via I2C. Which basically told the mega direction and distance. Then the mega would pass that directly to GRBL.
With TinyG2- You have to use the native usb port. So since SPJS is already connected to it, My plan was to have another daemon connect the SPJS via a web socket and pull the work/machine pos and use that link to inject jogging commands. I got that link to work, It’s ugly- But it works.
