Posts made by Leblond

allora,ho rifatto la sd della stampante ed ora funziona

@DavidG_68kg_PLA confermo che anche la rc3 ha lo stesso problema, la sonda si schianta sul piano, ho notato che il sensore a video legge anche in object model viene letto il sensore, ma quando si lancia la calibrazione della delta si schianta e si trascina il sensore

@Phaedrux
Thanks guy, the problem was that I didn't know that when you do a G32 that then it goes to call the BED.G
the probe does not activate in the moment of fast descent towards the floor, but it activates in the moment in which it proceeds with the probing coordinates, I thought that the probe activated in the moment in which the G32 command is given, while if the command is given G30 followed by the coordinates the probe is active

@Phaedrux
Funziona tutto

@Phaedrux
hi so the settings i used are:

M558 P8 C"!zprobe.in" H10 F120 T6000 reset to initial dwc 0, if I put my hand underneath and press it it goes to 1000.

M558 P8 C"^zprobe.in" H10 F120 T6000 result in initial dwc 1000, if I put my hand below it goes to 0

I made a G30 and it works but I don't understand why when I go to make a G32 it doesn't work

@Phaedrux bed.g

@Phaedrux

@Phaedrux
Inglese
si l'ho provato e funziona, da 0 a riposo a mille quando lo premo, e ho provato anche al rovescio da 1000 a 0 sempre manualmente e funziona, nel momento in cui vado a sondare il letto se non metto la mano sotto il probe non si ferma e si schianta sul letto, non ne riesco ad uscire, ho provato anche a cambiare l'input di ingresso ed e uguale al precendente, domaninmattina ti posto il bed.g
yes I tried it and it works, from 0 at rest to a thousand when I press it, and I also tried it backwards from 1000 to 0 always manually and it works, when I go to probe the bed if I don't put my hand under the probe it does not stop and crashes on the bed, I can't get out of it, I also tried to change the input input and it is the same as the previous one, tomorrow morning I'll post the bed.g

@Phaedrux I took +5v on the expansion connector, GND+Zprobe on the ZPROBE connector

@Phaedrux X2 Y2 Z2 works, but I have a serious problem that I can't solve, pressing the switch manually on the screen it shows me that it works but once I start probing the work surface the nozzle crashes on the surface

@Phaedrux
ok I'll try tomorrow

@Leblond
Problem 1:
I can't home the printer correctly without getting an error like (G28
Error: G0/G1: target position not reachable from current position)

Problem 2:
I can't use the original printer probe, the connections are correct and the program sees it as such, but the printer doesn't stop even if I manually activate it

Hi all, I swapped the FLSun SR delta printer card with a wifi duet2, but I can't configure it, could you help me? Thank you

my configuration:

RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F23T0-6JTD0-3S06T-TYAJF
Used output buffers: 1 of 26 (13 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 74544 of which 24 recycled
Never used RAM 13580, free system stack 134 words
Tasks: NETWORK(notifyWait,14.8%,237) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,294) MAIN(running,85.1%,408) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:26:46 ago, cause: software
Last software reset at 2023-02-26 15:13, reason: User, GCodes spinning, available RAM 13604, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 30.5, current 31.1, max 32.0
Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2023-02-26 15:40:38
Cache data hit count 4294967295
Slowest loop: 10.29ms; fastest: 0.15ms
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 4.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 4, maxWait 26075ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 12, completed 12, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], 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
=== Network ===
Slowest loop: 15.86ms; 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.26
WiFi MAC address 84:0d:8e:b3:b4:8a
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 26208
WiFi IP address 192.168.1.9
WiFi signal strength -69dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

homedelta.g config.g

@fcwilt ok grazie

@arnold_r_clark said in proximity sensor PNP:

Connect the sensor output wire to one end of a resistor (call this R1), and connect one end of another resistor (call this R2) to GND on the Z-probe connector. Connect the free ends of R1 and R2 together and to the IN pin of the Z-probe connector.

that is, as in the picture?

@fcwilt Forgive me you are right I have described the problem without giving you information.
My card is a duet 2 wifi v1.04 with firmware 3.4.1
the printer is a corexy tronxy
the voltage is 24v except for the bed which is 220v
yes I used them a couple of years ago but I don't remember anything anymore
the problem as I described at the beginning of the post is that the aluminum base of the printer is not made for an inductive sensor, so having the PNP sensor capicitivo and I wanted to exploit it

I accidentally got a PNP capacitive adjustable proximity sensor instead of the usual NPN.
Having mounted a magnetic bed about 4mm high and a 6mm heated plate of non-deformable aluminum at high temperatures milled on both sides and already having an inductive sensor NPN XY-08n "Tronxy" which works quite well "when it comes to normal aluminum or steel "and connected on the fan connector always active as 24v power supply and signal on Z_PROBE_IN, but it measures too little 0.8mm and forces me to remain dangerously low in the printing phase, I had already used the PNP sensor in the past with excellent results, now what I ask you is there a figure that shows the functioning electrical connection of the PNP sensor?, I looked at some post in particular the one who realized after burning the card that patience is the virtue of the strong , can you help me to have a diagram of how it should be connected without damage?

even the temperatures will have to lower by 5 degrees, petg mold at 230 degrees the print bed 75 degrees

@Phaedrux

probable, in fact I put my hand back to the configuration and I lowered the jerk from 1000 to 600, then once another piece is printed if I get improvements I post a photo

and it never happened to me, at least until recently