Messages

21

General Mach Discussion / Re: Why Is this happening?

« on: September 07, 2015, 03:45:55 PM »

Another strange thing

I have tried to remove the feed rate issue altogether

by changing the two code lines to  G00 A47  and G00 A45  (rapid traverse)

and it is just the same slow on the first cycle fast on the rest !!!!!!!!



Where is the feed rate for G00 set?



The screen set I am using has feederate option G94 and G95

In one of my textbooks it says Fanuc type lathe controls normally use G98 and G99

Does anyone know what is correct for mach lathe?


Cheers George

22

General Mach Discussion / Re: Why Is this happening?

« on: September 07, 2015, 07:12:53 AM »

One other thing I have noticed is that if I go into

config ports and pins when I come out of it

and try turret it reverts back to slow feed

for first cycle.

George

23

General Mach Discussion / Re: Why Is this happening?

« on: September 06, 2015, 10:48:56 AM »

Hi Gerry

Dim T1 As Long
Dim T2 As Long
Dim T3 As Long

DoOEMButton(1011)'Zero A axis DRO

DoOEMButton(303)'MPG Velocity Only

T1 = GetOEMDRO(102) 'current encoder count

Code (" G01 A47 F900") 'move 47deg anticlockwise fast
   While (IsMoving())
      Sleep (100)
   Wend
Code ("G01 A45 F200") 'move 2Deg clockwise slowly
   While (IsMoving())
      Sleep (100)
   Wend

T2 = GetOEMDRO(102) 'new encoder count

T3 = T2 - T1

SetOEMDRO(1999,T3)'Put value T3 into Encoder DRO


Note without DoOEMButton(303) it always runs slow


cheers George 

ps when I tried to attach file m1200 it told me 2 error one already exists rename"

so to load just remove (duplicate)               

24

General Mach Discussion / Why Is this happening?

« on: September 06, 2015, 07:57:09 AM »

I am in the process of setting up my lathe tool turret

I am using small stepper motor, an encoder and using Pokeys 57E

I have a button via Pokeys calling a macro controlling the operation.

In the macro I have G01 code controlling the movement with a high

feed rate F900. I need this high a feed rate because of the turret gearing

It all works as expected except  when I first load up mach and try it

at this point it appears to use the feed rate in feed DRO.

It completes the cycle ok but way to slow.

Once it has completed one cycle it seems to follow the macro perfectly.

Does anyone have any ideas on what could be influencing the first cycle


Any ideas would be greatly appreciated

cheers George

25

PoKeys / Re: Pokeys 57E Encoder reset

« on: September 06, 2015, 05:51:32 AM »

Spoke too soon,  It doesn't work

The values are copied from DRO 102  to DRO 1999

and you can reset DRO 1999

but when turret starts moving again the values don't start from

zero and count up they just copy DRO 102    Obvious when you think about it

Hey Ho  I will do it as NeoTO suggested and subtract start value in script

cheers George

26

PoKeys / Re: Pokeys 57E Encoder reset

« on: September 05, 2015, 01:33:59 PM »

Hi NeoTO

Cracked it (I Think)

I set Pokeys Encoder2 DRO setting to 102  'MPG2"

Then did a short one line brain program


(ADD Input)    Mach variable  MPG2 count

(ADD Input)   No Operation

(Terminate)    DRO 1999


This just copies the values from DRO 102 to DRO 1999

then in script

SetOEMDRO(1999,0)

and it works (or seems to so far) the only thing I think I need to

check is what the transfer rate is like in real time to make sure of it's repeatability.

If it introduces too many errors I will do what you say and tweak in script.

Many Many thanks for all your help (On a Saturday Too !!!!!)

cheers George

27

PoKeys / Re: Pokeys 57E Encoder reset

« on: September 05, 2015, 12:27:07 PM »

Hi NeoTO

Many thanks for your help

I have changed the DRO used to 1999 to both Pokeys encoder DRO, and dro box via screen4

then using SetOEMDRO(1999,0) in macro

and I am just getting the same result

ie the values are in the DRO box and moving with the motor but still won't reset

