Brother postprocessor problem

[borut_ogrizek]

I would like switch probe on (M402, BLUM) a little early then in attached picture. I tried 2 times but gives me an error. I tried in onOpen funcition "writeBlock(mFormat.format(402);"

there is also list of my personal changes from L9 to L16.

Thanks in advance!

Borut

 

[boopathi.sivakumar]

Hi @borut_ogrizek 

Could you explain the reason behind why you want the probe to be on the mentioned line since the probe is activated right before the first XY move.?
other the code readability?

[borut_ogrizek]

Probably something is wrong, because probe plunges in to the measured piece, not always but sometimes, 

the attached picture show that at line 74 comes to the problem, but I didnt have time today to measure something.

thanks for the help in advance!

[boopathi.sivakumar]

Could you DM me the Fusion file and I guess you are using the brother speedio inspection post?

[Tomek.G]

Hi @borut_ogrizek 

Your probe is not activated! Fortunately, you didn't damage your stylus.
It appears that the Blum cycle did not switch it on. Do you have a specific M-code to activate the probe?

[borut_ogrizek]

my hand is always on potentiometer, but you never now, if is measuring move or something else. you are quickly to late

Actualy I damaged the tip

, because I insert M402 in the begining and it was working, then I process 3 programs together and than in the begining 2nd program plunges directly without stylus on. It looks like it between programs switches off and then back on again. In these days I dont have to much time to play with posprocessor, but maybe for the weekend I will find some time

[Tomek.G · Accepted solution]

Hi @borut_ogrizek,

I took a second look at the code you provided and found that right before the code to activate the probe, there is an IF statement that jumps to line number N20.
With line numbering switched off, it appears this code is being skipped. It's peculiar that the probe is moving because a non-active probe should be treated as deflected, meaning the move should be skipped.
As a suggestion, try toggling line numbering in the post properties to ensure the code executes as intended.

[borut_ogrizek]

Thank you for your suggestion for turning on line numbbering! I guess, I will make 2 posts 1 for measureing one for manufacture, because brother doesnt like numbers over 1.000.000, it throw's the error at that number. I measure two times with some short probe tip, it seems OK. 

Thank you again, Borut

[Tomek.G]

Thank you for pointing it out @borut_ogrizek

It is indeed a postprocessor issue, and we are working on a fix.
In the meantime, using line numbering is a viable workaround.