From categories:
page 1123...next »

I don't see AVCC in the pinout diagram. Could somebody please point this out to me. Thanks! :)

I had this same problem and the solution is to supply voltage straight from the + side of your dc power to the board to the brown "V" wire for each of these endstops. These endstops are NPN type proximity sensors and will need 12 to 30 volts to work. My MKS V1.4 supplied 5V which worked for some reason but on the Smoothie V1.3, the V pin on the endstop plugs only outputs 4.78V which just won't allow the endstop to operate properly- the led just lit dimmly. Once I pulled he brown "V" wire loose from it's white three pin connector and supplied 24volts to it, it began sensing normally again.

This forum is moving to : https://forum.makerforums.info/c/controllers/smoothie

All data from this forum and from the old Google+ community have been moved there, please use the new forum

I had a similar problem. My prints were coming out skewed on an angle like I was losing steps, but I'm running servo motors that can't skip steps. It turned out to be my pulse length was to long. I was using a 4 microsec pulse and my driver was skipping a step on ever direction change skewing my prints. I shortened the pulse length and the problem went away. I'm not saying this is what's happening to you, but it might save someone some frustration.

Hi - I’m a new smoothieware user having issues with getting the zprobe to work for 3 point bed levelling. I’m using a BLTouch 3D on a Cetus3D printer running the TinyFab uC with smoothieware firmware.

I can post the config later but initially I had a few question about the config options.

Does the leveling point in the config below define were the probe pin touches the build plate or where the nozzle is ?

leveling-strategy.three-point-leveling.point1        10,10   # The first probe point (X, Y)
leveling-strategy.three-point-leveling.point2        170,10    # The second probe point (X, Y)
leveling-strategy.three-point-leveling.point3        170,170      # The third probe point (X, Y)

With the offset config does this define the probe distance from nozzle or nozzle from probe ? It would change the sign of the number.

leveling-strategy.three-point-leveling.probe_offsets 0,0,0          # The probe offset from nozzle, must be X,Y,Z (Z should always be 0)

The probe sits 20mm behind the nozzle in the Y axis (toward 0) and 40mm behind the nozzle in the X (axis) toward its zero. So is the offset -40,-20,0 or 40,20,0 ?

The problem I have is that whilst I can move the print head to each of the coordinates for point1, point2 and point3 as soon as I issue a G32 command via the web interface the build plate crashes into the end of the printer.

The printer build plate can go max 180,180mm so I’m not sure why the G32 command with coordinate settings for a max cartesian coordinate of 170,170 could possibly cause the linear bearing to try and run off the end.

I have spent 6 hours tonight trying to work it out but I’m scared I’m going to ruin my printer.

Zprobe issues by ilium007ilium007, 29 Apr 2019 16:06
2 layer pcb
j_tmecj_tmec 25 Apr 2019 18:01
in discussion Smoothie Firmware / General » 2 layer pcb

hello all
is there any 2 layer pcb design for smoothieboard with or with out internal stepper drivers?

2 layer pcb by j_tmecj_tmec, 25 Apr 2019 18:01

I have a Smoothieboard 5X v1.0b, couple years old but hasn't been powered on until now. USB powers up the CPU & LEDs blink properly and I can flash firmware no problem. Latest firmware installed as of a couple days ago.

Disconnect USB, then apply 24V to the VBB input on the big jack and nothing. No lights, no nothing. Double checked the polarity, initially got it backward but for only a second or two before shutting down and re-checking the wiring diagram. I do have the RECOM 5V regulator installed, and tried two different units, with the same issue.

What component would likely blow up on a reverse 24V situation?

Thanks in advance…

So a little while back I ordered a smoothie board 0 with the intention to build a 3d printer with it. But when buying it I originally thought that the board came with mosfets but not motor drivers, but upon receiving it I realized it didn't have mosfets to turn the hotend or heated bed on. So my question is what do I need to get in order to have a hotend and a thermistor plugged into it?

Smoothieboard 0 by greengoatmangreengoatman, 13 Apr 2019 22:48

Hi
I'm quite novice in Smoothiexxx
I have setupo alpha_current, beta_current, … epsilon_current to match the current driven by the steppers of my machine (1.0 Ams)

The weird thing is that I power cycle Smoothieboard, I do some quick movement tests and after like 1 or 2 mins there's an odour like ozone, the temperature of the dissipators of the drivers rise so that you can't touch them, like 80-90ºC and the temperature of the back plate of the steppers gets veeeery high lie 70-80ºC

I'm thinking to use my 30 days money back warranty… but I'd like to have some help for this

There are other issues like endstops working when I home only… If I jog, the endstop switches are triggered by the printer but the Smoothieboad permits me to move the motor regardless of the endstop triggered.

I have a Smoothieboard v.1.1
The printer is a GEEETech i3 PRO B

Could you give some advice?

Smoothieware stable build.

FWIW I have :
soft_endstop.enable true
soft_endstop.halt true
soft_endstop.z_min 0
gamma_max is 104

all homing and otherwise perfect running works. but.. being a delta , needs protection in case negative Z axis request is sent to it, otherwise will try and smash the (pnp) head through the deck. None of the endstop points seem to work. I have verified in get-config on console that the endstops are enabled and the zmin number is what I expect it to be….

I had a good look at the source, My first thought was that soft end stops might have been tested AFTER machine machine arm computations.
Nope in, robot.cpp etc , soft endstops are checked before geometry computations for the delta, so that should be OK. Code looks fine.

is my next step doing a debug build so the printfs work ? or load up GDB in jtag ? am STM32 familiar so :LPC cant be too hard…

Or do I not correctly understand how they are supposed to work :-)
-glen

I use LCDA357H driver with Nema 23 3Nm motors.
Now I turned it to 1600 imp/rev
Yes config is really old, but firmware is last version.

