Doosan MX2100ST Fanuc 31i Model A
Hello @ubi.james13
If turret 2 on all the machine does not support Y axis, then you could have grouped into one post doing the following changes.
In the global section add the following variable
var turret1GotYAxis = false;
then in the onOpen function
machineConfigurationMainSpindle = gotBAxis ? new MachineConfiguration(bAxisMain, cAxisMain) : new MachineConfiguration(cAxisMain);
machineConfigurationSubSpindle = gotBAxis ? new MachineConfiguration(bAxisSub, cAxisSub) : new MachineConfiguration(cAxisSub);
machineConfigurationMainTurret2 = new MachineConfiguration(cAxisMain);
machineConfigurationSubTurret2 = new MachineConfiguration(cAxisSub);
}
machineConfiguration = new MachineConfiguration(); // creates an empty configuration to be able to set eg vendor information
turret1GotYAxis = gotYAxis; // add this line
if (!gotYAxis) {
yOutput.disable();
}
aOutput.disable();
if (!gotBAxis) {
bOutput.disable();
}
finally in the onSection function
// Detect machine configuration
if (activeTurret == 2) {
machineConfiguration = (currentSection.spindle == SPINDLE_PRIMARY) ? machineConfigurationMainTurret2 : machineConfigurationSubTurret2;
gotYAxis = false; // addition
yOutput.disable(); // addition
} else {
machineConfiguration = (currentSection.spindle == SPINDLE_PRIMARY) ? machineConfigurationMainSpindle : machineConfigurationSubSpindle;
gotYAxis = turret1GotYAxis; // addition
if (!gotYAxis) { // addition
yOutput.disable(); // addition
} // addition
}
If you test this solution, please provide feddback.
Have a pleasant day.
Cheers
______________________________________________________________
If my post answers your question, please click the "Accept Solution" button. This helps everyone find answers more quickly!
Hello @ubi.james13
we can use a similar trick for this issue.
In the global section add the following variable
var turret1ToolFormat;
then in the onOpen function
machineConfiguration = new MachineConfiguration(); // creates an empty configuration to be able to set eg vendor information
turret1GotYAxis = gotYAxis;
turret1ToolFormat = toolFormat; // new addition
if (!gotYAxis) {
yOutput.disable();
}
after in the onSection function
// Detect machine configuration
if (activeTurret == 2) {
machineConfiguration = (currentSection.spindle == SPINDLE_PRIMARY) ? machineConfigurationMainTurret2 : machineConfigurationSubTurret2;
gotYAxis = false;
yOutput.disable();
toolFormat = CreateFormat({decimals:0, width:4, zeropad:true}); // new addition
} else {
machineConfiguration = (currentSection.spindle == SPINDLE_PRIMARY) ? machineConfigurationMainSpindle : machineConfigurationSubSpindle;
toolFormat = turret1ToolFormat; // new addition
gotYAxis = turret1GotYAxis;
Finally still inside onSection, at the toolchange output:
} else {
// preload first tool
var section = getSection(0);
var firstToolNumber = section.getTool().number;
if ((tool.number != firstToolNumber) && (section.getTool().turret != 2)) {
writeBlock("T" + toolFormat.format(firstToolNumber * 1000), formatComment("NEXT TOOL"));
}
}
if (activeTurret == 2) { // addition
writeBlock("T" + toolFormat.format(tool.number * 1000 + compensationOffset));
} else { // addition
writeBlock("T" + toolFormat.format(tool.number * 100 + compensationOffset)); // addition
} // addition
} else {
As previously, test with care, and don't hesitate to provide feedback.
Regards.
______________________________________________________________
If my post answers your question, please click the "Accept Solution" button. This helps everyone find answers more quickly!
Hi @ubi.james13
my fix had been created from brain cells brewing, but not completely tested.
Here is a revised post with the following changes:
I removed some extra empty lines, because we use eslint and it's done automatically when saving the file.
I added a missing semi colon at the end of a line.
I added a constant on the warningOnce command.
The main issue was probably the CreateFormat, instead of a createFormat.
And i may i have forgottent to change the multiplying factor on the tool number (100 instead of 1000 for turret 2)
Cheers
PS the file is zipped just to please the file uploader script of the forum.
______________________________________________________________
If my post answers your question, please click the "Accept Solution" button. This helps everyone find answers more quickly!
Hi @ubi.james13
You can either share a link to your Fusion file. See:
https://knowledge.autodesk.com/support/fusion-360/learn-explore/caas/sfdcarticles/sfdcarticles/How-t...
or you can save an archive (f3d, or f3z) and share it on the forum
https://knowledge.autodesk.com/support/fusion-360/troubleshooting/caas/sfdcarticles/sfdcarticles/How...
Because i have no idea, about the strategy being used, where this code is generated and why.
If it's written as pure test (i doubt) it will not use the yOuput variable.
Or it is using something else with a Y prefix, it's impossible to tell just from this picture of the code.
Hello @ubi.james13
As a reply to the post #9, to solve the Y axis issue, some codes need to be moved further down.
This piece of code should be placed much below than i first suggested
In the onSection function
// Detect machine configuration
if (activeTurret == 2) {
machineConfiguration = (currentSection.spindle == SPINDLE_PRIMARY) ? machineConfigurationMainTurret2 : machineConfigurationSubTurret2;
gotYAxis = false; // addition, we will move somewhere else, can be deleted here
yOutput.disable(); // addition, we will move somewhere else, can be deleted here
} else {
machineConfiguration = (currentSection.spindle == SPINDLE_PRIMARY) ? machineConfigurationMainSpindle : machineConfigurationSubSpindle;
gotYAxis = turret1GotYAxis; // addition, can be deleted here
if (!gotYAxis) { // addition, we will move somewhere else, can be deleted here
yOutput.disable(); // addition, we will move somewhere else, can be deleted here
} // addition, we will move somewhere else, can be deleted here
}Scrolling down in the function, seach for the invertAxes function call.
// invert axes for secondary spindle
if (getSpindle(PART) == SPINDLE_SUB) {
invertAxes(true, false); // polar mode has not been enabled yet
}
if (activeTurret == 2) { // addition
gotYAxis = false; // addition
yOutput.disable(); // addition
} else { // addition
gotYAxis = turret1GotYAxis; // addition
if (!gotYAxis) { // addition
yOutput.disable(); // addition
} // addition
} // addition
// Position all axes at home
if (insertToolCall && !machineState.stockTransferIsActive) {
moveSubSpindle(HOME, 0, 0, true, "SUB SPINDLE RETURN", false);
Regards.
Hi @ubi.james13
to fix the issue with the spindle code, you can proceed as follow:
search for the getCode function, then inside the function, find the code below, and add the commented lines (// change)
case "SELECT_SPINDLE":
switch (spindle) {
case SPINDLE_MAIN:
machineState.mainSpindleIsActive = true;
machineState.subSpindleIsActive = false;
machineState.liveToolIsActive = false;
return 11;
case SPINDLE_LIVE:
machineState.mainSpindleIsActive = false;
machineState.subSpindleIsActive = false;
machineState.liveToolIsActive = true;
if (currentSection.getTool().getTurret()> 1) {; // change
return 22;; // change
} else {; // change
return 12;; // change
}; // change
case SPINDLE_SUB:
For the G17 issue, is this for drilling operations, or for alll milling operation?
Because circular interpolations may be incorrect, if we don't use the correct plane.
What is the toolpath involved, machining on the part front, or outer diameter?
Regards.
______________________________________________________________
If my post answers your question, please click the "Accept Solution" button. This helps everyone find answers more quickly!
Hi @ubi.james13 ,
apparently when i copy and pasted the code, additional semicolon where inserted after the {, ] and ;
This was not intended. But that not the issue.
Actually i only switch to 22 when using the lower turrey, detected by this information.
So i find it strange that you added the code to your upper turret post.
Are you using the turret number in Fusion?
Regards.
Regarding the G19/G17 issue, is this for drilling operations, or for all milling operations?
Because circular interpolations may be incorrect, if we don't use the correct plane.
What is the toolpath involved, machining on the part front, or outer diameter?
Regards.
