Roeders 5 Axis post-processor problem: Error: The probe cycle 'probing-y-plane-angle' is machine specific and must always be handled in the post configuration.

[bernard5BABD]

I am a bit stuck here. Probing WAS working just fine. Since then, I did my best to "merge" drilling operations for the 3 axis post-pro (Found in the Post Library). Problem is, the structure is very different between the 2, and I am sure I messed up somewhere.

The thing is, this error appears nowhere in the code, so I am unable to find what triggers it. Your help will be greatly appreciated.

[Tomek.G]

Hi @bernard5BABD,

Probing and drilling operations use the same function onCyclePoint()
you probably overridden probing cycles and case "probing-y-plane-angle" not exist in your post anymore.

[bernard5BABD]

yes, it does, but I will look at onCyclePoint(), my mistake should be there.

[Tomek.G]

@bernard5BABD,

I can take a look if you are open to share your post (have to be zipped).
Or share it in DM if you don't want to post it here.

[bernard5BABD]

it's still a work in progress, but "drilling" is OK (and the probe operations that I implemented are working). I am in the process of comparing the output from the Roeders 3 axis drillings operations to mine.

I got lost, as the structure is really not the same, and I have been confused (still am, just maybe a little less) by onCycle and onCyclePoint.. 

Thanks for your offer to help, I join the zipped file.

[Tomek.G · Accepted solution]

Hi @bernard5BABD,

The protectedProbeMove function is missing parentheses, so some arguments were not passed to the writeBlock function

  if (_z && z >= getCurrentPosition().z) {
    writeBlock((probeCode.code + probeCode.value), "P" + 9810, _z, getFeed(cycle.feedrate));  
  }
  if (_x || _y) {
    writeBlock((probeCode.code + probeCode.value), "P" + 9810, _x, _y, getFeed(highFeedrate));
  }
  if (_z && z < getCurrentPosition().z) {
    writeBlock((probeCode.code + probeCode.value), "P" + 9810, _z, getFeed(cycle.feedrate));
  }

You have some missed semicolons also Lines 67, 627, 936, 1276, 1431, 1759, 2098, 2455, 2488, 2780, 2913, 2919, 3375
I would recommend you to install ESLint and ESLint VSCode extension.
It is a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code, with the goal of making code more consistent and avoiding bugs.

[bernard5BABD]

Thank you very much. Did not know this tool. Right now it does not work, but I will make it work, should be extremely useful. BTW, I am surprised by Javascript "tolerance" with missing semi-colons.

Best regards,

[bernard5BABD]

ESlint is now working, looks like a really great tool. Could you share your config file?  It was showing errors for ALL variables (undef), but I would like it to do that for really undeclared variables, not all of them! 

[Tomek.G]

Hit F1 and type ESLint: Create ESLint configuration

You can then edit it.
look at no-undef rule:
https://eslint.org/docs/rules/no-undef#no-undef

[bernard5BABD]

Yes, I managed to make it work after answering you. Very nice, it allowed me to clean my code and removed quite a few unused functions.