Posts made by StaticRed

@dc42 I dont use RRF on my duet currently i am trying out klipper. I think klipper has functionality for multiple neopixel on one board? Can you maybe name me the exact pin of the LCD Connector?

Hi,
I use a Duet3 Mini 5+ WiFi and would like to know if there is any other pin which is able to drive neopixel other than the Neopixel dedicated Pin? Would be useful to drive multiple strips via. klipper for example.

Thanks

Hey im using a duet 3 mini. And i configured stallguard like this:

M915 Y X S3 R1 F2 H200		

Im using a CoreXY Machine so i directly used the axis. I then configure my sensorless homing like this:

M574 X1 S3                               ; configure active-high endstop for low end on X via pin ^io4.in
M574 Y1 S3                              ; configure active-high endstop for low end on Y via pin !io3.in

To home the machine i use this macro:

G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
M913 X70 Y70 ; drop motor current to 70%
G1 H1 Y-175 F3500 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000       ; go back a few mm
G1 H1 Y-175 F360  ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000   ; lower Z again
M913 X100 Y100 ; return current to 100%
G90               ; absolute positioning

Sadly this does not work, my motors just crash into the frame and become really loud. Even if i use an S Value like -50 it does not work. Maybe i missconfigured something?

@dc42 Hey thank you for the quick answer. I have the latest Duet 2 Wifi I think and it already works fine with Endstops from the outside. So I will just send a High signal 24/7 and then say my Arduino to set the pin to low for a short duration and then back to High? What kind of duration can you recommend?

Hey I have an idea and im not sure if I can implement it correctly. So I have a secondary board inside of my machine which watches a lot of things like current voltages and temperatures inside of my machine. Now if some kind of sensor reaches a certain limit I want to give the Duet a signal to execute an emergency stop. How could I do this. I thought giving both the same ground and then using one of the end stop pins and putting 5v onto it. My duet currently runs at 24v so would this be possible (Duet 2 WiFi).

Sincerly

@dc42 i will test thank you

Hey so i got a inductive sensor which is working at 12v. It has 3 Cables, Plus GND and signal. When triggered on the signal line there is 12v, otherwise it is at 0v. When i now connected the probe to my duet 3 mini, for now only as a z endstop, it wil always read not stopped. Even if the sensor is stopped (it has a led to signal that). I put the signal line on io2.in. I read that it only detect when the pin is set to ground and not when a voltage is input. Is there any other connection i have to do then?

@dc42 seems like my thermistor has died randomly. Nevermind i will just by a new one and try it out.

Hello, so my printer is mostly working fine. But sometimes i have a weird error on my machine. When im heating up the hotend, the thermistor readout on the mainboard dies, and then i get a heating fault. So im not able to start a print or something similar. Im pretty sure its not a cable problem, because the problem only occures when the heater is heating. When i then reset the machine, the readout is normal again an it can read it out. Then if i try to heat it up again, the readout dies again. Im using a 24v 50w heater on my mainboard, and im sure that my power supply has enough power to supply that. So maybe something else is wrong. I also tried the other temp port, and it seemed to have fixed the problem, but after a while it occured again. So maybe someone of you have an idea.

Hey so im trying to run some input shaping on my 3d printer. Already im getting nice results using DAA and around 45Hz. The problem is now, if i want to use for example zvd as in the wiki, my printer says its not a valid type. Im running 3.4.0 b01 https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.0beta1. Also updated DWC to 3.4.0.

@martin7404 what speeds did you use for the testings? I used 30000mm/min to test it. My normal printing speed at around 10000mm/min has kind of the same readings as yours. But my machine is also at the moment super small and the carriage ways about 300g.

@phaedrux it would be good to know on how to correctly analyze the data i now gotten. Date for X Axis looks something like this
but which frequency should i now try to cancel out, like the 7hz one or more like the 43hZ one?

@phaedrux thank you for the quick answer, i will test it out

Hey, so i got finally my accelerometer running on my 3D Printer. I can run tests and collect the data and look at them. But what now? How can i use this data to use Input Shaper on my Printer. In the documentation nothing about this is listet at the moment.

@dc42 hey so i got now everything working on my board. Also using now the resistor. But now what should i do with the data? How can i now use input shaper? I mean i can view it an hit analyze, but then? Not sure what i should do next.

@dc42 i will definetly try that out. I had firstly swap my board because of that early production process. While doing that i also swapped my z axis, now need to reconfigure than, and then can test the lis3dh again.

@dc42 thats no problem. I dont need the printer 24/7 i have other printers which can get the job done. I thank you for the advice.

@dc42 oh wow that was the issue? Well thats nice then i did not ruin anything haha. Yes i will send a message to that email. I have a good contact to my supplier (i work there) so that hopefully will be a fast exchange. I btw tried to change my sdcard, which did actually work for one print, but now it seems like it stopped working aswell.

Thanks for the quick response, you saved my day

@staticred updated now to full release of 3.3. Same issue still. I hope my duet didnt broke randomly.

@staticred M112 results
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3RC3 (2021-05-26 13:44:42) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: N85PY-3096U-D65J0-40KMD-3J03Z-RHQAD
Used output buffers: 3 of 40 (13 max)
=== RTOS ===
Static ram: 102572
Dynamic ram: 106244 of which 52 recycled
Never used RAM 31980, free system stack 134 words
Tasks: NETWORK(ready,16.0%,234) HEAT(delaying,0.0%,320) Move(notifyWait,0.2%,276) CanReceiv(notifyWait,0.0%,943) CanSender(notifyWait,0.0%,358) CanClock(delaying,0.0%,339) TMC(notifyWait,0.7%,114) MAIN(running,81.9%,426) IDLE(ready,0.3%,29) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes: WiFi(NETWORK) HTTP(MAIN)
=== Platform ===
Last reset 00:08:05 ago, cause: power up
Last software reset at 2021-06-20 14:23, reason: User, GCodes spinning, available RAM 34836, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU revision 3, ADC conversions started 486123, completed 486122, timed out 0, errs 0
Step timer max interval 1490
MCU temperature: min 26.4, current 42.0, max 43.1
Supply voltage: min 23.6, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/26/26, gc cycles 0
Driver 0: position 12580, standstill, SG min/max 0/418, read errors 0, write errors 0, ifcnt 12, reads 25520, writes 12, timeouts 0, DMA errors 0
Driver 1: position -125, standstill, SG min/max 0/116, read errors 0, write errors 0, ifcnt 12, reads 25520, writes 12, timeouts 0, DMA errors 0
Driver 2: position 21156, standstill, SG min/max 0/150, read errors 0, write errors 0, ifcnt 12, reads 25520, writes 12, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/18, read errors 0, write errors 0, ifcnt 12, reads 25519, writes 12, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 25523, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-06-20 17:02:58
Cache data hit count 908366785
Slowest loop: 2320.57ms; fastest: 0.10ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 101.3ms, write time 17.7ms, max retries 0
=== Move ===
DMs created 83, maxWait 168308ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 5179, completed moves 5179, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is ready with "M122 " 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 4378, send timeouts 4375, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 2430/0/0
Last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 1470.92ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
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.26
  WiFi MAC address f0:08:d1:02:ef:56
  WiFi Vcc 3.38, reset reason Power up
  WiFi flash size 2097152, free heap 22192
  WiFi IP address 192.168.178.106
  WiFi signal strength -57dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0