Hello Guest it is December 07, 2021, 03:57:35 AM

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 - Oldraven

Pages: « 1 2 3 4 »
11
VB and the development of wizards / need help!
« on: February 20, 2015, 05:36:49 AM »
Hello all,

I really could use some help with one command in the VB script below.

This statement works but also seeds the X- and Z-axes DRO's with random digits!
Call SetOEMDRO(824,number)                  'Set tool # in DRO
Why ??
I am working on this for almost a week now.
For the rest the script works OK.

Jos

'REM _________Script to advance ATC/Turret 1 position.____________
 
  maxtool = 6                        '# of tools in turret
  extraAngle = 6                             'Extra angle added to turret rotation
  round = 360                        'One turn in degrees of turret
  oldtool = getcurrenttool                       'Tool # before rotation
  newtool = GetOEMDRO(824)               'Get Tool #
  Angle = round/maxtool                                     'Angle of rotation i.e. 60 degrees
  number = GetOEMDro(824)                                 'Get Tool #
  
Code "G91"                        'Incremental Distance Mode  
If GetOEMDRO(824) = 0 Or GetOEMDRO(824) >6 Then
   number1 = Question("What is current tool # ?")
   Call SetOEMDRO(824,number1)
   Call SetOemDro(803,number1*round/maxtool) '803 = A Turret DRO
   Exit Sub
End If  
number=number+1                                            'add 1 to the #
If nummer>maxtool Then number=1                        'check if tool # is 6  

'After executing the next line the X- and Z- DRO's display random figures.
'I do not know why.
Call SetOEMDRO(824,number)                                 'Set tool # in DRO  

                                          'now calculate the rotation angle of turret
If number=1 Then Call SetOemDro(803,0)
ToolChange = GetOEMDRO(803)                    'Get A position
ToolChange = (round/maxtool)+extraAngle                  'Tool-change turret 60 + 6 CW
                                 
Code "G0 A" & ToolChange                                'execute rotation CW
code "G0 A" & -6                          '6 steps CCW

While IsMoving()
Wend
Call SetOEMDro(803,((number-1)*round/maxtool))
 
Code "G90"                             'back to Absolute Distance Mode

12
VB and the development of wizards / Re: Reaction time IsActive(INPUT)
« on: June 09, 2012, 01:08:14 PM »

@ TP,

I found that too, later I used G00 A10

Thanks for your code, I'll give that a try tomorrow.

This macro stuff is very difficult.

Jos
Holland
The G0 A360 command will cause the Axis to rotate to either A360 or cause it to rotate 360 degrees depending on if you are in abs or inc mode.

Nothing in your Macro will stop it from running to completion.


IF you want it to REF HOME to the switch use

Code"G28 A0.000" it will move to the switch then back off the switch untill it remakes.

(;-) TP


13
VB and the development of wizards / Reaction time IsActive(INPUT)
« on: June 09, 2012, 05:02:52 AM »
Hi,

I am trying to get my M6Start.m1s macro to home at tool #1.

I am using these lines to have the macro look at INPUT1 (port 1, pin 13)

Code "G00 A360"                        'Rotate the ATC
While Not IsActive(INPUT1)       ' Look for ATC Home pulse
 Wend               'Input #1 must be active now

However INPUT1 LED lights up but no reaction. The ATC keeps on turning.

What is happening? Is the input pulse too short?

Any help would be greatly appreciated.

Jos
Holland

14
Post Processors / Re: Solidcam 2006 Rev10 to mach2-mach3 post pro
« on: January 22, 2012, 09:21:51 AM »
Is there a solution for these messages?

I use SW2010 and Solidcam 2011. The postprocessor is from cncbasher above.
It is not possible to generate a G-code so the SC is in fact useless for me.

thanks.

Thanks Dave for the post processor. I am using Solidworks 2011 and Solidcam 2010 to Mach 3 to my new Taig mill. I am having trouble with the most recent version of this post processor. I am working in imperial units.

 I am getting error codes as follows:

"Line 430: invalid GENERATE statement"
"Line 430: unrecognized statement"


15
General Mach Discussion / Re: G53 Z0 Strange Behavior.
« on: July 11, 2011, 04:34:22 AM »
Hi Hood,

That's it !!

I just tried it, put the G0 in the line N0 along with the rest and the Z worked normal.

That simple!

Thanks,

Jos

Put a G0 before the G53Z0, either on the same line or  before and it will move at rapid rate. The reason your move will be slow on the first is it will move at the G1 feedrate you have set at the time, so if just started it is F6 as default. The second time there will have been either a G0 or a G1, with a faster feedrate, preceding the G53.
Hood

16
General Mach Discussion / G53 Z0 Strange Behavior.
« on: July 11, 2011, 03:57:45 AM »

Hello all,

I need some insight here.
At the first encounter of G53 Z0 the Z-axis rises very slow.
At the next tool changes a call for G53 Z0 is made and the Z-axis rises in normal speed.

