The Shop > CNC

DDCSV1.1 4 Axis controller

<< < (191/202) > >>

WeldingRod:
I'd love to have a way to contact him directly!

Sent from my SAMSUNG-SM-G891A using Tapatalk

Avis:
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

Benedikt:

--- Quote from: Avis 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

--- End quote ---
Yes, since both hardware and software are the same for both devices. They are locked down in software, basically. The setting is preserved.

Avis:
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

c4g:
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page