DDCSV1.1 4 Axis controller

[Benedikt]

So, how i install the firmware?
there's more than a folder,
Thank you in advance.
Emanuel
PS. did you got the front panel laser cutted?

Really courious to see it finished, i'm working on mine, just waiting for the carbon fiber sheet to arrive and then i will machine it.

Nice! Good luck!

So the compiler is built successfully! It compiles things and I get the result I expected.
I have not tried the binaries yet but I will soon do that.



EDIT: I tested it and it works! 
Wow, even my framebuffer code seems to run. That's great!

[Merlin201314]

Fantastic!!!!!!


At the end it will be left just the board of the original controller...
I'm designing a new front panel and  Keyboard with all the buttons integrated including the MPG.
Let's see what i can do :-))

[Merlin201314]

So, i guess we could use even a better screen for the controller?
Assuming we could get and connect a better one? (like in the raspberry i mean)
I know we are just in a very early stage, is just a curiosity............

[Benedikt]

So, i guess we could use even a better screen for the controller?
Assuming we could get and connect a better one? (like in the raspberry i mean)
I know we are just in a very early stage, is just a curiosity............

Sounds interesting. Keep me updated!

No, we can't change the screen for a couple of reasons:
 - Size: it might be hard to find one that fits exactly (however if you redo the front that might not be a big deal)
 - Kernel: the kernel only contains drivers for the screen that is currently instelled; everything else would require us to write a driver and build an entirely new kernel
 - Connector: it might be hard or even impossible to find another screen that would work with the connector and connections available (I am just guessing as I haven't see the connector yet)

But the original screen isn't bad. Resolution and size are alright for a CNC, don't you think so too?


Currently I am trying to compile a framebuffer graphics library to use on the controller.

[Merlin201314]

The screen is not bad at all, is just because the plastic membrane that cover the screen is weak, and the keyboard will be pierced soon with an intensive use
of the caps, and i am using a lot the router milling pieces for my printers.
Don't know how much the keyboard will last to be honest

[Benedikt]

The screen is not bad at all, is just because the plastic membrane that cover the screen is weak, and the keyboard will be pierced soon with an intensive use
of the caps, and i am using a lot the router milling pieces for my printers.
Don't know how much the keyboard will last to be honest

I am all for replacing the membrane, but not the screen. So do you know a way to get a membrane made?

[Merlin201314]

The screen is not bad at all, is just because the plastic membrane that cover the screen is weak, and the keyboard will be pierced soon with an intensive use
of the caps, and i am using a lot the router milling pieces for my printers.
Don't know how much the keyboard will last to be honest

There's a company in London that do panels and custom made adhesive keyboard, i just have to do the design and be very specific in what i want, but it can be done.

[Merlin201314]

Of course we can get rid of the DDCSV1.1 logo from the front panel then

[Benedikt]

Of course we can get rid of the DDCSV1.1 logo from the front panel then

I really dislike the DDCSV1.1 name anyhow. It is so misleading. Even the hardware is revision 1.4.
Can we just decide for a new name all together?
Especially given that we need a name for the new firmware.

I have made progress with writing a small graphics library to assist me with writing small programs. Eventually I will port GTK/Cairo or some other library to the CNC controller.

[Merlin201314]

Well...  As you are the bigger contributor to this project you will have the honor(or duty) to give a name to this new baby,  then we can suggest smaller adjustments if you agree,  what do you think about that?

Sent by my tapatalk

[Benedikt]

Well...  As you are the bigger contributor to this project you will have the honor(or duty) to give a name to this new baby,  then we can suggest smaller adjustments if you agree,  what do you think about that?

Sent by my tapatalk

I am bad at naming, but some names could be:
 OCNCC -> offline cnc controller (or LCNCC = Linux CNC controller)
 Pandora -> as in how my CNC is called (due to the build being rather difficult and time consuming and as there always was something that went wrong)

But if you dislike them, I will think a little more about another name.

[Joules]

Box Clever CNC

or

MMCNC    (Mad Modder CNC)

and nice work on the software side 

[awemawson]

FLUFFY

FLexible

Unix controlled

Four Axis

FullY featured controller

[Merlin201314]

Well...  As you are the bigger contributor to this project you will have the honor(or duty) to give a name to this new baby,  then we can suggest smaller adjustments if you agree,  what do you think about that?

Sent by my tapatalk

Pandora is the right name for me, as in this project there's a lot of thing that will go wrong at some time, so why not?

[Merlin201314]

Benedikt, i am quite happy to sacrifice my controller if you want to go for a complete different way,


Have a look at this link, is not the program, is all the dependencies in python to have a look, including the GUI toolkit "tkinter"
https://github.com/vlachoudis/bCNC
Here you have the link,
I had downloaded this program as i own 2 "smoothieboard 5 axis", and i use them for my printers "32 bit processor obviously"  then i decided to buy the stand alone controller instead to install everything on a raspberry pi3
Hope that can help a bit, let me know your opinion please
Emanuel

[Benedikt]

Thanks a lot for all the input 

So how about Pandora MMCNC?

Still a nice name, awemawson!

Best of both 

[Merlin201314]

We could use the MMCNC for the controller and the Pandora for the software no?
I'll send you a splash sample in a few minutes

[Benedikt]

Benedikt, i am quite happy to sacrifice my controller if you want to go for a complete different way,


Have a look at this link, is not the program, is all the dependencies in python to have a look, including the GUI toolkit "tkinter"
https://github.com/vlachoudis/bCNC
Here you have the link,
I had downloaded this program as i own 2 "smoothieboard 5 axis", and i use them for my printers "32 bit processor obviously"  then i decided to buy the stand alone controller instead to install everything on a raspberry pi3
Hope that can help a bit, let me know your opinion please
Emanuel

Well I wouldn't mind naming it as you suggested.
Let's see what the other members think then we decide on a name.

Your idea sounds good and if I had known this a few months earlier, I wouldn't have bought a DDCSV1.1MMCNC.
But we'll stick with what we have. About the program, I don't know if porting it is possible. It might be worth a try, but remember, we still need to find out how the motion driver works and how we can communicate with it.
Unfortunately nobody here has an ARMv5 capable version of IDA or anything remotely similar to disassemble (and possibly turn back into C code to make it at least a little bit easier to understand) the attached file.   

[Merlin201314]

Here you have a sample, is open to any suggestion of course

[Will_D]

That would float my boat.

Lovely image!

Just as an aside: Wasn't the idea behind Pandora's Box was NOT to open it?

It may after all contain Schroedinger's Cat!!

[Merlin201314]

Pandora's box has landed in the wrong place, this is an open source forum, so there's no chance.......
 

[tom osselton]

Still the file folder could be named " do not open box " the electrics should have it anyways.

[Merlin201314]

Ok guys.... good news about the G-Code compatibility,
As i work with Visi19 Cam, the generated G-code is for a Fanuc machine, or can be changed for other Fanuc models, never the less is still complicated.
So i generated a simple square 3 axis interpolated toolpath (Is the orange path in the toolpath-1 picture).
Then generated the .NC G-code, wich is quite long . (attached as a .txt file if someone want to give it a look) just rename the .txt  to  .NC and load on a usb pendrive.
I just deleted 3 "strange" codes at the beginning of the file as they do not exist in the MMCNC language, just left the spindle on and speed setup, deleted the tool change,  and .......... IT WORKS!!!!
I have to say, i am impressed how the 3 axis are interpolated, very smooth, no material left or glitch in the path.
So clearly it can work if we find the way to add some more G-command to the library (with associated routine of course).
Any comment is fully apreciated
Regards

[Merlin201314]

  PS.
The tool is a 4 mm ballmill, it won't go deep more than 4mm, so is safe to try if you want to.
the toolpath is just the orange one, is not the full pocket, the gray part is untouched by the tool and has to be considered solid part.
Just to be clear
Cheers

[Merlin201314]

Hy all,
just come across this one.....
https://www.youtube.com/watch?v=8Pi-ramLLSo