@ctilley79 thanks for this. i have a similar issue with my voron 2.4. mostly the tool head/fan vibrates a ton a specific speed, but i noticed at least two speeds for mine. i don't use the ldo motors either but i have them. just not that excited to change them out...
Best posts made by mrwizzard
-
RE: High Pitched Motor Vibration in Narrow Range
Latest posts made by mrwizzard
-
RE: Accelerometer causes out of memory issue
Also, there's no issue collecting the accelerometer data with M956, it creates a CSV with data.
However this also happens in reverse. if i remove the accelerometer setup, home the machine then try to run M955 it will also crash with out of memory. so it's either connect the accelerometer or home the axis, can't have both. lol...
edit: i've disable the display and freed up more memory and it works, for now.
-
Accelerometer causes out of memory issue
Edit: i thought this happened after upgrading to RRF 3.4.5, please move to right forum.
When using an accelerometer, detected in the input shaping plugin, homing the machine causes it to reset.
Using this, which is correct for my setup i believe. removing this line from the config fixes the issue.
M955 P0 C"spi.cs3+spi.cs4" I10 ;Accelerometer
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-9T6BU-FG3SN-6J9FJ-3SN6L-9SWVG Used output buffers: 1 of 26 (12 max) === RTOS === Static ram: 23836 Dynamic ram: 85312 of which 0 recycled Never used RAM 76, free system stack 184 words Tasks: NETWORK(ready,10.8%,237) ACCEL(notifyWait,0.0%,348) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,86.1%,444) IDLE(ready,3.1%,30), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:24 ago, cause: software Last software reset at 2022-12-29 20:04, reason: OutOfMemory, GCodes spinning, available RAM 4, slot 0 Software reset code 0x41c3 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x20003e38 Task Move Freestk 324 ok Stack: 2001aa5c 0041009d 00000002 00410273 00000008 00000014 20004038 0042b43f 2001aa78 00425223 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 6c000000 20003eec 2001d540 2000c9e4 20003f18 00000000 00016e35 00425659 3fb504f3 Error status: 0x00 Step timer max interval 0 MCU temperature: min 25.0, current 25.5, max 29.3 Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/3, heap memory allocated/used/recyclable 2048/46/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min n/a Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2022-12-29 20:05:23 Cache data hit count 901695954 Slowest loop: 6.54ms; fastest: 0.19ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 0.7ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 1, 2.48 reads/min === Network === Slowest loop: 128.53ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.27 WiFi MAC address 84:f3:eb:83:2b:76 WiFi Vcc 3.37, reset reason Power up WiFi flash size 4194304, free heap 24728 WiFi IP address 192.168.20.49 WiFi signal strength -52dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0
-
RE: High Pitched Motor Vibration in Narrow Range
@ctilley79 thanks for this. i have a similar issue with my voron 2.4. mostly the tool head/fan vibrates a ton a specific speed, but i noticed at least two speeds for mine. i don't use the ldo motors either but i have them. just not that excited to change them out...
-
RE: [3.4.0beta7] Moves to back right of coreXY, after a few prints.
Had something similar happen a few times, not sure if it's an issue in my config but sounds similar. it just decides to go take a walk in the opposite direction, stop then it runs the next command which is usually homing X/Y then it resumes like normal. sometimes it tries to go too fast and the steppers buzzz like they're stuck but there's nothing in the way.... it works normally in every other scenario. it's glitched but seems hard to reproduce.
-
RE: 3.4.0beta7+7 config.g and accelerometer bug
@dogma2k I've experienced #3, and gave up. i figure it was the connection even though it does detect it every time. when it doesn't a reboot fixes it. i got data points in some files but at the end of them say something like "failed to read from accelerometer." and locks up the whole board. if it's the cable i'll just have to try another time. too frustrating to deal with and re-crimp wires, lol.
-
RE: Mesh Compensation not moving Z axis Motors
@thepfeiffenator looking at the mesh, i would try some physical leveling too. Either the X is tilted or bed is physically tilted. the less compensation the better. just because it compensates doesn't mean it always should
-
RE: Bed PWM stuck on full, hardware fault?
Seems like just a config issue on my part, crazy right? somehow a e2 heater got uncommented because it was connected to a chamber light so it turned on (was never on before!), then the config-override had 1.0 as the PWM which i never looked at and i did delete but i restored from a backup as i messed something up and completely forgot.... it was a long day. everything appears to work fine now.
However, i did get the panasonic SSR anyway as the omeron is out of stock (probably because people are building vorons). i figured the other one is fine as it's rated for 40A. (probably not but it might at least be 10A).
-
Bed PWM stuck on full, hardware fault?
So i've been building a voron and used an ssr i had used before but different board. i'm using the duet 2 wifi. so when I used this on bed output DC in on the ssr like usual, it works and the bed heats but the average voltage is the full 24v regardless the pwm setting so it's pulling like 700w, lol.
however when i tested it on another heater on the duex, e2 i think...before i finished the config it seems the mosfet poped and it's suck on. while the bed output isn't on the main board i feel like this SSR broke something or is preventing proper pwm.
Any ideas where to look? i have a new mosfet for the duex but perhaps this is an issue with U11? i haven't checked if my hotend has the problem which is probably a good idea. i have some extra replacement chips for U11 but.... i rather not if i don't have too.
Thanks
-
RE: Can two 24v heatbeds be connected to the same duet wifi?
Not just the duet but the power supply must be able to handle it too if using an SSR. my take is anything bigger than 10-12" and i would use an AC silicone heater with an SSR... it will also heat up just as fast as the hot end to 100c+
-
RE: Testing Power Fail and Resuming Print Issue
i didn't think you would home Z when there is a power loss... you would just run into the print unless you did home to max. setting it to ignore the un-homed z might work so you just home X/Y and Z stays as is.