Posting things I have not seen has anyone seen this?

[crazy^millman]

I can not figure out why this xabs prv_xabs yabs prv_yabs zabs prv_zabs p_abs prv_p_abs s_abs prv_s_abs is being put in.

 

Sample of posted code:

code:

---

%                             pheader$ pheader$ 46.

O0000 ( :0000 ) pheader$ pheader$ 46.

(PROGRAME - PR-R2252699-0001-2 ) pheader$ pheader$ 46.

(PROVEN DATE / / ) pheader$ pheader$ 46.

(CUST-) pheader$ pheader$ 46.

(P/N-) pheader$ pheader$ 46.

(SEE-SU-SHEET) pheader$ pheader$ 46.

(POST DATE - 19-11-05 TIME - 10:38 ) pheader$ pheader$ 46.

(POSTED FOR MITSUI5AX) pheader$ pheader$ 46.

(RON BRANCH) pheader$ pheader$ 46.

( T53 | 1/2 ENDMILL ) pwrtt$ p__73:2276 46.

G0 G17 G40 G80 G90 G94 G98 psof$ psof$ 48.

G28 G91 Z0. psof$ prefreturn 48.

xabs prv_xabs yabs prv_yabs zabs prv_zabs p_abs prv_p_abs s_abs prv_s_abs G0 G55 G90 X40. Y0. A0. B29. M5 psof$ psof$ 48.

M00 psof$ psof$ 48.

xabs prv_xabs yabs prv_yabs zabs prv_zabs p_abs prv_p_abs s_abs prv_s_abs G5.1Q1R1 psof$ p_goto_strt_tl 48.

N5300 ( 1/2 ENDMILL ) psof$ ptoolcomment 48.

G0 G55 G90 X-12.2398 Y13.7205 B0. A149.166 S6000 M3 psof$ p__4:1217 48.

G43 H53 Z23.8172 M8 psof$ p__8:1239 48.

---

From .pst of updated through .dll:

code:

---

psof$            #Start of file for non-zero tool number             

 

##### Custom changes allowed below #####

if ntools$ = one,

[

#skip single tool outputs, stagetool must be on

stagetool = m_one

!next_tool$

]

#if progno = zero, progno = one

 

# *progno, *sopen_prn, "PROGRAM - ", progname, *sclose_prn, e

# pbld, n, *sopen_prn, "DATE - ", date, " TIME - ", time, *sclose_prn, e

#pbld, n, *smetric, e

 

 

if mr4$ = 0, pbld, n$, *sg00, *sgplane, *sg40, "G80", *sg90, *sgfeed, *sg98, e$

if mr4$ = 1, "/", n$, *sg00, *sgplane, *sg40, "G80", *sg90, *sgfeed, *sg98, e$

if mr4$ = 2, pbld, n$, *sg00, *sgplane, *sg40, "G80", *sg90, *sgfeed, *sg98, e$

 

sav_absinc = absinc$

absinc$ = one

prefreturn #xout, p_out not output here

absinc$ = zero

p_absinc_chng

if mr4$ = 0, "G0", pwcs, "G90", "X40.", "Y0.", "A0.", "B29.", "M5", e$

if mr4$ = 1, "/", "G0", pwcs, "G90", "X40.", "Y0.", "A0.", "B29.", "M5", e$

if mr4$ = 2, "G0", pwcs, "G90", "X40.", "Y0.", "A0.", "B29.", "M5", e$

prv_p_out = 0

prv_s_out = 30

if mr4$ =0, "M00", e$

if mr4$ =1, "/", "M00", e$

if mr4$ =2, "M00", e$

seqn = 0

#ptoolcomment

comment$

pcan

 

##### Stop custom changes #####

---

So if you got to here can you please be of help.

 

[ 11-19-2005, 02:22 PM: Message edited by: Crazy^Millman ]

[Paul Decelles]

Ron send us the original v9 .pst and .txt and zip2go the offending file (along with your X .control .mmd and .pst files). I'll get someone to look at it Monday morning.

[crazy^millman]

Well I am home now so Monday when I get it I will send you everything.

 

Thanks

[WeGrok69]

It sounds like you accidently deleted a # sign

in the post-like if you forget an end ) and the whole program is a comment

[crazy^millman]

Yeah you might think that but since it is how it is straight from the update utility I kind of ruled that out. Also it is from varaibles that I am sure are coming out of the .psb and since I was using a variable that most MPGEN5AX posts use and my use of the Mr4 is problay what is giving the error output. Thanks

[Don S at Barefoot CNC South]

Ron

Try putting a space in after

= 1

= 2

= 3

 

 

code:

---

prv_p_out = 0      prv_s_out = 30      if mr4$ =0, "M00", e$      if mr4$ =1, "/", "M00", e$      if mr4$ =2, "M00", e$      seqn = 0      #ptoolcomment      comment$      pcan      ##### Stop custom changes #####    

---

[Don S at Barefoot CNC South]

Opps

= 0

= 1

= 2

[Tim Johnson]

Your debugger is not showing postblock "p_absinc_chng" You might try looking for something there.

[Paul Decelles]

Ron,

I know Ke took a look at your post and found that the initialization for result had been commented out as a duplicate declaration - both in the .pst portion and in the .psb portion. I'm not entirely sure why this occured and we haven't been able to recreate the problem (so I'm guessing it may have been a bug that has been fixed - either directly or inadvertantly). In any case, I would recommend looking at the error log if you have any issues with output (you may have to change the settings in the Files topic in your CD to always save the error log to view it). In this case a quick look at it and the approx 30 - 40 lines of errors reported turned up the problem pretty quickly (the common denominator was he result variable).

[crazy^millman]

Result fixed that problem. Thanks.