Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Project Logs / Re: Close. But, no Cigar.......
« Last post by Brass_Machine on February 20, 2018, 02:01:34 PM »
A little late to the party. Nice to see it running Dave!

BUT that LTD!

 :bugeye: :bugeye: :bugeye: :bugeye: :bugeye: :jaw: :jaw: :jaw: :jaw: :jaw:
22
CNC / Re: DDCSV1.1 4 Axis controller
« Last post by Cosimo.83 on February 20, 2018, 01:09:35 PM »
Congratulations on the progress made. I tried what is all for a program, for example, plasma is not the case, the program hangs and waits. Perhaps in autorunning the function is disabled.
23
CNC / Re: DDCSV1.1 4 Axis controller
« Last post by Cosimo.83 on February 20, 2018, 01:04:43 PM »
Complimenti per i progressi fatti. Ho notato che se all' interno di un programma provo a richiamare la sonda per fare un azzeramento , esempio la torcia plasma il probe non va , si blocca il programma e rimane in attesa. Forse in autorunning la funzione disabilitata.
24
Project Logs / Re: Close. But, no Cigar.......
« Last post by Chuck in E. TN on February 20, 2018, 08:06:02 AM »
Suspense is killing us! What did he do to fix it? You can't leave us hanging...
25
CNC / Re: DDCSV1.1 4 Axis controller
« Last post by Will_D on February 20, 2018, 07:49:52 AM »
Hi Josef, Thanks for the info.

The 3 step probe.nc is actually in most of the 1.1 versions!

I eventually found one like yours in the 2017_03-04 version download [Attached]. Not tested this out yet!

Trouble is at the moment the 3 attempts version only runs the last probe!!

I am still trying to debug this using M00 halts, G04 Pauses and commanding a spindle speed to display a parameter version!

NOTE: I don't control my spindle so this is the best way to display variables.

Like this:

(Safe Block)
G17 G21 G90 G54 G40 G49 G80

(set initial X, Y  and Z)
G00 X0.0 Y0.0 Z0.0

G04 P5000; Little delay

(Read the co-ordinates)
#20 = #840
#21 = #841
#22 = #842

(Check Settings)
(G54.X)
S #20*100
G04 P8000; #840 Check Speed!

etc
M30
%


Am getting nowhere at the moment!

More later hopefully

Will
26
CNC / Re: DDCSV Support Forum
« Last post by JPoepsel on February 20, 2018, 07:33:15 AM »
Just to answer my question by myselve:

I mailed to technical@ddcnc.com and within 30min I got a reply with an ivitation link!

 :beer:
27
CNC / Re: DDCSV Support Forum
« Last post by JPoepsel on February 20, 2018, 06:49:33 AM »
Hi all!

No, I'm not the one normaly translating foreign language forum entries to English (I think the original poster can use Google translator as well, which would be fair to the other users), but this time is an exception, since I have the same question:

"Ciao Ho provato a registrarmi sul forum dd ma mi chiede un codice di invito che cos' ?" means somethink like

I tried to Register on that Forum but Registration requires an Invitation code. Where can I get one?

So, anbody willing to invite me?

CS

Josef
28
CNC / Re: DDCSV1.1 4 Axis controller
« Last post by JPoepsel on February 20, 2018, 04:44:59 AM »
Hi Will!

You are right, #516 is not used directly in probe.nc.