I am at a loss, no idea what is going on.
I General Config I only have G21 in the Initialization String.

What is going on?

My G-code;
(PROGRAM NAME - BASE-2D-3.NC)
(POST - MACH 3 MILL METRIC)
(DATE - SAT. 07/09/2011)
(TIME - 09:33AM)

N01 G21 G40 G49 G54 G80 G90 G91.1
N02 G53 Z0. >>>>>                                        Here the Z-axis goes up very slowly <<<<<<

(JOB 1 CENTER HOLE RANDOM POINT PATTERN)
(2MM CENTER DRILL)

N03 M06 T1
N04 S1901 M03
ETC.

Thanks,

Jos
Holland

17
Bargain Basement / Re: probe
« on: July 08, 2011, 11:56:58 AM »
Hello Dave;
below some things I found during a session with MSM

Hi Jos,
Yep, getting into CNC with Mach can make for a steep learning curve  ;)

With MSM you are adding additional functionality beyond a stock mach setup - so some more reading is probably in you future  ;D  - fortunately, MSM has a pretty good user manual.
 
Here are some answers to your questions...
1) MSM uses mach's regular facilities for storing values entered into DROs. Whether mach remembers DRO values between mach sessions is controlled by a Mach configuration setting.
Please use the mach menu for Config/general config and in the General Logic Configuration dialog look in the area at the lower right of the dialog. There you will find the following options:
Tool Selections persistent (controls if mach remembers what tool is mounted)
>>> Is Not checked.

Persistent offsets (controls if mach remembers work coordinate offsets between sessions)
>>>  Is checked.

Persistent DROs - this is the one that controls whether Mach remembers DRO values between sessions.
>>> Is checked.
I suspect you do not have this checked, check it and your values will be saved between mach sessions.
>>> Ans Optional Offset Save is checked.

The mach configuration options are documented in the mach "install and config" manual which is available from a button on the MSM reference page.
>>> Downloaded it and started reading it.

2) probe operations use the units of the "setup units" of the machine. Thus if the machine has metric setup units the probing feeds and distances are also metric for units.
>>> It is back to Metric now, I do not know what caused it.

3) The probe tool # is DRO value - with persistent DROs off, it to will be lost between sessions.
>>> I used Tool #10 for my Probe Tool. Arbitrarely.

4) The message about step off width etc -
A side effect of having mach configured to not remember DRO values (step of width is a probing parameter DRO value).
>>> Yes, fiigured that out.

The probing parameters are documented in section 8.4 of the user manual - you can look there to see what each one is. Again, the user manual is available from a button on the MSM reference page.

5) Finally, while I'm happy to answer questions, Please drop over to the MSM user forum at www.CalypsoVentures.Proboards.com if you have more questions.
I monitor the MSM user forum but may or may not see a post about MSM here in the bargin basement area of the Mach forums.
>>> I already registered and did some reading on various subjects.
>>> Anymore questions I will ask there and free bandwith on this forum.
I have got it running again and made a screendump for assisting my memory.
Thanks,

Jos

Dave


18
Bargain Basement / Re: probe
« on: July 08, 2011, 07:15:22 AM »
Hi Dave,

Sorry but now I need some help.

After the first probing test, that worked on all tests, I shut my PC down.

Two hours later, the info I had put in in all the fields was gone. All back to zero.

So I did the input as far as I remembered ( I should have made a screendump) but I got faults.

On Z probing the probe did go down to Z-level and up, but kept on going up until the top of the Z-axis.
I had filled in for Z Clearance 10.00 as I assumed it was in millimeters.
Correcting this to 0.25 lifted the Z-probe to about 10mm.
I was certain I had filled in 10mm earlier this morning.

How do I know / set the screens for Metric millimeters??

Also the Probe Tool# is not remembered by the system.

Doing a corner probing now I get the fault; StepoffWidth <= EffprobeRadius + M -------
How do I correct this??

I was lucky early this morning it seem, all ran well but not after shutdown.
 
Regards,
Jos
Holland

19
Bargain Basement / Re: probe
« on: July 08, 2011, 04:05:56 AM »
OK Dave,

I have got it up and running.
After filling in some parameters in the probing it came to life.

I even got my sample G-code running quite quickly. But as the screens are very extensive I need some time to
get comfortable with all that.
Bear in mind that I am a relative newbie with cnc.

A lot to learn!
Solidworks 2010, Bobcad V24 and Mach3. It all keeps me off the street, grin.

Jos
Holland

20
Bargain Basement / Re: probe
« on: July 07, 2011, 11:08:16 AM »
Dave,
I have an Android too, HTC Desire.

Typing with my big fingers is a bit awkward. javascript:void(0);

I have downloaded the necessary files and will give them a try tomorrow.

Jos
Holland
www.mraven.com

Pages: « 1 2 3 4 »