Hello Guest it is October 31, 2020, 09:30:35 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 - octopus80

Pages: 1 2 3 »
1
General Mach Discussion / Re: DRO are not to set valeu in it
« on: October 22, 2017, 05:07:23 AM »
Hello Craig
I've tried what you wrote. For the Mach3 version that works, it's correct what you wrote. For the rest, the problem remains. We have installed 3 computers mach3 on Friday, of which 2 the same model under windows 7 is another model under windows 10 and these all showed the problem. I have a new computer 2 months old with windows 10 and also have Mach 3 geistalized without any problems. It's not the first time I'm dealing with this problem, usually I can fix this by reinstalling Mach 3 if I've removed everything from Mach 3 to the remaining files. I've installed 100 times Mach 3 but this time I'm probably not going to buy another computer for that project.

Greetings Benny

2
General Mach Discussion / Re: DRO are not to set valeu in it
« on: October 21, 2017, 03:25:44 AM »

Hello, how can I change the settings of the coordinates? For the moment, this is the most prominent explanation. I do not know why it's on most computers without problems, and with some computers it just does not work. probably again something that has to do with windows.

3
General Mach Discussion / Re: DRO are not to set valeu in it
« on: October 21, 2017, 03:13:42 AM »
I am sure that it is not the problem of the reset the machine is work for the rest fine, so the only problem is that if I have to fill in the valeu example when I am turning of the x axis it is not posible , I have this problem sometimes whit the install of Mach3 on a computer  in the most case when I remove mach3 complete and install it again the problem is solve, know I have a problem that the problem stays.

4
General Mach Discussion / DRO are not to set valeu in it
« on: October 20, 2017, 10:21:44 AM »
I have regular a  problem that I can not put valeu in the DRO in the X Y Z axis I can set them on zero but when I clik on the DRO it change the color but I can not put in a valeu.
I have clear everthing from Mach3 and install the program again but it stays the same. this problem I have whit some computers some othe computers install it whitout any problem do I have somebody any idea what the problem is and how to solve I get more the idea that it is something in Windows.

5
General Mach Discussion / Re: EMCO PC Mill and Turn 55 - Conversion
« on: January 10, 2016, 07:19:03 AM »
Do somebody have the compleet electrical schematics of the Emco PC55 Mill so that I can convert it to Mach3 whit less modification.

6
CS-Lab / Re: CSMIO IP-M very slow input
« on: May 18, 2015, 11:06:16 AM »
Hello Thomas
I have the turret working on the marco I have turn the encoder a litte bit so that there is a delay between the 2 signals.
and the major problem was that signal was triggering on the go down flank that I aspect that is was working on the going up flank.
greetings benny

7
CS-Lab / Re: CSMIO IP-M very slow input
« on: May 04, 2015, 07:44:27 AM »
,Emco PC-Turn 50

'M6Start.M1s
'Input1 is an optical sensor used to count tool positions
'Input2 is from a microswitch used to determine tool 0 position
'OUTPUT6 drives the tool changer forward, de activating it allows the tool changer to rotate back against the ratchet pawl at low power and is the default
'Un comment the Open statement, various write# statements and the close# function to write a logfile for diagnostic purposes

'Close #1
'Open "M6start_log.txt" For Output As #1 'open a file to write logs to
NewTool = GetSelectedTool()
'NewTool = 2
'Write #1, "NewTool ", NewTool
OldTool = GetCurrentTool()
'Write #1, "OldTool ", OldTool
MaxToolNum = 6 'Max number of tools for the changer
CurrPos = OldTool

While (NewTool > MaxToolNum)
    NewTool = Question ("Enter New Tool Number up to " & MaxToolNum)
Wend

    'there is nothing to do so we just exit
If (NewTool = OldTool) And (NewTool > 0) Then
   'Write #1, "New tool number is the same as old tool number. Nothing to do "
       Exit Sub
End If

'If OldTool is 0 that means we dont know where the tool changer is currently positioned and need to reference to the microswitch for tool 1 position.
    'need to establish tool 0 position from microswitch