Im ab it confused at the moment :loco:.
I found your translated probe.nc in this forum (https://madmodder.net/index.php/topic,12427.msg148354.html#msg148354 ) and I think also in this forum there was a post with the nc files of the RATTM RMHV2.1 version with the translated comments (sorry, I do not find the post at the moment, I downloaded the files the time I read the post some weeks ago). I did not check it  that time and thought, that the files on my device (I bought a RATTM RMHV2.1) are identical but they are not! The ones on my device are not translated!?
Your probe.nc is different to this two versions at all. It does a three times test and an averaging, my does only a one time test
I will put  the translated probe.nc I downloaded at the end of this post so you can compare. The question is: where did you get your version?! (BTW: a rough look showed no differences in your slib.nc to mine) .

But to come back to the real thing: In Probe.nc  the first ()-comment (in all versions) is

(Reads the current machine tool coordinate position ȡǰ߻еλ)

followed by

#20=#864
#21=#865
#22=#866

so I assumed that #864.. are the current machine tool coordinate positions ;-)

In the system lib I found #864 (to be precise: #866) also used in subprogram O100 for the case statement of #516. If #516 is 7, #864 is used for correction (with this #[#1+2] indirect addressing trick). #516 may range from 0 to 7 (not 0..6)! This is why I said that #516 is different to #455.

Some words about M101 and M102 used in probe.nc:

In Probe.nc the following is used

M101
G91 G01Z-100 F100
M102
G04 P0   

Im now more or less sure that M101 means enable stop movement if probe enabled and probe contact closed and M102 means disable stop movement on probe contact.
So, if M101 is active, the probe contact acts like the normal limit contacts! I did not try this, but I think, this also works on any movement in any direction, not only on Z. The G04 P0 is for  synchronization, whatever that means.
This in mind it should not be a problem to write a macro which finds the middle of inner/outer circles, rectangles (assuming, the probe can touch in X/Y directions):headbang:. The result (the center) may be stored as a local zero-position of G55 or any other local coordinate system for readout or other usage

You asked, whether my probe function works and what are the differences between mode 1 and 2 ?! To be honest: I dont know. I tried it and I have an idea, but I do not use it at the moment  (need some practice with my machine until I risk a tool lost ;-) ) . Here my idea:  Mode 1 uses the probe and sets Z to 0 in the local coordinate system (with some offsets) after probe contact. Mode 2 uses an internal variable to store the first probe result done after an All-Zero-Setting of coordinates by the user. This internal variable is used from the second probe on to use differences to the first to calculate relative tool offsets (see also comments in Probe.nc. Since the probe mode number in Probe.nc is not used (at least I dont can figure it out), there must be some other magic build in the system)).

Josef

P.S.: Here my (unmodified) Probe.nc (translated version):

G04P0 ;Pause for 0sThe current machine coordinate position is correctly read for subsequent programs Ϊȷȡǰеλ
M5;Close the spindle ر
(Reads the current machine tool coordinate position ȡǰ߻еλ)
#20=#864
#21=#865
#22=#866
;Determines whether the system uses the fixed position tool presetting mode or the current position setting mode
(̶Եģʽ£XYZĽ)
IF#571EQ0GOTO1
#1=#572-#20
#2=#573-#21
#3=#574-#22
GOTO2
(X, Y, Z feedrate is cleared in current tool setting mode ǰԵģʽ£XYZ)
N1#1=0
#2=0
#3=0
(Move to the initial position of the tool ƶԵʼλ)
N2G91G00Z#3
G91G00X#1Y#2
(100% speed detection of 100mm knife detection signal 100ٶ̽100mmԵź)
N1M101
G91G01Z-100F100
M102
G04P0 ;Pause for 0s ͣ0s
#402=#400;Save the coordinate system Z axis zero offset ϵZƫ
#403=1;Set the automatic correction coordinate system flag Զϵ־
#404=-#870;Save the thickness of the block, if the thickness of the blade before the parameter is 0, the system will use the variable correction on the block thickness parameters in order to complete the first knife Եȣ֮ǰԵȲΪ0ϵͳøñԵȲɵһζԵ
G91G01Z#575F#578;The tool is completed and the Z axis retracts ԵɣZ

29
Project Logs / Re: Little Blazer X4
« Last post by philf on February 19, 2018, 06:03:19 PM »
Hi Doc,

Brilliant to see all 4 running.  :thumbup:

As you say nobody makes you watch the whole video.

Looking forward to the next project.

Cheers.

Phil.
30
Project Logs / Re: Close. But, no Cigar.......
« Last post by Stilldrillin on February 19, 2018, 05:58:22 PM »
Well......

I was so browned off, with this tiny bundle of bits. Wasted enough time on it. So, I sent it back to Herefordshire.

This afternoon. A video arrived.......




Seems, Phil has the necessary magic!  :clap:

I think. In future. He can do the commissioning for me......
Pages: 1 2 [3] 4 5 ... 10