PS_ON not working?

[joehsmash]

hey there,

i just got my duet 2 wifi, and am currently re wiring my JoehBo 3d printer ( heavily modified robo3d r1) any ways on the ramps board i used to control the 850W ATX PSU via Pi and octoprint, the pi used to just bond out (ground) the PS_ON pin on the PSU to turn in on/off via M80/81 commands.

i expected this to work the same way, and perhaps im just not understanding the WIKI.

i currently have it setup so my EXT 5V jumper is installed and the INT 5V jumper is removed.

i have the EXT 5V header wired up |+5v |PS_ON|GND| as indicated by the wiring diagram, wiki, and documentation.

how ever when ever i send a M80 command via the GUI nothing happens. or via YAT it acknowledges the command but does not switch the psu

when i MANUALLY short PS_ON to GND it will turn on and everything is gold.

the board is currently powered via the ATX PSU via the +5SB and gnd. which means it is ALWAYS on unless i kill the power by unplugging it.

any ideas?

Joeh

[T3P3Tony]

@joehsmash what firmware version are you using? also can you share a picture/sketch of your wiring.

What you describe should work!

[joehsmash]

@T3P3Tony i agree with you. It should work

I couldn't figure out how upload pictures so I put them on imgur.

Duet https://imgur.com/a/p6Awzmh

When i manually short out that pson wire to amy of those green wires (ground) it activates my psu.

[joehsmash]

also i realized i never answered all of your questions, a m115 reveals

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2<LF>ok<LF>

[joehsmash]

i just updated the firmware to

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.05.1 (2020-02-09b1)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6

[joehsmash]

still no change, when i manually short the ps_on with the GND beside it on the header the psu fires up like it should.

its like theres a relay thats just not firing.

[joehsmash]

also, im not sure if it matters but i havent actually set up the duet yet according to my printer. it was just straight out of the box, mounted and setting up the psu

im going through the reprap config tool now.,

[joehsmash]

@T3P3Tony any ideas?

[joehsmash]

i am also finishing up the wiring, when ever i plug ANY end stop into the y axis it causes the DUET to crash. it reboots the minute i unplug it.

this board is starting to annoy me its been 4 days of messing around with it to get it working with one problem after another.

is there any actual customer support or are we just delegated to using this forum and waiting weeks for some one to possibly help us?

i mean its not like this board was cheap... it cost me 260 bucks. i could almost get a whole other printer for that.

[Danal]

@joehsmash said in PS_ON not working?:

ANY end stop into the y axis it causes the DUET to crash

That is symptomatic of a physically incorrectly wired endstop. Verify:

• I am assuming you have physical switches, and will run them "NC" or "Normally Closed".
• For NC on a three terminal switch, attach wire to the outer two terminals; leave the middle unconnected.
• Duet2 Wifi endstop connectors are shown below. Verify that the switch is connect to "GND" and "STOP". This is different than a lot of other printers, and connecting 3.3V and Gnd will cause exactly what you are describing

[Danal]

This post is deleted!

[Danal]

Also, I STRONGLY suggest you start a new thread for each new problem. Example: "Endstop Switches not working" will get a lot more attention as a thread than a dozen posts down the "PS_ON not working" thread.

P.S. I have no relation to Duet the company.

[joehsmash]

@Danal i gotcha, i have verified the wiring and changed the switches. Nothing has changed on my printer other than the duet. I have tested every switch with my meter as well.

[joehsmash]

i will try to redo the connectors tomorrow morning

[T3P3Tony]

Hi @joehsmash thanks, looks correctly wired like this:

.

Assuming that wiring worked previously (the 5V SB goes to the correct place?) then it should work. please can you share your config.g just in case there is something odd going on that is interfering with M80/M81. Also please try the following tests:

1. Once started up send M98 P"/sys/config.g" to run config.g again. sometimes errors in the config file are not reported in the console during startup so this will run it again and report any errors.
2. send M122 and post the results here, see if they are any different before/after the M80 command

P.S. You can cut and paste images into your post or use the "upload image" button to attach images.