Can you see what I am doing wrong?

cheers George

28

PoKeys / Pokeys 57E Encoder reset

« on: September 05, 2015, 09:00:03 AM »

I have hit a brick wall here and in desperate need of help

I am driving my lathe tool turret with a small stepper motor. The turret rapid rotates (47deg) anticlockwise past location, pawl engages then slowly rotates (2 deg) clockwise to locate etc.

I have got it working physically in that I press a button and  it indexes properly. However as a safety feature I have added an encoder to verify that it has indexed correctly.

(eventually I want to get it working automatically via  M6 macro)

I have linked the turret rotation up to A axis and that DRO is working fine. I have created a encoder count DRO  and that is mimicking the values in the Pokeys F7 table  but what I can't

get it to do is to zero. Note if I press the reset button on the F7 table it does zero but not via my macro.

What I want to achieve is the following. (encoder related only)

When the button is pressed the macro is called.
The encoder count is set to zero.
When the turret rotation is complete the encoder count value is compared with a reference value.
If it is within range proceed, if not output an error message and stop.

For the moment I have cleaned the macro down to just two lines

DoOEMButton(1011)  ' This zeros the A axis DRO and this works'   I have left this in as this proves my link from the button to the macro works

SetOEMDRO(102,0)  ' This isn't working


For information

The encoder is set up as encoder 2 in pokeys mapped to OEM DRO 102 " MPG2" and setup in config ports and pins encoders

(Also don't know if it's relevant but I am not using pokeys pulse engine)

I am pulling my hair out here so any help would be greatly appreciated

cheer George

29

Brains Development / Re: compare immediate not working

« on: June 22, 2015, 02:35:06 PM »

Hi Thomas

Hope you had a good weekend.

Thanks for that I will keep it in mind.

I managed to get the brain program working eventually. It hasn't failed

yet but I am still keeping a close eye on it for the moment. I still get the feeling

brains contains bugs but hopefully they only expose themselves during the programming

phase. If the brain proves to be unreliable I will make use of your suggestion of script.

The reason I wanted a brain to monitor the tool position is just for speed.

I thought it would mean that I could use a much shorter tool change macro.

That is my next project.

Just for information in case anyone else is looking to write a similar brain I have attached

a photo of the final program and one of it in action.

My observations/recommendations  are as follows

(the observations may or may not be correct but may allow you to spot a common trend and hence identify a bug)

1) Read poppabears user guide to brains first. (forum user documents) Wish I had found it earlier.

2) Although I could not see a reason why it should not work. The immediate compare function did

    not seem to work for me. Luckily Thomas showed me a workaround.

3) The formulae box did not like straight forward integer values. Instead they needed to be in terms of an input.

4) Could not get local variables ie V0 V1  to pass from one brain to another. If they can only stay within one brain they
   
    must be of very limited use.

5) Only use a particular output once within a brain. It might even confuse it if two or more brains are trying to output

    to the same location I don't know but worth checking if you are having problems.

6) The length of the brain seems to be an issue. For me any program over 20 line the scroll feature would kick in and incorrect results achieved.

    When reading poppabears notes I think he said 50 lines was the max but he normally stopped at 40.  Maybe screen size

   can have an influence !!.  If this is the case maybe temporarily changing the screen resolution may be a workaround.

7) If you are still struggling and needs to post for help hopefully Thomas or one of the other regular contributors will answer your call.

   I don't know where we would be without them.

Thanks Guys

George

30

Brains Development / Re: compare immediate not working

« on: June 19, 2015, 05:16:35 PM »

Hi Guys

Just a quick note to say I think I've cracked it.

I didn't manage to get two brains to swap variables

but I did manage to shorten the program so it stopped throwing up errors

basically in my first attempt I was using 4 inputs to define each tool station

if fact I just needed 3 and in some case 2

ie  input2 = 0  AND  input3 = 0   uniquely describes tool station 4    etc etc

if I get a chance over the weekend I will do a quick summary of my findings

just in case anyone else is wanting to do anything similar.


cheers George