DDCSV1.1 4 Axis controller

The Shop > CNC

<< < (167/202) > >>

Will_D:

--- Quote from: lordprimoz on January 15, 2018, 07:03:23 AM ---
--- Quote from: PK on January 13, 2018, 11:13:04 PM ---How many steps per mm do you have configured?
The controller (any controller) can only move a minimum of one step. So, if a step is 0.049mm and you command a move of 5mm then it's only going to move 4.998mm...
Could this be what you are seeing?

PK

--- End quote ---

I have it set to 640steps per mm on both the x and the y axes. The z axis is at 1066.667. ( i also tried with 1067, no luck).

I wouldnt mind a few thousands offset because the controller cant handle that. But as i mentioned before, this is several tenths, and variable as well.

The gcode file seems to be fine. Just the controller not doing what its told by gcode.

--- End quote ---

I have just set up my X and Y steppers (metric 2 and 4 mm pitch) and was not getting the expecetd results. Different Overshoot and Undershoot at different places on the ball screws! :bugeye:

Turns out that the gibs were way too tight. Slackened off and set properly as expecected :thumbup:

Now the Z axis screw is imperial (0.2" pitch") did the calcs and plugged in the values (1600 steps / rev so 314.961 Steps /mm) - result;m Rubbish could not get it too work.

Thenn it dawned on me - I had reconnected the lifgt spring! disconnected it and checked the gibs for correct tightness, tweaked the its backlash and it is now withing 5 microns in 30 mm.

I am very happy

merc:

--- Quote from: Benedikt on January 06, 2018, 07:29:35 AM --- :update:
Here's the latest version of Pandora for DDCSV1.1 and RMHV2.1:
http://dl.pandora-cnc.eu/firmware/bleeding/Pandora-20180106.zip

It's not yet tested and therefore I can't claim it is stable. Testing is very welcome.
I have decreased the minimum steps per mm and increased the maximum steps per mm.
Also inch accuracy should be fixed with this version as well. Again, this should be tested.

Best regards,
Benedikt

--- End quote ---

Hi! I updated to the latest firmware, but still have a problem.
Its in the post https://madmodder.net/index.php/topic,11598.msg147711.html#msg147711
Any ideas how to fix this?

dale brisson:
ok lets see if i get a response to this question ( since no one like to share input)..to any questions i ask
mode 1 mode 2 for probe fixed position
is there a way to set my z0x0y0 as my probe fixed position ?
i want to build a tool height sensor where it will go to 000 probe new tool continue cutting or something in that nature ?

WeldingRod:

--- Quote from: dale brisson on January 21, 2018, 09:51:02 AM ---ok lets see if i get a response to this question ( since no one like to share input)..to any questions i ask
mode 1 mode 2 for probe fixed position
is there a way to set my z0x0y0 as my probe fixed position ?
i want to build a tool height sensor where it will go to 000 probe new tool continue cutting or something in that nature ?

--- End quote ---
Dale,
I've though about that too. As far as I understand (based on reading, since I haven't probed anything yet), the probe operation simply happens wherever the spindle is. So, if your gcode zeros, then probes, you should be ready to cut.
Regards,
Rod

Sent from my SAMSUNG-SM-G891A using Tapatalk

dale brisson:
i did kinda find a way but still work in progress i set as
mode2 fixed position .
i set 0 random on the table then hit probe the big issue is that the z will go down first to the probe height then y and x will fallow my 000xyz is at the back of the table and i wanted the probe at one corner at front of table.. so if there's (example)aluminum at g54 g55 where ever on the table where i want my start point to be. the z will crash then go the the fixed spot and slowly move.( i think i said this right bare with me here) still new to the game

Navigation

 Message Index

Go to full version