Great thanks for the detailed explanation.
I really did not consider the frequency 100 000.
I made a step per mm 32. (16 does not work correctrly)
The speed has risen to 140,000 mm/min.
After 1000 movements at 0.5m, the error was about 0.01mm.
This is acceptable for my pick-up robot on first time)).
Next time I’ll really be designing it with servomotors.

Just got a new second hand corexy style printer. I have taken most of it apart and put it back together. I had it working, but just replaced the hot end. Now the z axis only moves towards the print head. I'm very new to smoothieware, and I'm hoping its just a config issue please help!!

Config is as follows:

You are going to want to use Google at this point : "site:forum.smoothieware.org my search".

We are working on migrating the forum to a better platform, this one sort of sucks compared to modern options.

Re: Search function by arthurwolfarthurwolf, 27 Mar 2019 18:53

What exactly do you want to do ?
Generally you'll end up with a combination of G30 Zsomething, G92 Zsomething, G0 Zsomething, etc.

Re: Z probe (CNC router) by arthurwolfarthurwolf, 27 Mar 2019 18:51

What stepper driver are you using ? Many high-microstepping drivers have the option to do "extrapolation" where for example you are controlling them at 1/8 microstepping, but they output at 1/256. This generally won't really cost you precision/accuracy, but allows you to work around the 100khz limitation.

Edit : also your config file is a very old revision, please make sure you upgrade to the very latest config file example ( porting over your old values to the new example file ) and latest firmware, before asking for help, as the documentation requests.

Max pulse rate from Smoothie is 100 000 steps/s (IIRC).

For move of 300 000 mm/min = 5000 mm/sec x 256 steps/mm = 1 280 000 steps/sec

Working forwards, with 256 step/mm and max step rate of 100 000 steps/sec = 390 mm /sec = 23 400mm/min

(I haven't even taken cosine transform of delta to cartesian, which can require up to 2.5x more steps per mm)

Remember also, minimum pulse length of step pulse from smoothie is ~3us, so even with instant drop to 0, then new rising edge at 3us, max step rate theoretically possible is 333 333 Hz, at 256 steps/mm = 1302 mm/sec. Check your external driver docs too, they usually have a minimum pulse duration for Step input - mine are 1.2us but I've see as high as 5us.

Remember also, ABB, Kuka, Fanuc etc use AC servos, not stepper motors, for exactly this reason (well also because the stepper motor itself loses torque as speed increases, so its not just about processing speed)

Just a rough look at your setup, large Linear Delta with incredibly high speeds desired - if this is for pick and place with low accuracy required (like sorting robot for food industry), try to get your gearing higher, so steps/mm is more like 25steps/mm, and drop acceleration to around 2000. Your large motors have good torque at low speed, so you want to keep motor speed low and use gearing to increase robot speed.

Ultimately, I think you need to be looking at AC servos and Mach3 or LinuxCNC to drive it.

I'm not sure if I understand what you're doing, but I added this custom menu item to my config, which uses G30 Z#

custom_menu.height_touch_off.enable true
custom_menu.height_touch_off.name Height_Touch
custom_menu.height_touch_off.command G28|G00_Z10.0|G30_Z1.62|G28

This is for a 3D printer, but I use it to set Z0, with a 1.62mm thick contact plate.

Re: Z probe (CNC router) by gavinmetzlergavinmetzler, 26 Mar 2019 21:43

My robot has L=1025mm R=366mm. I need a real speed of 5m/s. It's normal for industrial robots like ABB, Adept Quattro ets.
Here I have maximum 1m/s ((
In my opinion, the limit is in the program's algorithm.
Motor Nema 23, external driver.
My config:
arm_solution linear_delta # delta
alpha_steps_per_mm 256 # 125mm/rev *1/2.5(reducer) = 50mm, Pulses/rev = 12800 Steps per mm for alpha stepper = 12800/50 = 256
beta_steps_per_mm 256 # Steps per mm for beta stepper
gamma_steps_per_mm 256 # Steps per mm for gamma stepper
arm_length 1025.0 # this is the length of an arm from hinge to hinge
arm_radius 366.2 # this is the horizontal distance from hinge to hinge
gamma_max 88 # Высота присоски над столом
default_feed_rate 4000 # Default rate ( mm/minute ) for G1/G2/G3 moves
default_seek_rate 4000 # Default rate ( mm/minute ) for G0 moves
acceleration 10000 # Acceleration in mm/second/second.
junction_deviation 0.05 # Similar to the old "max_jerk", in millimeters,
x_axis_max_speed 300000 # mm/min
y_axis_max_speed 300000 # mm/min
z_axis_max_speed 300000 # mm/min
alpha_max_rate 300000.0 # mm/min
beta_max_rate 300000.0 # mm/min
gamma_max_rate 300000.0 # mm/min
mm_per_arc_segment 0.5 # Arcs are cut into segments ( lines ), this is the length for
delta_segments_per_second 100 # for deltas only same as in Marlin/Delta, set to 0 to disable
planner_queue_size 32 # DO NOT CHANGE THIS UNLESS YOU KNOW EXACTLY WHAT YOU ARE DOING
microseconds_per_step_pulse 1 # Duration of step pulses to stepper drivers, in microseconds
base_stepping_frequency 100000 # Base frequency for stepping, higher gives smoother movement
acceleration_ticks_per_second 1000 # Number of times per second the speed is updated

I tried to make "delta_segments_per_second " 0. Anyway maximum speed is 60000 mm per minutes
How could increase the speed?

page 1123...next »

This site is a WIki, which means you are very welcome to help us improve it. Help on how to do that can be found at the Editing the Wiki page . You can edit any page by clicking the "Edit" button bellow :