smoothie won't start printing

[bvandiepenbos]

I have my smoothie board wired up and working from GLCD panel. I can home, jog, turn on heat etc. stc. from LCD, but when I start a print it just heats up bed and never will start printing. I can connect to it from Matter Control but it acts the same, never starts printing. I have tried Slic3r and Matter Slice, niether one works. Even tried old gcode that was successfully printed with the Rambo board.
What is wrong?

I will attach a gcode file.

[mhackney]

Brian, can you post your smoothie config file (give it a ".txt" extension to upload here).

[mhackney]

Is it possible that your bed is not reaching 100°C so it doesn't start? Try printing with lower bed temp just to see if you can get started. You also need to have bed enabled in the config (which is why I'd like to see it).

cheers,
Michael

[bvandiepenbos]

The LCD says it is 100 c, but I will give that a try.
By the way the bed is running on 19 volts, man that heats up so much faster!
It is a Meanwell 24v with voltage adjust turned all the way down.
everything else is running on a second 12v meanwell supply.

I will attach my config

thanks

[bvandiepenbos]

I did more testing this morning. I ran my gcode file for tower z adjusting which has no heat commands, it does not work properly either... it homes ok then goes up, crashing into top mecahnical limits. So I do not think it is waiting to heat, it must be something wrong with setting Z height.
When I home from LCD it seems fine but LCD reads X214 Y214 Z213.7 Z height is correct for this machine but why is X & Y not zero?
after homeing with lcd then trying to jog with lcd it will not move.
However, if I select 'set home' after homing then LCD reads X0 Y0 Z0 and then it will jog in all directions.

I must have something wrong in my config or start code


The only thing in my start code is G28
that has always worked with the Rambo.

[Polygonhell]

I vaguely remember that linear_delta is not the correct arm_solution setting, I think it ends up using cartesian with that set.
Try setting arm_solution to kossel instead.

Given the example configs have it set to linear_delta, that seems like a bug to me.

[mhackney]

Polygonhell, they did just recently rename the delta solution 2 weeks ago on the edge releases. You MUST use the correct config file with the binary you download or build. The proper solution for the newer firmware is linear_delta, it used to be kossel.


But the reverse of your other comment would be true - don't use linear delta with earlier firmware!

Just checked, June 2 was the changeover date for the arm solution name change.

[Polygonhell]

No, my download had it set to linear delta in the examples, and it caused issues until I changed it to kossel
if you look at the code they just compare 16 bit checksums of values

Code: Select all

#define  kossel_checksum                     CHECKSUM("kossel")

// Random other code here

    if(solution_checksum == hbot_checksum || solution_checksum == corexy_checksum) {
        this->arm_solution = new HBotSolution(THEKERNEL->config);

    } else if(solution_checksum == rostock_checksum || solution_checksum == kossel_checksum || solution_checksum == delta_checksum || solution_checksum ==  linear_delta_checksum) {
        this->arm_solution = new LinearDeltaSolution(THEKERNEL->config);

This code implies that kossel should be identical to linear_delta, however the collision rate on a 16bit hash is extremely high (it's basically the birthday paradox), so my guess would be that there is a hash collision, though the chances are only like 1% for the small number of unique values they have.

Either that or I had other issues during setup and messing around I happened to make that change along with the actual fix.

[mhackney]

I was working on my TemperatureSwitch module during this changeover. Caused me all sorts of grief trying to figure out why my printer was acting weird - basically only one tower moved at a time - like a cartesian!

[mhackney]

Brian, which firmware are you using? When you connect to the printer, issue an "@version" in Protorface. Not sure if RH will do this. You'll get the build date and version.

[Polygonhell]

I was working on my TemperatureSwitch module during this changeover. Caused me all sorts of grief trying to figure out why my printer was acting weird - basically only one tower moved at a time - like a cartesian!

It's possible I happened to pull in that period, my download is a couple of weeks old

[bvandiepenbos]

Brian, which firmware are you using? When you connect to the printer, issue an "@version" in Protorface. Not sure if RH will do this. You'll get the build date and version.

OK, I will check. Thanks guys!

I probably should just download and flash the newest fw ?

[mhackney]

Yes, the newest FW has my TemperatureSwitch module in it!

[bvandiepenbos]

what is the command to get version of smoothie fw?
I typed @version in matter control terminal window, no response.
MC is connectted and communicating with smoothie, I can see it polling temp and get response (M105)
M119 gets response from enstops X max:0 Y max:0 z max:0

[mhackney]

Each host software has its own way of passing these sorts of commands. Some may not do it either. Try "@" or "!" before the version command.

If that fails you can use a serial terminal application. I use CoolTerm as it supports Mac, Windows and Linux. It is a very simple and light application. Once you have it installed and running, click the Options button. Then select Terminal from the side panel. Set "Line Mode" for Terminal Mode. To connect, you choose the Serial Port on the side panel and select your port from the list, nothing else here matters. Click Ok and then Connect on the main window.

Now you can enter Smoothie commands directly. Type version and hit enter. There are lots of commands and not all are listed here. Do a 'help' in CoolTerm and you'll get a list. You can load files (gcode for example), start or stop priming, reset the board and other useful stuff.

[Jimustanguitar]

Hey Brian, I bet it'll work if you use their newest firmware

[bvandiepenbos]

flashed newest firmware and all works now !
we are smooooth and happy now
test print right now @ 150mm is looking good.
Thanks guys.

[Jimustanguitar]

Here's Brian's first print, if you're curious.

[youtube]http://www.youtube.com/watch?v=wfFYrOYgdJg[/youtube]


Edit... I hate the youtube embed feature! It never seems to work the same twice. URL, embed code, address bar link... wtf... I did this last night in another post and it worked with the URL that included the word "watch". Shakes fist at Google!

https://www.youtube.com/watch?v=wfFYrOYgdJg

http://youtu.be/wfFYrOYgdJg

<iframe width="560" height="315" src="//www.youtube.com/embed/wfFYrOYgdJg?rel=0" frameborder="0" allowfullscreen></iframe>

<object width="560" height="315"><param name="movie" value="//www.youtube.com/v/wfFYrOYgdJg?version=3 ... ram><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="//www.youtube.com/v/wfFYrOYgdJg?version=3&hl=en_US&rel=0" type="application/x-shockwave-flash" width="560" height="315" allowscriptaccess="always" allowfullscreen="true"></embed></object>

[mhackney]

I had the same issues - turns out you need to use https protocol and then all should be fine.

[bvandiepenbos]

Thanks for posting the video Jim.
( This was printing at 150 )
wow the smoothie is awesome! ....
bye bye RamBo

[mhackney]

Welcome to the club Brian!