Showing results for 
Search instead for 
Do you mean 
Reply
Solved! Go to solution

Read ahead problems

Having trouble with read ahead variables. mom_nxt_pos(0) as an example.

 

mom_prev_pos(0)  works fine

 

in same location, mom_nxt_pos(0) does not

 

       MOM: Invalid address expression: $mom_nxt_pos(0)

 

any ideas?

 

18 REPLIES

Re: Read ahead problems

Sorry -

 

Post Builder 10.0.3 MP8

 

thanks

Re: Read ahead problems

Try adding

global mom_kin_read_ahead_next_motion
set mom_kin_read_ahead_next_motion        TRUE
MOM_reload_kinematics

to the very beginning of your post.

Marek Pawlus, NCmatic

Production: NX 11.0.1
Development: C#, Tcl/Tk, CSE

Re: Read ahead problems

now the post does not error - thanks

 

but returns the current poistion, not the next position.

Re: Read ahead problems

That is strange. I didn't have such problem yet. More likely I would expect that mom_nxt_pos is not avaliable than it gives current value instead.

Marek Pawlus, NCmatic

Production: NX 11.0.1
Development: C#, Tcl/Tk, CSE

Re: Read ahead problems

Where - what event(s) are you looking for the "nxt" pos?

Note that look ahead is generally useless until you get to at LEAST "initial" and "first" move events (I keep forgetting the results of my testing - it may be useless until the next event AFTER "initial" / "first" move events)

 

 

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP5 + patch/TC11.2
I'd rather be e-steemed than e-diseaseled


Re: Read ahead problems

Need "look ahead" ( $mom_nxt_pos(0) ) to apply G65 U V W A C offsets. Mazak-Vari Axis

 

Note output below - the 1st example of G65 is the problem - inside path, rotating in same tool (using different MCS to apply a Start UDE to initiate "look ahead" PB_CMD). Intial Move does not apply here. I need the next position A C rotations to be in the G65 P8000 line. Line needs to read G65 P8000 U-1. V4. W6. A-70. C0.

 

The next example works as expected - Inital Move applies at all tool changes, and I can assign rotaion to the G65 line. All is good here. ( but not using $mom_nxt_pos(0) )

 

Y-65.532
G0 Z256.75
G64 (HIGH SPEED SMOOTHING CYCLE OFF)
( NEXT OFFSETS  U-1.00 V4.00 W6.00 M54 S55 ) (ROTATED) 
(--)
G0 G53 Z0.0
(INDEX TO INDEX)
G65 P8000 U-1. V4. W6. A-90. C0.0 M54 S55
G0 G90 G55 X75. Y-65.532 A-90. C0.0
G0 G53 Z0.0
G0 G17 G90 G55 X75. Y-65.532 M3 S22000
G0 X-39.278 Y116.021 A-70.
Z159.69
Z79.608
G3 X-34.278 Y111.021 I5. J0.0
G1 X-15.668
G3 X-10.668 Y116.021 I0.0 J5.
G1 X-39.278
Y114.581
G3 X-34.278 Y109.581 I5. J0.0
G1 X-15.668
G3 X-10.668 Y114.581 I0.0 J5.
G1 Y116.021
G0 Z229.608
( NEXT OFFSETS  U0.00 V0.00 W0.00 M54 S55 ) (ROTATED) 
(--)
G0 G53 Z0.0 M9
M5
( TOOL NAME: T111_28MM_U_DRILL )
( TOOL DIAMETER: 28.000)
N30 T109 M6
G80 G17 G90 G40 G21 G54 G94 M8
M1
T103
G0 G53 Z0.0 M133
G65 P8000 U0.0 V0.0 W0.0 A-90. C0.0 M54 S55
G0 G90 G55 X0.0 Y0.0 A-90. C0.0
G0 G53 Z0.0
G0 G17 G90 G55 X0.0 Y0.0 M3 S5000
Z150.5 M8
G83 X0.0 Y0.0 Z93. R128.5 F400. Q5.
G83 X81. Y-26.5 Z18.6 R109.5 Q5.
G80
G0 Z150.5
G0 G53 Z0.0 M9

 

thanks for the help

Re: Read ahead problems

Hi,

"look ahead" is not the best decision to define index rotation, especially in the situation when "rotating in same tool". Sometimes you are not able to get correct "next" values for "first move" event.

I prefer another idea - not to output the rotation until I get the actual data.

Re: Read ahead problems

How then would you recommend filling out an offset line for compensating rotation? Post processing 1st - getting the roation then manually inserting?

I have 127 tools, with mutiple rotations.

thanks

Re: Read ahead problems

Hi,

I say nothing about "manual inserting".

Do it on "initial" / "first" move event.

Do you try to output the offset line before this event, using "next" variables?

 

Learn online





Solution Information