Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.
lekonna
1948 Views, 4 Replies

Post processor development function reference

Hi,

 

So i'm looking into implementing a post processor for a device (Brother tc-215) that doesn't actually really support G-code. However it is possible to edit the programs in the computer, so in theory i think it would be possible to modify the post processors within certain limits to also suite this machine.

 

My question is:

Is there a function reference to the post processors somewhere available?

 

What functions do i have in my use, what variables do i have provided by the system? 

 

What are the member functions for currentSection ect, is this information somewhere available? 

 

When i look at the ready made posts, and find things like this:


function onCyclePoint(x, y, z) {
var probeWorkOffsetCode;
if (isProbeOperation()) {
var workOffset = probeOutputWorkOffset ? probeOutputWorkOffset : currentWorkOffset;
if (workOffset > 99) {
error(localize("Work offset is out of range."));
return;
} else if (workOffset > 6) {
probeWorkOffsetCode = probe100Format.format(workOffset - 6 + 100);
} else {
probeWorkOffsetCode = workOffset + "."; // G54->G59
}
}

if (isFirstCyclePoint()<--not defined in this file) {
repositionToCycleClearance(cycle<--huh?, x, y, z);

// return to initial Z which is clearance plane and set absolute mode

var F = cycle.feedrate;
if (properties.useG95) {
F /= spindleSpeed;
}
var P = (cycle.dwell == 0) ? 0 : clamp(1, cycle.dwell * 1000, 99999999); // in milliseconds

switch (cycleType) {

        ^^^^^^^^^---first reference to this variable in the whole file

 

 

It makes me feel like there is most likely a lot that i'm missing. I've found a PDF document that described some of this, but that was out of date and the examples provided did not work. 

 

So, is there a reference on what all is usable for the post developer ? I mean with the examples provided one could in theory modify the current ones with trial and error to suit, but seems like a really backwards way of approaching this problem.

 

best regards,

Janne