Planning to Retrofit a Mazak Integrex200Y Mill-Turn Machine

More
1 year 6 months ago - 1 year 6 months ago #326260 by jochen91
Hi Tommy,

i think i never used the lower case "s". I used the millturn.comp for this function. Here is the part from my comp file:

EXPORT_SYMBOL(kinematicsType);
EXPORT_SYMBOL(kinematicsSwitchable);
EXPORT_SYMBOL(kinematicsSwitch);
EXPORT_SYMBOL(kinematicsInverse);
EXPORT_SYMBOL(kinematicsForward);

static hal_u32_t switchkins_type;

int kinematicsSwitchable() {return 1;}

int kinematicsSwitch(int new_switchkins_type)
{
switchkins_type = new_switchkins_type;
rtapi_print("kinematicsSwitch(): type=%d\n",switchkins_type);
// create case structure for switchable kinematics
switch (switchkins_type)
{
case 0: rtapi_print_msg(RTAPI_MSG_INFO,
"kinematicsSwitch:TYPE0\n");
*haldata->kinstype_is_0 = 1;
*haldata->kinstype_is_1 = 0;
break;
case 1: rtapi_print_msg(RTAPI_MSG_INFO,
"kinematicsSwitch:TYPE1\n");
*haldata->kinstype_is_0 = 0;
*haldata->kinstype_is_1 = 1;
break;
default: rtapi_print_msg(RTAPI_MSG_ERR,
"kinematicsSwitch:BAD VALUE <%d>\n",
switchkins_type);
*haldata->kinstype_is_1 = 0;
*haldata->kinstype_is_0 = 0;
return -1; // FAIL
}
return 0; // ok
}
Last edit: 1 year 6 months ago by jochen91.

Please Log in or Create an account to join the conversation.

More
1 year 6 months ago - 1 year 6 months ago #326264 by Aciera
The message about 'undefined symbol: kinematicsSwitch' is actually a spurious error that will pop up whenever the kinematic fails to load.
I believe the actual problem is:
Code:
rtapi_app: caught signal 11 - dumping core

which unfortunately is a bit cryptic.

I would start out with an unmodified 'xyzcb_tdr_kins.comp' and do the modifications in small steps while frequently 'halcompiling' the file to find out when it breaks.
Last edit: 1 year 6 months ago by Aciera.

Please Log in or Create an account to join the conversation.

More
1 year 6 months ago #326267 by jochen91
I had problems during the installation of linuxcnc irrc i had to manual mount the usb drive. how should i continue I'm a bit clueless :(

Please Log in or Create an account to join the conversation.

More
1 year 6 months ago #326268 by Aciera
You might have missed edit in the last post

I would start out with an unmodified 'xyzcb_tdr_kins.comp' and do the modifications in small steps while frequently 'halcompiling' the file to find out when it breaks.

The following user(s) said Thank You: jochen91

Please Log in or Create an account to join the conversation.

More
1 year 6 months ago #326274 by Aciera
You are missing this line in your kinematic component:
Code:
res += hal_pin_float_newf(HAL_IN ,&haldata->angleXX ,comp_id,"%s.angleXX" ,HAL_PREFIX);
The following user(s) said Thank You: jochen91

Please Log in or Create an account to join the conversation.

More
1 year 6 months ago - 1 year 6 months ago #326343 by jochen91
Hello Aciera,

yeah that was basically the problem. I could figure it out with your suggestion with the frequent halcompile way, but this was the culprit. Now it works and i started working on vismach.

I figured out how vismach works and started to modify an existing configuration. But in general its a bit of a pain.

I wonder if its possible to give feedback to the dev-Team in terms of new ideas?

I think it could be done easier, more comfortable and more accurate if it would be possible to export the already animated and set up machine out of Freecad and then just implement it into LCNC. Which would result in a proper machine simulation just as the big boys do it (siemens/fanuc etc.)

It is nice to import .obj and .stl but fitting them together is somehow a bit painful.

Even the documentation has a nice little note:
Code:
part = Capture() I have no idea what this does ! But it seems to be important for tool tip visualization…

But anyway, thank you so far for the great support!
Last edit: 1 year 6 months ago by jochen91.

Please Log in or Create an account to join the conversation.

Time to create page: 0.082 seconds
Powered by Kunena Forum