Posts made by piranha32

@dc42 Thanks for response. I have a Duet2 board, so CAN is not an option. I'm planning to build the pump controller, and I'm looking around what interfacing options are available.

@o_lampe That's one of possibilities, however my goal is not to have the information in a digital format, but to control the pump. It is easier to just integrate the PWM signal and use micro's built-in ADC, and should be precise enough. Having this information in digital format would make make implementation simpler, and I hoped there was a configuration option which enables it.

Hi,

I would like to use for part cooling a mains powered air pump. It needs a phase angle controller to control the air flow, so I can't use the PWM signal from Duet board directly. I can convert it to a DC-ish voltage, however it would be much easier if the board could talk to the pump controller via some kind of serial protocol.
I'm using Duet2 WiFi board. Is there a way to tell the firmware to send the fan speed information in a digital format (via UART, SPI, I2C, or any other digital bus)?

@droftarts said in My Duet2WiFi stopped responding:

@piranha32 could be that you inadvertently shorted the erase pins, then on next reset (possibly when endstop shorted) the firmware got erased.

It is possible, but highly unlikely. All the wires I used were insulated, the board was sitting on a non-conductive surface, and I don't use the endstop connectors right next to the erase pins.
I'm worried that it may happen again when the board will be installed in the printer, so I'd like to understand what's happened, and protect against it.

@dc42 said in My Duet2WiFi stopped responding:

@piranha32 said in My Duet2WiFi stopped responding:

Thanks, it fixed the issue. Verify on the firmware before erasing showed >90 pages with errors. Do you have an ideas on what might have caused the failure?
Possibly static discharge to the +3.3V or +5V rail. Are your stepper motor cases and hot end metalwork grounded?

At the moment there is no grounding connection. ESD was my first suspicion, but I find it very weird that a minor discharge would wreck so much havoc on the firmware in flash (over 90 pages did not pass verification before erase).

@oliof said in My Duet2WiFi stopped responding:

@piranha32 endstop pin order is different on duet boards compared to typical RAMPS derivatives, see https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Connecting_different_types_of_endstop_switch

I wired the connectors according to the description of the pinout. The status LEDs were showing correct state, status is read correctly on all 3 inputs when I use a jumper wire, so the most likely reason why the controller doesn't read the endstops properly is incorrect voltage level from the sensor in "low" state. I'm going to add a buffer circuit between the sensor and the board, and I hope this will solve the problem.

Thanks, it fixed the issue. Verify on the firmware before erasing showed >90 pages with errors. Do you have an ideas on what might have caused the failure?

Hello,

I have a problem with my Duet2WiFi board. The board is brand new, I've got it a couple of days ago to replace the original, proprietary control board in my printer.
For testing I used a Thinkpad power supply outputting 19V (heaters are disconnected, the power supply can supply enough current to power the rest of the system). I have upgraded the firmware to 3.1.1. The printer uses optical endstop sensors, and I could not make them work. The status LEDs on the board were indicating correct state of the switches, but software was registering state changes only on Z axis.

To verify whether the problem was with the sensors or the inputs, I disconnected the switch connectors (with power disconnected), and connected a jumper wire to one of the inputs to check how it responds to supplying 0 and 3.3V from the pins on the sensor connector. Unfortunately at this point the board stopped responding. I'm not sure whether it did not come on after connecting the power, or when I was connecting the jumper cable to the 0/3.3V pins. I was watching the input status indicators on the web interface, and noticed the "Connecting" popup still on when I started to investigate why I don't see any changes.

The serial USB interface still works, disappears when I press the RESET button, so I assume the CPU works. The DIAG LED stays on all the time, the serial console does not respond to input, and the board does not respond to IP pings.

I would appreciate an advice how to debug and fix the issue.