Welcome to the SeeMeCNC Community

mhackney wrote:Broose, yes, the convertor is convenient. I have one installed also. I posted info on where it goes on the smoothie wiki (see photo at bottom of page).

I just used your annotated photo on the wiki the other day to locate the jumper for the small mosfets.

Hmm, I didn't know the memory card was the cause of all those problems! I bought a microSD to regular SD adapter yesterday with a Samsung card, maybe that will help. Actually I just noticed that it's in the board right now. Maybe switching to it is what made my problems go away. I still have the smoothieboard connected to my laptop with the USB, as I need it connected to run overnight prints. The first real print came out really well, although it was a 0.4mm nozzle so it's not as crisp as what I've become used to with 0.25mm nozzles.


I'll post a few pictures of the print sometime today.

Since it has both a USB and ethernet cord, do we have four options for how to control the printer?

1) Print directly from the USB with a host program
2) Start the print with the gcode on the microSD, then remove the USB to print standalone
3) Print with the ethernet cord over the internet with the new server host program
4) Print wireless with a Raspberry Pi through the USB

Am I right on those?

Thanks for sharing your config file! I ordered my own 5x earlier today, so I'll be using that soon.

Is there a Git fork anywhere with an 'official' Rostock Max config file, or is this all based on the experience of others?

You can also print free-standing use a panel (LCD). You can also control over ethernet to print files on the microSD card using a terminal program like CoolTerm.

Jim, not aware of a git for Rostock smoothie config. Sounds like a good contribution to the community though.

There was originally a Rostock max specific version that I submitted for use,but in my communication with the wolf guy he informed me that it was using slower maths. And removed it and told me to use the Kossel config. The kossel config became the linear-delta config.

The x and y towers are swapped on the linear-delta (previously called kossel), and this is the only difference between it and the rostock specific I had submitted. (although I seem to remember having to reverse my endstop logic as well, I'm fuzzy about if this was what I had to do on the X5 only or the kossel....hmmm)

I had also set the default arm and delta radius for the rostock so you will obviously have to redo that to match your config.

******
flat-eric commented on Apr 12
Simply added together recent changes and updates and completed the Rostock with them up to date.

wolfmanjm commented on Apr 12
it is not recommended to use the rostock arm solution. the kossel is the recommended one.
probably should remove it.
Jim Morriswolfmanjm closed this on Apr 12

flat-eric commented on Apr 12
Is that the code for arm rostock to be avoided? What's the differences between the two types in code? Just more up to date? Suggest some naming convention that suggests that kossel/rostock are interchangable or perhaps simply rename it to delta for the newer less experienced users? Otherwise for new people it looks like you drop rostock support. Understandably they are the same hardware wise.

flat-eric commented on Apr 12
It was my understanding they were identical other than a tower swap. Working really well with the rostock on my setup. Or is there more to know here and how to swap the two towers for the rostock setup then when running kossel?

wolfmanjm commented on Apr 12
the end result is similar but the calculations are different, and rostock is slower to calculate. The tower swap angles in rostock do not seem to work either. I have been meaning to remove it, but it is nice to have it for historical purposes.

If you switch to kossel you will need to swap you XY towers.

I wanted to rename it delta but there was opposition to that idea.. maybe linear-delta woul dbe better.

flat-eric commented on Apr 13
Gotcha.