Topics created by GeorgeM

@phaedrux I'm also interested in this. It'd be nice to have an easy way to focus the laser... Currently I just set it to low power with low speed, but that's not optimal.

If there's no firmware way is there an easy macro that would work? I'm on rrf 3.1 I think.

Thanks!

Thank you. Looked right past that.

@bot said in Could Duet2 cause this? CoreXY skew.:

@GeorgeM that’s funny! Glad you figured it out.

If you would still like to adjust scaling, you can use the M579 command.

Thanks bot, that is my next move.

I do appreciate all your attention to this. You were able to get me corrected about the U parameters. That's a win.

I do need to start a new thread about why my laser wont operate from gcode commands.

@GeorgeM said in Duet2 WiFi using heater pins for fans?:

specs

insufficient data. yes it will trigger at 3.3v, but no info on impedance or source/sink current at 3.3v, only max current. 2.8v logic threshold leaves very little room for adding a series resistor to limit the current.

i'd measure the current at 3.3v or go with a buffer for good measure.

@Phaedrux said in Sanity check on Fan setup:

M98 Pconfig.g

Thank you for replying.
First off I redid some of the wiring for the fans. Instead of using VIN power I am now supplying the power from a buck to reduce the 24v to 12v via the middle pin on the V Fan Jumper. I also found a loose connection on the Fan0.
So after that Fan0 and Fan1 are working as they are supposed to. However I am back at not getting Fan2 to control the laser. Even when I hook up a simple fan it does not work. Moving the slider on the Dashboard produces nothing. And when I send m106 commands the slider moves but the fan does not. (By the way I checked with two different fans, both know to be working).

M98 produces nothing
Here are the m106 status

6/17/2020, 5:41:58 PM m106 p0
Fan 0, speed: 0%, min: 10%, max: 100%, blip: 0.10
6/17/2020, 5:41:54 PM m106 p1
Fan 1, speed: 100%, min: 10%, max: 100%, blip: 0.10, temperature: 45.0:45.0C, sensors: 1, current speed: 0%:
6/17/2020, 5:41:50 PM m106 p2
Fan 2, speed: 0%, min: 10%, max: 100%, blip: 0.10

And here is the fan part of my config.g
; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"!fan2" Q1000 ; create fan 2 on pin fan1 and set its frequency
M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off

Lastly here is the M122:

6/17/2020, 5:36:13 PM === Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SJ-6JKD4-3S46L-TUW7D
Used output buffers: 3 of 24 (20 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93984 of which 60 recycled
Exception stack ram used: 264
Never used ram: 8784
Tasks: NETWORK(ready,368) HEAT(blocked,1216) MAIN(running,1816) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:41 ago, cause: power up
Last software reset at 2020-06-17 10:03, reason: User, spinning module GCodes, available RAM 8784 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 31.8, current 36.0, max 36.0
Supply voltage: min 23.7, current 23.8, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
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-06-17 17:35:47
Cache data hit count 66412690
Slowest loop: 7.78ms; fastest: 0.14ms
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 16.4ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 23.25ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 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.23
WiFi MAC address cc:50:e3:6a:85:90
WiFi Vcc 3.35, reset reason Unknown
WiFi flash size 4194304, free heap 24448
WiFi IP address 192.168.1.73
WiFi signal strength -67dBm, reconnections 0, sleep mode modem
Socket states: 4 0 0 0 0 0 0 0

I don't see where I am off.

George

Thanks. I was going to try that today

Thank you so much. That worked. And your explanation was very helpful.

@T3P3Tony Thank You. That works.

@dc42 On the driver I can set the control to be either high or low. Would that be the same as using the 74HCT02 chip?

@Phaedrux Second day and it's still holding pretty steady so good to go.
Thanks for all you input.

👍 Good to hear

@georgem said in Solved-First time setup. Cant get steppers working properly:

Thanks bricor
It actually was wired correctly. What I found is that when I was switching X and Y one of the pins for Y had pulled loose. Once I reconnected that I was able to get them operating correctly.
This is my first post here. How do I edit the title to show it is solved?

Click on Topic Tools and select Ask As Question. Then click on Topic Tools again and you will see a new option Mark As Solved.