Topics created by Nurgelrot

@dc42 just a follow upletting you and anyone following this issue that in my case the expression nesting was still too deep even under 3.5.1. I corrected it by making my macro a little cleaner. Basically not loading so much into one variable assignment. but spreading out the math 🙂

@chrishamm Right that's basically what I do. But I don't know playing around with a pretty graph until things look "flatter" bugs me 🙂 Is there was some way of knowing I'm doing it "Right"? I guess at the end of the day as long as the prints look corect its the only indicator. I doesn't help that in all the IS examples you see this clear peek none of my printers no matter how I adust them ever have pretty graphs.

@Phaedrux Yes everything should have been correctly wired and the problem did occur again two more times. I replaced the toolboard and that has solved the problem. I'm working under the assumption that I cooked the previous toolboard. As I have temps reaching 80+ C reported from the board for long periods on an identical build that has not been in service as long. It just a guess right now but... Will figure out how to drop the temps and continue to watch it.

yeah I must have done something stupid. I swear it had power. but ... now its working. thanks for the assist for whatever dumb thing i did.

m122 b121 Diagnostics for board 121: Duet TOOL1LC rev 1.1 or later firmware version 3.4.0 (2022-03-15 09:00:04) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) All averaging filters OK Never used RAM 2172, free system stack 62 words Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,3.0%,57) MAIN(running,91.8%,349) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0% Last reset 00:02:11 ago, cause: power up Last software reset time unknown, reason: WatchdogTimeout, available RAM 2612, slot 0 Software reset code 0x00a0 ICSR 0x04413011 SP 0x20007f18 Task MAIN Freestk 5934 ok Stack: 200047a8 00000002 42003800 20000000 41000000 000167bd 0000c1a8 01000013 00000020 00000020 200031a4 000167bd 200047a8 00000005 00000000 00b00b00 00000015 fffffffd 9ed18dcf 00000000 00000002 00000000 00000002 000191c7 00000000 2000213c 200020e0 Driver 0: pos 0, 400.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 174, writes 12, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter -3/9, peak Rx sync delay 627, resyncs 0/0, no step interrupt scheduled VIN voltage: min 24.3, current 24.3, max 24.4 MCU temperature: min 28.1C, current 35.5C, max 35.5C Last sensors broadcast 0x00000002 found 1 229 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 2735, send timeouts 0, received 1210, lost 0, free buffers 37, min 37, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 Accelerometer: LIS3DH, status: 00 I2C bus errors 0, naks 3, other errors 0 === Filament sensors === Interrupt 4 to 9us, poll 8 to 700us Driver 0: pos 0.00, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0```

@lo-fi For the record if anyone is reading this. .5 was too much but I printed different sizes in a batch in the resin printer. The one with .3 added to the inner surface of the lid of the MMF v2 housing got me to the magic agc 110 mag 128 that seems to be working... All magnets vary of course so maybe mine was just a little bit strong.

But if you have a sensor that's reading way high mm/rev sensitivity back your magnet off a tiny amount. the tolerances in the thing are super tight.

@pcr Yes, thats right. Unfortunately PrusaSlicer uses an invalid content type for the G-code request so I had to work-around it.

@carl-higby the dimensions are in the scad if you can read that? The PCB dimensions as are on the wiki here:
https://duet3d.dozuki.com/Wiki/Duet3dFilamentMonitor_RotatingMagnetVersion#Section_PCB
i would aim for no more than a clearance gap.

@fcwilt It just something I'm doing wrong or not understanding in RRF. Marking it resolved for no since I'm sick of working on it. Klipper is on the printer right now and all the probes are exactly where they should be every time. Too bad I cant stand klipper 🙂

Thanks for your help with this I did learn a lot about how things work even if I didn't solve whatever is going on with this printer. (I have several other with no issues so who knows)

@Nurgelrot thanks. for the feedback. Actually what @dc42 is saying is right. When the screen is dimmed communication with the printer just works as normal and PD should receive all updates.

So if you still observe weird things don't hesitate to start a new thread describing your problem.

@nurgelrot said in Number of probe point 400x400 bed?:

@fcwilt Well I don't see the point of getting into -my bed is more level than yours- discussions.

That wasn't my goal.

I was just wondering if you know your bed is even because you have done a dense grid or you just think it is even.

No big deal.

Frederick

Thanks for the heads up on the config tool.

@o_lampe said in RRF install failure with Hardkernel Odroid C4 as the SBC:

@joeko said in RRF install failure with Hardkernel Odroid C4 as the SBC:

with Exec On MCode setting i shut down the sbc with M7722

Shut down isn't hard, but how do you restart it? I have an remote controlled mains adapter to switch the odroid powersupply off/on to restart...

you can restart the sbc also on this way. create an new service and call him reboot. modify the lines from poweroff to reboot andfrom M7722 to M7723 and than you can reboot with M7723. also updates over the sbc should be possible

@adammhaile Well they where working until I replaced them With Odroid C4's and then pulled off the odriod's from all but 1 printer. SBC mode has been more trouble than its worth.

Thanks for the update. Let us know if it happens again.

@jens55 on a whim I touched up the solder on the 5v and ground pins on the fan board. Have it running on another pi that's running 2 web cams + a small display and hasn't had an issue yet. I'll test for a couple days. Maybe it was just bad manufacturing.

@fcwilt
If there's a Meta-code repository, it would be nice to post it there. too.
Maybe with variables for iteration-depth and deviation-target. Placed at the beginning of the file, they are easier to find for all of us.

@jay_s_uk - Ahhh ok. TY !