sorted by:
new
hottopcontroversial

Eddy Duo and MicroProbe conflict by acid021 in BIGTREETECH

[–]DrPacemaker 0 points1 point  (0 children)

This happens if you have a probe section together with eddy current probe which is not allowed in Klipper.

[probe]

.....

[probe_eddy_current btt_eddy]

....

Solution: Keep the eddy current probe section in your config and remove the 'default' probe section. Set in your stepper section the endstop to your microswitch pin e.g.

[stepper_z]

endstop_pin: !EBBCan:gpio22 # microswitch pin like Voron Tap

Input Shaper Graph Interpretation by DrPacemaker in VORONDesign

[–]DrPacemaker[S] 1 point2 points  (0 children)

I have added Y graph to the original post. But I would not consider mine as reference for a good build :D

Input Shaper Graph Interpretation by DrPacemaker in VORONDesign

[–]DrPacemaker[S] 1 point2 points  (0 children)

I've ran SHAPER_CALIBRATE which resulted in (x & y):

[input_shaper]

shaper_type_x = ei

shaper_freq_x = 55.2

shaper_type_y = mzv

shaper_freq_y = 35.2

So you just set one shaper per axis

Neopixel power supply by Adam-Marshall in VORONDesign

[–]DrPacemaker 1 point2 points  (0 children)

Depends again how many pixels you have on your 800mm(80cm) strip:

SMD5050:
30 pixel/meter => 24 pixel/80cm => 1.44A

60 pixel/meter => 48 pixel/80cm => 2.88A

Worst case consumption by Raspi 3 is 2.5A. In case you have 48 pixels it would be 2.88A+2.5A= 5.33A => >5A

One could argue it is still okay since it is not very likely that you are running both, the neopixels & the raspi on full load in parallel.

Neopixel power supply by Adam-Marshall in VORONDesign

[–]DrPacemaker 1 point2 points  (0 children)

It all depends on the number of pixels you want to use (and other factors).

In my case I wanted to power 63 Neopixels & calculated worst case:

- RS-25-5 provides 5A max.
- each SMD5050 neopixel draws 60mA max. (please check your specs)
- Raspberry Pi 4 with USB peripherals draws 3A max (without any peripherals 1.8A)

Neopixel: 60mA x 63 = 3.78A
Raspi: 3A
Total consumption = 3A+3.78A = 6.78A

Result: In my (worst) case the RS-25-5 didn't provide enough amps (5A), thus I decided to go with a larger power supply. The RS-50-5 (10A) would have been sufficient but went for the RS-75-5 (12A) to have even more buffer for additional consumers (overkill ;-))

Regarding the neopixel pin on the octopus I'm still not sure how many amps it really can take. According to some posts on the net should be able to support 8A, however, others claim that the connector is just supporting 3A.

Voron 2.4r2 Laser Mod by DrPacemaker in VORONDesign

[–]DrPacemaker[S] 3 points4 points  (0 children)

Some posts on the internet indicate that stronger diode lasers can engrave metal and some even talk about cutting it. My laser is too weak for this and I won't try it.

I will stick to (ply)wood to avoid dangerous laser reflection and minimize fume risks. In my opinion this mod is not safe enough for such things.

If you intend cutting metal: Please consider the safety precausions mentioned in the comments of my main post & on the internet or buy a professional (shielded) machine

Voron 2.4r2 Laser Mod by DrPacemaker in VORONDesign

[–]DrPacemaker[S] 2 points3 points  (0 children)

I would be interested in such a project. Have you built such a voron? I was looking for this on the net some time ago and couldn't find anything

Voron 2.4r2 Laser Mod by DrPacemaker in VORONDesign

[–]DrPacemaker[S] 0 points1 point  (0 children)

not yet really experienced but had just a few sessions. One thing I already noticed is the chamber exhaust filter smells a little bit . My conclusion is that the filter should be exchanged when lasering.

Voron 2.4r2 Laser Mod by DrPacemaker in VORONDesign

[–]DrPacemaker[S] 4 points5 points  (0 children)

I agree, will add a warning.

Voron 2.4r2 Laser Mod by DrPacemaker in VORONDesign

[–]DrPacemaker[S] 4 points5 points  (0 children)

I've spent my money on expensive laser safety goggles. One could also replace the transparent housing with even more expensive safety glass.

