From categories:
page »

Forgot to mention this, but I've also tried swapping the Tx and Rx lines. It was complete radio silence when I did that. Not even the debugging info came through, so I'm confident I have them the right way around without swapping.

I also tried to grab the debug info at multiple baud rates, and it was always different levels of gibberish. I don't think it's in ascii, so I can't really confirm if I'm running the right baud.

Hey all,

I'm trying to talk to my V1.0 Smoothieboard using a serial connection. I am using a 768-1032-ND USB/Serial converter from Digi-Key and here is my config file:

I set the Smoothie to talk at 9600 baud, but that's all I've changed in the config as far as communication stuff goes. I also just flashed it with the latest firmware this morning. So far I've been able to receive the debugging info, but it's just a bunch of gobledegook to me:

It does not respond to anything I send it. I've tried GCode, as well as the help console command. No luck. I've also tried a whole slew of baud rates, from 75 to 128,000, still nada.

Currently I only have the Rx, Tx, and Ground wired to the USB/Serial converter. I did try also wiring the RTS and CTS pins, but that didn't seem to change anything. I am supplying a separate 5V to the Smoothieboard, so I do not have the 5V line wired from the USB/Serial converter.

I can get everything to work over USB, so there shouldn't be other hardware issues.

Anyone have any experience with this?

This was the first thread I found when trying to solve this problem. Then I found a youtube video that had the solution in the comments lol. If anyone else is having this issue then try this as it had worked for me without having to restart the print. In the settings menu of Pronterface, goto the viewer tab and check the "Use a lighter 3D visualization" check box. Then hit resume and pause a few times. If view /Pause is grayed out, hit reset and it will tell you it is already printing and show the pause/resume button again. I was printing a 3 million line print and it was at 97% when it failed. It picked back up as if nothing happened.

I know this is an old thread, but I was able to get the BLtouch to deploy by disabling my panel. ( the enable feature set to false )
i tested this on quite a few attempts, and in all cases, the only thing i changed in the config was enabling/disabling the panel
in each case i sent a deploy/stow command using pronterface terminal. M280 and m281

additionally, I got my panel AND the BLtouch working by removing some of the pull-up designations on the EXP pins for the panel. ( not sure why that would make a difference. )

Also, in full disclosure, I'm using an MKS Sbase 1.3 board.

I have same problem. So i replace LPC1769 with new one. Is it necessary flash bootloader for new chip?

What pin do i use for analog input om smoothieboard? and is it 0-3.3v or 5.0v?

Using the following

Early smoothieboard
Pronterface over Ethernet (TCP-streaming on)
Cura for slicing

Machine and computor hard wired to same switch

Print downloaded from thingyverse. Machine did about a quarter loop of a small circular print. then died. The following error apeared.

ok T0:211.6 /210.0 @237 B:63.3 /60.0 @0
Printer is now online.
Smoothie command shell
ok T0:212.0 /210.0 @231 B:63.0 /60.0 @0
Loading file: C:\Users\newki\Documents\Labbet!\Holly\carrot.gcode
Loaded C:\Users\newki\Documents\Labbet!\Holly\carrot.gcode, 51802 lines
3268.80mm of filament used in this print
The print goes:
- from 0.00 mm to 174.53 mm in X and is 174.53 mm wide
- from 0.00 mm to 124.53 mm in Y and is 124.53 mm deep
- from 0.00 mm to 88.80 mm in Z and is 88.80 mm high
Estimated duration: 223 layers, 0:42:18
Setting hotend temperature to 210.000000 degrees Celsius.
Setting bed temperature to 60.000000 degrees Celsius.
ok T0:213.3 /210.0 @206 B:61.7 /60.0 @0
Extruding 5.000000mm of filament.
ok T0:213.6 /210.0 @187 B:60.6 /60.0 @0
Extruding 5.000000mm of filament.
ok T0:212.4 /210.0 @187 B:60.4 /60.0 @126
Print started at: 09:29:13
Exception in thread Thread-3:
Traceback (most recent call last):
  File "threading.pyc", line 801, in __bootstrap_inner
  File "threading.pyc", line 754, in run
  File "printrun\printcore.pyc", line 339, in _listen
  File "printrun\printcore.pyc", line 283, in _readline
  File "encodings\utf_8.pyc", line 16, in decode
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe4 in position 40: invalid continuation byte

[ERROR] Print thread died due to the following error:
Traceback (most recent call last):
  File "printrun\printcore.pyc", line 534, in _print
  File "printrun\printcore.pyc", line 619, in _sendnext
  File "printrun\printcore.pyc", line 676, in _send
  File "encodings\utf_8.pyc", line 16, in decode
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe4 in position 40: invalid continuation byte

Exception in thread Thread-9:
Traceback (most recent call last):
  File "threading.pyc", line 801, in __bootstrap_inner
  File "threading.pyc", line 754, in run
  File "printrun\printcore.pyc", line 391, in _sender
  File "printrun\printcore.pyc", line 676, in _send
  File "encodings\utf_8.pyc", line 16, in decode
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe4 in position 40: invalid continuation byte


Has anyone gotten the BLTouch to work with the X5 Mini WiFi?


X5 Mini WiFi BLTouch by bcrazycramerbcrazycramer, 01 Nov 2019 15:48

Any luck on getting the BLtouch to work on the X5 Mini Wifi?


i'm using morgan scara
i built a scara robot, with X Y arm length 200mm
i'm using optical endstop Xmin and Ymax and mechanic endstop on Z (i would know if soft endstops can be used for bed size limit) can its works in this mode?
i would set bed size of 300x220 with 0,0 in this way should work also in negative

Cartesian grid strategy leveling seems work

At the moment my robot is drawing (not print), if I try to draw the perimeter of a square, it does not draw straight lines, can this problem be due to the kinematics or the length of the arms?

Than you in advance!

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 :

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

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 :-)

page »

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 :