Digital input problem's / pwm signal output

matej1006

@matej1006 here is also diagnose

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.4+1 (2022-11-15 17:36:33) running on Duet 3 MB6HC v1.02 or later (standalone mode)
Board ID: 08DJM-9P63L-DJMSS-6JTD0-3S46L-9UFZ8
Used output buffers: 3 of 40 (18 max)
=== RTOS ===
Static ram: 152740
Dynamic ram: 100312 of which 172 recycled
Never used RAM 97448, free system stack 200 words
Tasks: NETWORK(ready,29.7%,218) ETHERNET(notifyWait,0.1%,445) HEAT(notifyWait,0.0%,344) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.1%,799) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,7.0%,91) MAIN(running,62.9%,925) IDLE(ready,0.3%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:46 ago, cause: power up
Last software reset at 2023-07-25 18:49, reason: User, GCodes spinning, available RAM 97448, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 127
MCU temperature: min 25.1, current 31.3, max 31.4
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.8, current 12.2, max 12.5, under voltage events: 0
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, mspos 8, reads 64014, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 64015, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 64015, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 64016, writes 13 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 64016, writes 13 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 64018, writes 11 timeouts 0
Date/time: 2023-07-25 19:05:26
Slowest loop: 3.98ms; fastest: 0.06ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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
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 463, received 3512, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 621, free buffers 50 (min 49), ts 233/232/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 3.60ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
State: active
Error counts: 0 0 0 1 0 0
Socket states: 2 5 2 2 2 0 0 0
= WiFi =
Network state is disabled
WiFi module is disabled
Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

infiniteloop

@matej1006

that i will get more heat out of water

… and less heat away from the hotend. So it’s better to improve the cooling than to reduce the flow.

deckingman

@matej1006 said in Digital input problem's / pwm signal output:

............... for emergency stop on main board (6HC). i have 3.3V connected to COM on emergency contact and than signal back to io0.in................................

.............................................
M950 J1 C"io0.in" ; Define Emergency endstop - emergency stop switch condition
M950 P4 C"io0.out"
M581 P1 S0 T2 ; Define action to be taken with activation of emergency stop switch
M582 T2 S0 ; set trigger #3 pending unconditionally

If I've read that correctly, you want to detect when 3.3 v goes to to pin io0.in. So your trigger (M581) ought to be set to detect a rising edge (inactive to active) which is S1 not S0.

matej1006

@deckingman no i want to when it goes form 3.3 to 0. i did add a resistor 10kohm to gnd and io0.in. isn't helping and also i did try pull up in code nothing was working.

matej1006

@infiniteloop ok yeah that far i wasn't thinking yeah

deckingman

@matej1006 Here is what I have which triggers two macros based on the presence or otherwise of 3.3V on an io pin.

M950 J1 C"0.io3.in"
M581 P1 T2 R0 S1; io from low to high
M581 P1 T3 R0 S0; io from high to low

Other than using a different io pin, the only differences I can see between your code and mine is that I explicitly use board 0 (C"0.io3.in) but it should default to board zero if none is specified, and I use R0 to specify that the trigger should be acted on at any time rather than when printing from the SD card, but again, that should be the default behaviour. Maybe you have a wiring issue?

For info, the first line of my trigger2 file is M118 S"Trigger2" and the first line of my trigger3 file is M118 S"Trigger3" so I can easily see when they trigger.

dc42

@matej1006 you should connect your NC switches (or 2 switches in series) between the IOx_IN pin and ground. Leave the 3.3V pin not connected. See https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_endstops#microswitch.

matej1006

@dc42 damm i missed this info sorry

matej1006

@infiniteloop so now i have temp. set to hold between 20 to 25 C.
what would you recommend to set between 50 to 60 C

infiniteloop

@matej1006

so now i have temp. set to hold between 20 to 25 C.
what would you recommend to set between 50 to 60 C

You didn’t tell us, but I assume you want to cool your hotend. In this case, the effective temperature above the heatbreak is influenced by many factors: temperature of the heater, efficiency of the heatbreak, retraction settings, temperature of the surrounding air (think of a hot summer or of a heated chamber), heat transfer rate of the cooling jacket, …

Frankly, I cannot calculate any of these properly, so for me, it’s try & error. My pump is thermostatically controlled, it steps-in at 35 °C and runs full power at 65 °C (back flow). With these settings, I reliably avoid any heat creep. But with your system, you might need to apply different values.

matej1006

@infiniteloop yes ok that i know. i just didn't know what cca temp i would like to have in system running.