Topics created by dhusolo

@Alijambo73 I switched the pwm converter to a 24V power supply and switched to using out2 then played with it until I got to the point that it can reach 24,000 rpm and when set to 12,000 rpm I'm getting 12,500. I ended up adjusting the hz to 400 to acheive this.

M950 R0 C"out2" Q400 L0:24000 K0:1

I would love to get it dialed in more if anyone has any suggestions.

@dhusolo yes that should work.

@dhusolo you could try G38.2 moves instead which are protected and will stop when the probe is triggered.
The millenniumOS plugin has it working I believe and that's aimed for CNC use. It's still a work in progress though

@droftarts Genius. That fixed the problem. Thanks!

@dhusolo You may want to download it again, Bluetooth is enabled again by default in the latest image. In previous ones it was turned off.

@GeneRisi HTTP: https://github.com/Duet3D/RepRapFirmware/wiki/HTTP-requests DSF 3.5 supports those requests, too.

@jay_s_uk Go figure I completely forgot to change that. That worked thanks.

I found the single 5V pwm output limiting, plus to get the most precise control, an analog 5v fed to the CPAP blower driver board is most accurate. Tried a few ways to do that and settled on this board https://www.amazon.com/dp/B079BH3SHX?psc=1&ref=ppx_yo2ov_dt_b_product_details -- it's powered by 24v, will take the pwm output of a regular fan output and create a clean 0-5v analog output. If you run it at 100-200hz you can get the low end to be around .5v, and that's as slow as the CPAP blower can go. I can go the full spectrum and have perfect output control. Not sure of another source for these boards, but I will use them for duet and for klipper configs since they're simple and the best part is the fan control is super accurate.

@droftarts It simply echoed

M106 P3:4 H2 T20

But you were correct. I was able to get them both to run with

M106 P3 H2 T20 M106 P4 H2 T20

@chrishamm I found an old USB to TTL adapter. I connect the USB to the Duet's RPI USB port.
I've got the it connected by
TTY RX to Pi TX
TTY TX to Pi RX
TTY GND to Pi GND

I have the jumper on the tty in the 3.3v setting

On the pi listening I ran terminal with

cat /dev/ttyS0

On the duet pi I ran

stty -F /dev/ttyUSB0 115200 /opt/dsf/bin/ModelObserver -q -f "heat/**|tools/**" > /dev/ttyUSB0

This is the output
1b9f91b8-d7ee-4900-b6b5-912538fab252-image.png

@dhusolo the object model changed between 3.3 and 3.4 are documented at https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x#reprapfirmware-340.

@fcwilt Agreed. I planned to incorporate it in my build and was disappointed when I couldn't use it. However after enough tweaking I think I'm in a better place. Upgrading to the PTFE coated leadscrews helped quite a bit. I also figured out the leadscrew offsets were slightly off. Once I changed the config results started to improve. Even more so after using 4 points to calculate the leadscrew offset. This was my last G32 without the spring steel sheet on.

8bae2ed7-b959-4195-ac48-706a0157e10c-image.png

@dhusolo said in PSON Macro not working as intended.:

Anyone have any ideas what's going on?

Your trigger macro works more or less "by accident", depending on the timing of config.g as @dc42 points out, and depending on the bouncing behaviour of your button. In addition (and as @dc42 says), you forgive the chance to check power before you turn it on, regardless of state, which, in turn, ultimately runs the config.g.

I think you should rework your macro:

wait 50-100 ms for the button to debounce, then, check its state again: if it is open, quit the macro with M99. if ATX power is off, put it on, then, run your config.g else, wait another second or two (whatever you consider a long press), then check its state: if it is still pressed, turn ATX power off.

Depending on your timings (aka "button press habits"), you can add a loop to wait for the button to be released; this would then be called after steps 2. or 3., regardless of which branch you took.

@dc42 Yes
29b0c3c1-5bf1-4009-9726-d603ec4da891-image.png

@dc42 I reran it like you suggested. These are the results

G1 X5 G4 S2 G1 X105 F20000 M400 M956 P20.0 S1000 A0

70e576cc-43b1-487c-aeca-9380c3a239b7-image.png

G1 Y5 G4 S2 G1 Y105 F20000 M400 M956 P20.0 S1000 A0

6970f7e9-520c-47b7-9241-66f17fd42094-image.png

@dhusolo PanelDue uses 3.3V signal levels, Arduino Nano uses 5V. If you use a level shifter then you probably don't need to change the resistor.

@dc42 said in Neopixels Driven off RPI:

I guess it should be possible to use the shared SPI channel and an external gate to drive NeoPixels on Duet 2.

That sounds promissing!
The ext. gate for level shifting?
Do I have to put the request in the firmware wishlist section?

@o_lampe I'm a moderator with the BLV printing community. So anything I do I have to make sure it stays close to the standard BOM. The BOM calls for a Duet 2 WiFi. Eventually we'll move it to ESP8266 but at the moment it's easier to maintain it on an Arduino.