[joehsmash]

@T3P3Tony here is my M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-7JKDA-3S86M-9BAZN
Used output buffers: 3 of 24 (17 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93140 of which 0 recycled
Exception stack ram used: 392
Never used ram: 11828
Tasks: NETWORK(ready,764) HEAT(blocked,904) MAIN(running,3824) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 01:44:08 ago, cause: power up
Last software reset at 2020-05-05 21:39, reason: User, spinning module GCodes, available RAM 11836 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 32.2, current 32.6, max 32.8
Supply voltage: min 2.0, current 2.0, max 6.5, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 2020-05-06 15:21:01
Cache data hit count 4294967295
Slowest loop: 5.34ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 159, MaxWait: 7ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 10, completed moves: 10, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 201.13ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 2
  WiFi firmware version 1.23
  WiFi MAC address bc:dd:c2:2d:64:61
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 23184
  WiFi IP address 192.168.1.44
  WiFi signal strength -42dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0

it appears that i was using the stock connectors on the end stops and as such were wired up in 3.3v to gnd positions.

i remade the connectors appropriately and the end stops are no longer causing me an issue.

still have the PSON issue, but i have circumvented that by just shorting it on all the time now. i will come back to this one.

current issue is VIN not in spec?

[joehsmash]

@T3P3Tony It looks like i have a blown fuse on my board.

the 7.5a mini blade fuse blew. i wonder what would have caused that. i know i head a kind of pop when i tried to turn on my hotend.

im not sure what would have caused it if it was the hot end, i just replaced the heater, and the thermistor. i also have replaced the line going straight back to the duet. there's only one connector just before the hot end if i ever need to disconnect it.

[dc42]

@joehsmash said in PS_ON not working?:

the 7.5a mini blade fuse blew. i wonder what would have caused that. i know i head a kind of pop when i tried to turn on my hotend.

Most likely you has a short circuit in the hot end heater or in the wiring to it.

[joehsmash]

@dc42

yes i discovered last night after i ripped my printer appart that there was indeed a short between the hotend wire and the heater cartridge. some kapton and a some silicone sleeves and all is well there!

[joehsmash]

@T3P3Tony i feel like im getting pretty close, i have come back to the original issue here is my M122 pre M80

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-7JKDA-3S86M-9BAZN
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93140 of which 0 recycled
Exception stack ram used: 384
Never used ram: 11836
Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3752) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:08:16 ago, cause: power up
Last software reset at 2020-05-07 00:48, reason: User, spinning module GCodes, available RAM 11780 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 29.9, current 30.3, max 30.5
Supply voltage: min 0.6, current 0.7, max 0.7, under voltage events: 1, over voltage events: 0, power good: no
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-05-07 16:34:14
Cache data hit count 1617214182
Slowest loop: 1.16ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 158, MinFreeDm: 158, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 4, completed moves: 3, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 1 in use
Movement lock held by http
http is idle in state(s) 1 8
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 201.11ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 1
  WiFi firmware version 1.23
  WiFi MAC address bc:dd:c2:2d:64:61
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 23112
  WiFi IP address 192.168.1.44
  WiFi signal strength -45dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0

and here it is post M80

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-7JKDA-3S86M-9BAZN
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93140 of which 0 recycled
Exception stack ram used: 384
Never used ram: 11836
Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3752) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:10:46 ago, cause: power up
Last software reset at 2020-05-07 00:48, reason: User, spinning module GCodes, available RAM 11780 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 30.1, current 30.8, max 30.8
Supply voltage: min 0.6, current 0.7, max 0.7, under voltage events: 1, over voltage events: 0, power good: no
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-05-07 16:36:45
Cache data hit count 2209121988
Slowest loop: 2.06ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 158, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 4, completed moves: 4, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 202.11ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 2
  WiFi firmware version 1.23
  WiFi MAC address bc:dd:c2:2d:64:61
  WiFi Vcc 3.39, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 21648
  WiFi IP address 192.168.1.44
  WiFi signal strength -44dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0

not much has changed