| The Shop > CNC |
| DDCSV1.1 4 Axis controller |
| << < (110/202) > >> |
| antonio:
Hi Benedikt it seems backlash function not work properly with original firmware. Did you fix the problem with new firmware? When change move direction the driver should add the valures which I declare on setvar at velocity declared but it seems that velocity did not change (remaining same on g1 g2 and g3) and also the booth axis moving contempory instead one even change only one direction. many thanks for your kind coop. Inviato dal mio iPad utilizzando Tapatalk |
| PPRINT:
Benedikt, thanks for the detailed write up on the steps. That helps. No worries on losing the parameters. Reconfiguring them was much faster, and I was able to do a better job, the second time. Thank you, Rob |
| Benedikt:
--- Quote from: PPRINT on May 01, 2017, 06:56:09 AM ---Benedikt, thanks for the detailed write up on the steps. That helps. No worries on losing the parameters. Reconfiguring them was much faster, and I was able to do a better job, the second time. Thank you, Rob --- End quote --- I am glad you don't mind loosing the parameters too much. The original firmware upgrade process would have deleted the parameters anyways, so it is not directly my fault. I have now added a line to my custom installation script to preserve existing configuration in any case. Feel free to ask again if something breaks or is unclear. --- Quote from: antonio on May 01, 2017, 12:52:44 AM ---Hi Benedikt it seems backlash function not work properly with original firmware. Did you fix the problem with new firmware? When change move direction the driver should add the valures which I declare on setvar at velocity declared but it seems that velocity did not change (remaining same on g1 g2 and g3) and also the booth axis moving contempory instead one even change only one direction. many thanks for your kind coop. Inviato dal mio iPad utilizzando Tapatalk --- End quote --- Thanks for reporting. I will see what I can do about it. There is unfortunately a limitation of how much can be patched as there is few empty space in the elf that we can use to patch. We could always overwrite the unused functions with additional code. Also I forgot to ask, who is interested in having Ethernet or WiFi capabilities implemented? This is possible using USB adapters (cheap 10/100 Ethernet or Edimax WiFi adapters), however, it requires a new flash image to run. This is not trivial for us, since it would require developing a *robust* OTA flash update application, but it would work. This would also allow changing the ugly splash screen. The downside for you will be the risk of actually bricking the controller in case of a power outage or corrupted image. Note that you can always solder a cut off USB cable to the internal debug header to restore the image. So JTAG or low-level flash programming is never required. I would even fix broken units / upgrade them, if shipping to Germany and back is paied for. We will, if we succeed at making an OTA updater, make this optional. I would just like to know who would like to remote control or customize the controller under these conditions. In case anyone wants to know why the processor manufacturer did not provide custom and robust OTA update capabilities, the answer is, they did, but it only works for updating from SD card. And our controller's hardware engineers did not provide us with an SD card slot. D'oh! Regards, Benedikt |
| riorao:
Hello! I use two motors on the X axis. This controller will work with this configuration? there is synchronization? |
| jjae6:
--- Quote from: riorao on May 02, 2017, 02:21:17 PM ---Hello! I use two motors on the X axis. This controller will work with this configuration? there is synchronization? --- End quote --- I think I have read in this post that some people use 2 motors on one axis, but with two drivers, one per motor. |
| Navigation |
| Message Index |
| Next page |
| Previous page |