DDCSV1.1 4 Axis controller

The Shop > CNC

<< < (105/202) > >>

m_c_t:

--- Quote from: Benedikt M. on April 02, 2017, 08:35:24 AM ---
--- Quote from: librarymark on April 02, 2017, 08:27:59 AM ---
--- Quote from: BrokenEye on April 02, 2017, 07:33:33 AM ---That caught me out at first, I use a constant current bench PSU and I set it for 500mA , and only the buzzer sounded, I thought It was busted at first, but there was no "magic smoke" so I cranked it up to an Amp and found that it worked :) :zap:

--- End quote ---
I got my controller in the mail yesterday. Hooked it up to 24V and it was pulling 91mA with no USB drive. BrokenEye - when you cranked it up to an Amp what voltage did it wind up at?

--- End quote ---
Glad you received it!
I would recommend you to flash the new firmware rightaway ;-)
https://www.bmuessig.eu/secure/data/CNC/DDCSV11/install-mod-20170304.zip

Usual upgrade instructions apply (extract to root of USB + reboot controller with stick inserted).
This should fix many of the annoyances of the controller. I am still working on the new version with the G-Code rewriting.

--- End quote ---
Hello!
This update is very good, congratulations. :smart:
My question many:
How is it possible to turn ON password protection?
How is it possible by G-code, called workflow?
I think here:
"G21
G0 Y100 x200
M20 (probe code)
M03
G1 F2000 x200 y120
"
M20 is a unique probe or macro function.
How is this possible?
When you can run code of "probe" function references?
Thank you, good job, good luck

iocapa:
Greetings fellow madmodders.
A few days ago i ordered my unit, in the meantime i decided to look over the stuff it can do and i saw it had some limitations. So i made some research and maybe i can help with the software rewrite.
Soo.. i started to look over the stuff Benedikt did, and started to dig deeper in the reverse engineering, and found that for sure the internal UI made with Segger EmWIN.
I also started to a reverse engineer the motion driver (motiondev.ko), sorted out the low level comm stuff, and started writing source code for it. It's basically a character driver that uses some ioctl commands to acces some memory areas by a simple parallel port emulated through the GPIOs (more details in the code). I will upload it on github.
I am not that experienced in linux and maybe someone can help me with the files needed for the compilation of the kernel object so i can make a replacement for the original driver (from the reverse engineering it looks poorly written), i know that i need some headers for the version i want to build.

Basically the application writes some registers in the FPGA.
For example to beep the buzzer you have to write address 0x63 LSB with 1 or 0.
If you will look over the decompilation you can see some examples (look for functions that contain WR_DATA). The hard part will be the interpolation stuff, but i guess it should be doable. Maybe i can hook mine to a JTAG adapter when it arrives.

Also I will embed some disassembly/decompilation from IDA

https://github.com/iocapa/motiondev

Benedikt:

--- Quote from: iocapa on April 11, 2017, 04:45:40 PM ---Greetings fellow madmodders.
A few days ago i ordered my unit, in the meantime i decided to look over the stuff it can do and i saw it had some limitations. So i made some research and maybe i can help with the software rewrite.
Soo.. i started to look over the stuff Benedikt did, and started to dig deeper in the reverse engineering, and found that for sure the internal UI made with Segger EmWIN.
I also started to a reverse engineer the motion driver (motiondev.ko), sorted out the low level comm stuff, and started writing source code for it. It's basically a character driver that uses some ioctl commands to acces some memory areas by a simple parallel port emulated through the GPIOs (more details in the code). I will upload it on github.
I am not that experienced in linux and maybe someone can help me with the files needed for the compilation of the kernel object so i can make a replacement for the original driver (from the reverse engineering it looks poorly written), i know that i need some headers for the version i want to build.

Basically the application writes some registers in the FPGA.
For example to beep the buzzer you have to write address 0x63 LSB with 1 or 0.
If you will look over the decompilation you can see some examples (look for functions that contain WR_DATA). The hard part will be the interpolation stuff, but i guess it should be doable. Maybe i can hook mine to a JTAG adapter when it arrives.

Also I will embed some disassembly/decompilation from IDA

https://github.com/iocapa/motiondev

--- End quote ---
Hi there!
If you contact me via email I can provide you with the development tools for this exact controller. Including the factory flasher and the tool that loads linux images to RAM and executes them (talks to the bootloader in ROM and then jumps to the linux).
These tools include the source code to the full UI library and most kernel modules (not including the motion module, but including GPIO /etc.)
Of course this also includes all toolchain tools and the linux kernel used.
I am glad you got that far into reverse engineering. I had no time recently but great that you got on the right path! :beer:
I have gotten SDL to work, so if we decide to give our custom UI a go, the screen interface already works well.

EDIT:
Thank you so much for the decompilation! I don't have the HexRays Decompiler so this saves me so much work. :thumbup:

Benedikt:
Somehow I was lucky and my USB port was not fried :bugeye:
I connected the factory programming tool and I can now write anything to the controller that I want!
But :worthless:

So:

m_c_t:
Very clever.
Did you answer me? previous question ...
I've got more professional controller.
I help you?Link e-mail went
You need him?

Navigation

 Message Index

Go to full version