If (OldTool = 0) Then
   'Write #1, "Old tool number is zero, looking for reference position"
   ActivateSignal(OUTPUT5)' Set toolchanger for full speed move
        'Write #1, "Activated Output 5 to enable toolchanger motor"
        ActivateSignal(OUTPUT6)' rotate tool changer forward
        'Write #1, "Activated Output 6 to set forward direction"
    While Not IsActive(INPUT2)
    Wend
    ' Input 2 must Now be active so the microswitch has been triggered at position 1
    CurrPos = 1
    'Write #1, "Reference position found "
    ' Decide whether to just stop for the normal toolchange process
    If ( CurrPos <> NewTool) Then
       DeActivateSignal(OUTPUT6)
       DeActivateSignal(OUTPUT5)
    Else
    ' Or if we actuallly wanted tool 1 then stop and lock
           DeActivateSignal(OUTPUT5) 'stop rotating forward, rotate backward now
      'Write #1, "DeActivateSignal Output 5 toolchanger reverse "
           SetCurrentTool(NewTool) 'sets up the current tool variable as the start point for a future tool change
           'Write #1, "Setting CurrentTool to NewTool value ", NewTool
           Sleep(2500) 'Allow a time interval for the toolchanger to settle back against the ratchet pawl
           'Write #1, "Waited 2.5 seconds for toolchanger to lock "
           DeActivateSignal(OUTPUT6) 'Disable toolchanger motor
           'Write #1, "DeActivateSignal Output 6 toolchanger stop "
    End If
End If

If (CurrPos <> NewTool) Then 'write the start condition to a variable
   If IsActive(INPUT1) Then
      PreviousSensorState = "Active"
   Else
      PreviousSensorState = "Inactive"
   End If
   'Write #1, "PreviousSensorState =", PreviousSensorState
   ActivateSignal(OUTPUT5)' Set toolchanger for full speed move
          'Write #1, "ActivateSignal Output 6 toolchanger go"
        ActivateSignal(OUTPUT6) 'start rotating forward
        'Write #1, "ActivateSignal Output 5 toolchanger forward "
       While CurrPos <>  NewTool
          'Some logic to ensure that we only count on the leading edge of a slot in the toolchanger optical disk
           If IsActive(INPUT1) Then
              SensorState = "Active"
           Else
              SensorState = "Inactive"
           End If
           'Write #1, "SensorState =", SensorState
           If SensorState <> PreviousSensorState Then
              If SensorState = "Inactive" Then
                 CurrPos = CurrPos +1
                 If CurrPos = 7 Then
                    CurrPos = 1
                    'Write #1, "CurrPos reached 7, reset to 1 "
                 End If
              End If
              'Write #1, "CurrPos =", CurrPos
              PreviousSensorState = SensorState
           End If
           If CurrPos = NewTool Then
                 DeActivateSignal(OUTPUT5) 'stop rotating forward, rotate backward now
                 'Write #1, "DeActivateSignal Output 5 toolchanger reverse "
                 SetCurrentTool(NewTool) 'sets up the current tool variable as the start point for a future tool change
                 'Write #1, "Setting CurrentTool to NewTool value ", NewTool
                 Sleep(1500) 'Allow a time interval for the toolchanger to settle back against the ratchet pawl
                 'Write #1, "Waited 1.5 seconds for toolchanger to lock "
                 DeActivateSignal(OUTPUT6) 'Disable toolchanger motor
                 'Write #1, "DeActivateSignal Output 6 toolchanger stop "
           End If
           sleep(200) ' just slows the iterations down a bit
           'Write #1, "Waited 0.2 second "
       Wend
       'Write #1, "should be job done "
       'Close #1
End If   


So the marco have to run on a Emco Turn 50 machine

8
CS-Lab / Re: CSMIO IP-M very slow input
« on: May 03, 2015, 01:48:02 PM »
so I use a marco and the freqence is maybe 1Hz this can not be the problem, the Macro work whit other people only it work not good whit me.
Benny

9
CS-Lab / Re: CSMIO IP-M very slow input
« on: May 03, 2015, 06:29:58 AM »
so it have only to read the inputs van de turret when it is moving and so it is not posible to read 2 inputs the same time.
so when the turret is moving you never know what place it gone stop.

10
CS-Lab / CSMIO IP-M very slow input
« on: May 01, 2015, 05:27:01 AM »
Hello do somebody have any idea what the input freqencie is from this module I can't get 2hz as input, and for a turret I am missing pulse on it when the turret is turning.
I have the idea that it is not posible to read 2 inputs tougether.
I have done this whit e LeaveBoy 77 card and never have problems whit it.

benny

Pages: 1 2 3 »