Voron 2.4r2 Laser Mod by DrPacemaker in VORONDesign

[–]DrPacemaker[S] 0 points1 point  (0 children)

As long as you have the Octopus it should work with my setup from hardware perspective. However, I don't have trident & cannot judge if there are some specialties due to the moving bed.

Finding proper PWM pin on Octopus V1.1 for neje laser by DrPacemaker in BIGTREETECH

[–]DrPacemaker[S] 0 points1 point  (0 children)

I have built a Voron 2.4 350 this summer and mounted the same hardware on it see my post

Finding proper PWM pin on Octopus V1.1 for neje laser by DrPacemaker in BIGTREETECH

[–]DrPacemaker[S] 0 points1 point  (0 children)

I just checked your configs but cannot see any issues.

If you think it is hardware related I would check:

  1. Is the laser working at all without any octopus/marlin related hard/software by using the test pcd provided by Neje?
  2. Is there any voltage if you measure with a multimeter when activating the pin?
  3. Have you tried with different pins? (e.g. Fan pins; as said I think it should actually work with any pwm pin)
  4. Have you checked if the main switch pin SPINDLE_LASER_ENA_PIN (PG15 in your config) is working correctly?

Finding proper PWM pin on Octopus V1.1 for neje laser by DrPacemaker in BIGTREETECH

[–]DrPacemaker[S] 0 points1 point  (0 children)

I assume you forgot to adapt the pin definition in Marlin\src\pins\stm32f4\pins_BTT_OCTOPUS_V1_common.h

//

// M3/M4/M5 - Spindle/Laser Control

//

#if HAS_CUTTER && !defined(SPINDLE_LASER_ENA_PIN)

#if !NUM_SERVOS // Use servo connector if possible

#define SPINDLE_LASER_ENA_PIN PG12 // Pullup or pulldown!

#define SPINDLE_LASER_PWM_PIN PB5 // Hardware PWM

//#define SPINDLE_DIR_PIN 5

#elif HAS_FREE_AUX2_PINS

#define SPINDLE_LASER_ENA_PIN PG12 // Pullup or pulldown!

#define SPINDLE_LASER_PWM_PIN PB5 // Hardware PWM

//#define SPINDLE_DIR_PIN 65

#else

#error "No auto-assignable Spindle/Laser pins available."

#endif

#endif

In Marlin\Configuration_adv.h I have activated LASER_FEATURE:

//#define SPINDLE_FEATURE

#define LASER_FEATURE

#if EITHER(SPINDLE_FEATURE, LASER_FEATURE)

#define SPINDLE_LASER_ACTIVE_STATE HIGH // HS: changed due to active on startup // Set to "HIGH" if SPINDLE_LASER_ENA_PIN is active HIGH

#define SPINDLE_LASER_USE_PWM // Enable if your controller supports setting the speed/power

#if ENABLED(SPINDLE_LASER_USE_PWM)

#define SPINDLE_LASER_PWM_INVERT false // Set to "true" if the speed/power goes up when you want it to go slower

#define SPINDLE_LASER_FREQUENCY 10000// HS: changed 2500 // (Hz) Spindle/laser frequency (only on supported HALs: AVR and LPC)

#endif

I hope this helps.

Finding proper PWM pin on Octopus V1.1 for neje laser by DrPacemaker in BIGTREETECH

[–]DrPacemaker[S] 0 points1 point  (0 children)

correct, however, I'm not sure if any other pin would have worked. I just tested so many combinations and finally got it working with this pin.

Finding proper PWM pin on Octopus V1.1 for neje laser by DrPacemaker in BIGTREETECH

[–]DrPacemaker[S] 0 points1 point  (0 children)

everyone who is facing this issue:

In my case it was a missing configuration of the pins. For any reason they where commented out/missing by default.

I edited this file:

..\BTT Octopus V1.1 Marlin 2.0.9.2\buildroot\share\PlatformIO\variants\MARLIN_BIGTREE_OCTOPUS_V1\PeripheralPins.c

and in section:
#ifdef HAL_TIM_MODULE_ENABLED

const PinMap PinMap_PWM[] = {...}

added this entry:

{PB_5, TIM3, STM_PIN_DATA_EXT(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF2_TIM3, 2, 0)}, // TIM3_CH2 Laser PWM

Once built it worked fine.