Author Topic: DDCSV1.1 4 Axis controller  (Read 230005 times)

Offline WeldingRod

  • Full Member
  • ***
  • Posts: 165
Re: DDCSV1.1 4 Axis controller
« Reply #950 on: September 05, 2018, 01:51:43 PM »
I'd love to have a way to contact him directly!

Sent from my SAMSUNG-SM-G891A using Tapatalk


Offline Avis

  • Jr. Member
  • **
  • Posts: 10
  • Country: es
Re: DDCSV1.1 4 Axis controller
« Reply #951 on: November 17, 2018, 03:13:43 PM »
Hello, I have the driver DDCSV1.1 4-axis version. If I update with pandorainstaller to the latest version of the manufacturer, do I keep all the axes?
Thank you

Offline Benedikt

  • Full Member
  • ***
  • Posts: 187
  • Country: de
    • My website
Re: DDCSV1.1 4 Axis controller
« Reply #952 on: November 17, 2018, 03:58:25 PM »
Hello, I have the driver DDCSV1.1 4-axis version. If I update with pandorainstaller to the latest version of the manufacturer, do I keep all the axes?
Thank you
Yes, since both hardware and software are the same for both devices. They are locked down in software, basically. The setting is preserved.

Offline Avis

  • Jr. Member
  • **
  • Posts: 10
  • Country: es
Re: DDCSV1.1 4 Axis controller
« Reply #953 on: November 18, 2018, 09:31:44 AM »
Today I did the update with pandorainstaller, "excellent work", but I still have the problem of blocking in complex programs (I have to restart the panel again), with simple works works perfectly. I've seen on You Tube a user with the same problem, today I put a fan on the back of the panel (remove the back cover) and it seems to work well, it's strange since the DDCSV1 does not heat up at all, but with the fan I have better results.


Regards

Offline c4g

  • Newbie
  • *
  • Posts: 4
Re: DDCSV1.1 4 Axis controller
« Reply #954 on: November 29, 2018, 12:29:51 AM »
I wish to modify the slib.nc file which comes with the latest firmware patch. Most of the config files in the /upgrade/nand/ diresctory are gibberish when opened for editing as they are not iso english, so i do not know how to read/edit them.

I wish to add a manual tool change subprogram, where:

1) the main program is paused via M0,
2) a g28 command is issued (return to home), (fusion360 automatically adds a G28 Z0. move command)
3) the tool is manually changed and then manually centred over touch-off plate,
4) the start button is pressed to unpause the program
5) the program calls the built-in probe routine (via G38 Z or via M98 ????, which is it? probe.nc is gibberish. if the probe routine is not callable then steps 4 & 5 can be reversed and the probe done manually)
6) the main nc program continues on with the new tool.

 This will work well with fusion360   :nrocks:

if this is not possible then separate nc files for each tool can be created, but that entails more set-up work and file editing.

I read in the DDCSV pdf that the controller gcode is fanuc g compatible. I'm using the fanuc -G91 post processor within fusion360, but manual tool changes are being ignored by the controller (the spindle shuts off then immediately turns back on). That seems to be an easy patch within slib.nc by at adding a M0 or M1 command (wait for operator input), or by adding a new  subprogram  with the 6 steps from above.

PS:  With some testing, the controller completety ignores M00 and M01 gcodes. This is going to be harder to implement than I realized.  Yet the pause button pauses the program, which seems to be implemented in the OS, and not the slib library.  Ill use separate files for each tool as a work around for now.
« Last Edit: November 29, 2018, 07:58:43 PM by c4g »

Offline c4g

  • Newbie
  • *
  • Posts: 4
Re: DDCSV1.1 4 Axis controller
« Reply #955 on: November 30, 2018, 12:34:21 AM »
Update: A quick and manual way to do tools changes from fusion360, to post with "fanuc - with subprograms" and have "subprograms in a separate file" checked off. Each tool operation will be posted to a separate numbered nc file.

I scrap the 1st numbered file 1001.nc, (its not needed) and edit the remaining numbered files. I scrap the lines between the % and 1st title in brackets ie "(boring1)" as the controller does not  accept 0XXXX header gcode, and Fusion360 inserts tool moves at the top of the file that are redundant. All thats left is tool change and pathing gcode. (fusion360 likes to insert G43 command but the controller ignores them from what I can tell). If needed,  a M03 command is added at the top of each file,  and M05 command at the bottom before the M99 exit. I double check the z start and finish positions in each file.  Fusion 360 is good leaving the tool above the stock. I set the "probe retraction distance" to be above any stock used.

I then load each file in sequence 1002.nc,1003.nc,..,..   manually doing tool changes and probes where needed. I keep track of what tool goes with which file, and which operation has been completed. I can pause/start or restart a particular file, or even re-home if steps are lost for example.

Still, automating all of this in one file, and having the DDCS pause on M00,M01 or T# M06 gcodes would be the way to go.