Hello Guest it is March 28, 2024, 06:56:31 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - SteelWolf

Pages: 1 2 3 4
1
PoKeys / PoKeys57CNC and external sensors?
« on: December 28, 2016, 11:47:49 AM »
The Pokeys57CNC feature list includes the following point:

"support for up to 100 sensors, that can be connected to I2C bus, 1-wire bus or on the general purpose analog inputs,"

I guess most of the people (maybe Im wrong) will use the board in combination with Mach3

Is there really no possibility to access I2C and 1-Wire values from Mach3?

Greetings,
Max

2
I will try it when im back from work and IKEA o:

Did you test it with differen tool length? Because with only one tool I think the error wont occur.

Max

3
Still no results.. it seems to only act this way inside a tool-change cycle.
It also moves Z-Axis when approaching the sensor.. so even before any G43 movement.

Greetings,
Max

4
The problem is that its hard to reproduce outside of the M6end file
But I will try this today to maybe isolate it a bit more.
Isnt there maybe a basic mach3 setting or "mode" that triggers this behaviour? (that I missed)

Max

5
I already commented the macro call out (just blinking leds..) without any success :/
But ill try it again when im back home.. maybe i missed something.

Is this a wrong syntax for msgbox?
The german text says that no tool number was chosen


Max

PS:

The M6start:

Code: [Select]


'Save coolant
SetUSERLED(1200, 1)
If GetOEMLED(12) Then
DoOEMButton(114)
SetUSERLED(1200, 0)
End If


SetOEMDRO(1216,GetOEMDRO(83))  'Save x
SetOEMDRO(1217,GetOEMDRO(84))  'save y

Code "M1001"
Code "G0G53 Z" & GetOEMDRO(54)
While IsMoving()
Wend
code "g0 g53 x" & GetOEMDRO(33) & "g0 g53 y" & GetOEMDRO(34)
While IsMoving()
Wend



tool = GetSelectedTool()
SetCurrentTool( tool )

6
I found my code on dropbox:

Code: [Select]
'code "M1002"

 DeActivateSignal(Output14)
 DeActivateSignal(Output16)
 DeActivateSignal(Output17)

If GetOEMDRO (24) <>0 Then


code "g0 g53 x" & GetOEMDRO(1218) & "g0 g53 y" & GetOEMDRO(1219) 'Move to Tool-Probe
While IsMoving()
Wend
   

code "g0 g53 x" & GetOEMDRO(1218) & "g0 g53 y" & GetOEMDRO(1219) 'Go to probe Position
While IsMoving()
Wend

'Probing process
code "g0 g53 z" & -GetOEMDRO(1220)
While IsMoving()
Wend
code "g31 z-1000 f700" 
While IsMoving()
Wend
code "M1002"
code "M1010"
code "g53 g0 z" & GetOEMDRO(85)+3
While IsMoving()
Wend
code "g31 z-1000 f50"
While IsMoving()
Wend
code "M1002"





Axis_Pos = GetOEMDRO(85)
Tool_Offset = Axis_Pos
Call setOEMDRO(42, Tool_Offset)

        Code "G0G53 Z" & GetOEMDRO(54) 'safe-Z
While IsMoving()
Wend
        Code "G0G53 X" & GetOEMDRO(1216) & "G0G53 Y" & GetOEMDRO(1217)
While IsMoving()
Wend


'Restart coolant
If GetUSERLED(1200)<>1 Then
If GetOEMLED(12) Then
Else
DoOEMButton(114)
End If
SetUSERLED(1200, 1)


End If



Else
MsgBox "Keine Werkzeug-Nummer gewählt",0
End If 

Still makes no sense to me :/
But thanks for your effort!

Max

7
Unfortunately m at work right now.
I will post it when im back home.

But the problem , as mentioned above, also occurs before the probing routine (when i change the tool length manually while the spindle is at the change position)
There is the same positioning code, except it has the sensor coordinates as target.
There are just some output switch commands for leds and one If(reference check I think) before the positioning (probably not the problem)

It just acts like it _has_ to set the tool zero as its absolute zero everytime in this M6end file

Max


8
Im using the ethernet smoothstepper, but no idea if this can be a problem with the controller?

This snippet is from the M6end file

basically the same code is used in a dedicted probing routine that just measures the tool height and works without problems.

It must have something to do with previous z-correction commands or something alike.

If i change the tool offset _before_ the M6end toolprobe routine. It even tries to correct it when approaching my tool-probe.
(That means it crashes into my 4th axis when given a more negative value because the tool sensor is right behind it and it makes an interpolated move between programmed move and Z correction value.

Max

9
I also seperated the x and y commands
it doesnt matter
it tries to "correct" the zero plane to the mill tip on the first x or y move

10
Hello,

It seems that all my problems are related to some sort of weird axis movement (normally Z)

But now it should be a basic mach3 thing that i simply dont see.

How can this behaviour be disabled:

In my M6END file:

After probing a tool and retracting from the sensor I make X&Y movement to the workpiece but my Z-Axis moves the difference between the last during that move!

Code: [Select]

...
Tool_Offset = getVar(2002)+GetOEMDRO(49) 'get probe-trip abs
Call setOEMDRO(42, Tool_Offset)


        Code "g0 g53 Z" & GetOEMDRO(54)
While IsMoving()
Wend
Code "g0 g53 Y" & GetOEMDRO(1217) &"g0 g53 X" & GetOEMDRO(1216)  
While IsMoving()
Wend
...

means: on the "Code "g0 g53 Y" & GetOEMDRO(1217) &"g0 g53 X" & GetOEMDRO(1216)  
      While IsMoving()
      Wend" it also starts to moves the Z-Axis simultaneously (this often triggers the Z-Limit switch)

Any ideas what Im missing here?

Thanks!

Pages: 1 2 3 4