RRF36 disconnecting mid-print
-
@justGuner When the print fails, what is happening with the flashing led on the RRF36? Is it flashing quickly, slowly or not at all?
After the print fails if you reset the mainboard using the reset button on the skr2 but do not powercycle it (and especially don't powercycle the RRF36), do not do anything that moves the print head (like homing) does the led on the toolboard come back into sync with the mianboard? Can you get a M122 B124 after doing that reset? If not power cycle the printer, do not move anything, does the RRF36 sync with the mainbord, if so can you get a M122 B122 from it.
-
@gloomyandy said in RRF36 disconnecting mid-print:
When the print fails, what is happening with the flashing led on the RRF36? Is it flashing quickly, slowly or not at all?
The led flashes rapidly.
@gloomyandy said in RRF36 disconnecting mid-print:
After the print fails if you reset the mainboard using the reset button on the skr2 but do not powercycle it (and especially don't powercycle the RRF36), do not do anything that moves the print head (like homing) does the led on the toolboard come back into sync with the mianboard?
As far as I remember, after pressing the reset button on the mainboard, the led on the toolboard would come back to synk with the mainboard and regain all functionality. I started another print job to verify the behaviour.
I should also mention that after the fail point, the hotend seems to hold it's determined temperature, because it doesn't cool down and it doesn't seem to cook the filament in the nozzle either.
-
@justGuner That sounds like the RRF36 did not crash, I would be looking closely at the CAN bus wiring between the two boards. The mainboard was showing CAN Tx timeouts and a bus off error, that usually indicates a problem with the CAN bus wiring.
Messages queued 9917, received 4473, lost 0, errs 0, boc 1 Longest wait 4ms for reply type 6024, peak Tx sync delay 201 free buffers 50 (min 19), ts 2564/1112/0 Tx timeouts 105,0,1452,0,0,777 last cancelled message type 8191 dest 127I assume that you have the terminator enabled on the toolboard?
-
@gloomyandy I pressed the reset button on the board, and now it is stuck in a boot-loop. After power cycling the board, it remains in boot-loop. The contents of the sd card are still readable on my laptop.
-
@justGuner How do you know it is in a bootloop? What did you do differently to the last time you reset the board, you said above "after pressing the reset button". Doing a hardware reset will not normally cause any sort of loop.
-
@gloomyandy this is the behavior that I'm associating with boot loop:
https://drive.google.com/file/d/1EX8ncjLaL5Gg9t0ZIwL676H8gxXVDZhE/view?usp=drivesdk
The difference between what I did now and before is that before when problem occurred, I would first pause the print, and then press the button. This time I just pressed the button without stopping the print.
-
@justGuner I've never seen pushing reset cause any sort of loop and I push reset a lot when debugging/developing the firmware. Are you sure that there is not some other problem like an issue with the power supply? I can't see your video it is still be processed.
The only thing I can suggest is that you try reflashing the firmware to the board from the sd card.
-
@gloomyandy I've changed the link, you should be able to see the video now.
Reflashing the firmware did not solve the issue.
-
@justGuner What is the Led that sort of fades out? Is that the normal status LED? If you put a firmware.bin file on the root of the sd card and reboot the board do you see any leds flicker for a short while after power on? Also if you check the card after a waiting a short while has the firmware.bin has the name changed to something else?
-
@gloomyandy If you mean the green one I think it's a power indicator.
If you put a firmware.bin file on the root of the sd card and reboot the board do you see any leds flicker for a short while after power on?
Yes, and after that it repeats the previous behaviour.
Also if you check the card after a waiting a short while has the firmware.bin has the name changed to something else?
It turns into a cursor file.
-
@justGuner So it sounds like you still have a bootloader. If that is a power led then it looks like something is pulling the power supply down very low and that is causing the board to reboot. You could try removing everything from your config.g file (keep a copy) other than the commands to setup the wifi and see if that allows the board to boot. Are you sure you have not made any other changes, for instance to any of the wiring or to the config.g file?
If the above does not work then I'd suggest disconnecting everything from the board and see if that allows it to start.
-
@gloomyandy ok, removing everything from the board (except the esp32) after deleting everything in the config file except the networking stuff lets the board boot up. I can acces the board through web control. I guess I will shut it down and start plugging in stuff untill it stops working again.
-
@justGuner Yep that's the process. Good luck!
-
@gloomyandy Everything works fine untill I connect the efd to the board. After that, it's the same story again...
Closer inspection of the efd doesn't reveal any burns. It also passes the smell test (no burnt electronics smell)
-
@justGuner Sorry what is the "efd" in this context? How is it connected to the board.
-
@gloomyandy isn't that what the can adapter from mellow is called? The one connected to the exp ports
-
@justGuner Ok so it is the CAN-FD interface. Do you still have the CANBUS connected to the board? If you disconnect that does it still cause problems?
-
@gloomyandy No, if I power on the board without the CAN-FD interface, the board boots up just fine.
-
@justGuner how do you have that connector wired? post a picture.
-
I feel like I should mention that this system worked for the last month, and only just now that I started to print faster it began showing the initial behavior.
