well I wanted to end by showing my code, but it gets rejected as spam...

@achrn
Wow, that was what I was looking for,
works great thanks!

@infiniteloop
Whell the last time it happened the teensy hung mid print was because of af bad solder connection of the IR-sensor, and the library for that melexis sensor makes Teensy hang. So I am looking in on to how to avoid that. But it made me realize that there can be other bugs that makes the teensy stop working...

But thank you for the watchdog tip, I will look into that to!

@Sindarius
Yes, I added you option as well. It prevents a fals trigger at startup as daemon.g runs every 10 seconds.
Now daemon.g runs 5 times before it is triggered and halts a print.
very nice !

Thank you, I will see if I can use this function for my purpose...

So I am doing some preliminary searching on how to get this done:

I have an arduino/teensy board, connected to my main board over serial, instead of a display.
for my next project i want to read a lot of bitmaps from the SD card on the mainboard.
I know there are gcodes to list/read and write files, but these are meant for gcode files...

So my question is if RRF can make the files on the SD card available to an Arduino over serial?

(My ultimate goal is to create a printhead on corexy kinematics with multiple individually addressable diode lasers, to be used in a SLA or SLS printer. The Arduino reads the bitmap files uploaded with DWC, reads the steps of the x-axis motor and controls the multiple lasers according to color of the corresponding pixels. So my 3d models need to be sliced with a DLP slicer like Chitubox instead of a Gcode based slicer like Cura. This system would eliminate the need for a galvo system)

well I wanted to end by showing my code, but it gets rejected as spam...

@Sindarius
Yes, I added you option as well. It prevents a fals trigger at startup as daemon.g runs every 10 seconds.
Now daemon.g runs 5 times before it is triggered and halts a print.
very nice !

@achrn
Wow, that was what I was looking for,
works great thanks!

@infiniteloop
I agree !

@infiniteloop
Whell the last time it happened the teensy hung mid print was because of af bad solder connection of the IR-sensor, and the library for that melexis sensor makes Teensy hang. So I am looking in on to how to avoid that. But it made me realize that there can be other bugs that makes the teensy stop working...

But thank you for the watchdog tip, I will look into that to!

Hello,

Normally I search the internet for guidance while I am halfway with a project , this time I thought I will ask around before I start ... so let me start by explaining my setup:

I am running RRF 3.3.0 on an SKR2 board (sorry) and it controlles a SLS 3D printer. The temperature of the powderbed is measured with an IR-sensor that is connected to a Teensy board (=arduino). The Teensy board emulates a max6675 thermocouple, and RRF reads the powderbed via a SPI communication. Meanwhile the Teensy board also needs to check what the set-temperature is. It does that by sending a M409 command over the serial port, and thus checking the Object model tree of RRF 3.3.0

And this work great!

But.... if mid-print the IR-sensor dies, or teensy hangs for whatever reason, and keeps sending the same temperature over SPI, then RRF has no way of knowing this...

So my goal now it to have RRF check if Teensy is still alive.

My initial idea is to have teensy send a G-code to set someting in the object model tree, like switching on a fake fan, and do that every 30 seconds.
Than use Deamon.g to check if the fake fan is on every minute.
If the fake fan is on, deamon.g turns it off
If the fake fan is off, deamon.g will stop the print and turn off the mainheater switch.

Now my question is if there is a nicer way of doing this, my methode feels a bit clumsy using a "fake fan" and all...

Any input is welcome!