Strange error at debugging my ATC component
20 Apr 2014 20:31 #46135
by tkamsker
Strange error at debugging my ATC component was created by tkamsker
Happy easter all.
I am quite happy so far with my ATC Component for the Bridgeport 412 ,..
It works almost as "wished" ,..
I do have a bottom which is avail by glade UI which is for resetting error state.
So if homing takes to long what ever ,..
But i get a really strange error ,..
Like this ->
on_abort executing
STATE_FAULT
Tool Changer -- Took Too Long to Move the Carousel
Press RESET to Clear
RTAPI: Task 2[0xeec12800]: Fault with vec=14, signo=11 ip=fc69e07a.
RTAPI: This fault may not be recoverable without rebooting.
So my question to the experts how do i debug that if i open the gates of hell
Setting Debug mode to highes i get a lot of info but this isn't very helpful ,..
So any hint or link would be appreciated
thx
thomas
I am quite happy so far with my ATC Component for the Bridgeport 412 ,..
It works almost as "wished" ,..
I do have a bottom which is avail by glade UI which is for resetting error state.
So if homing takes to long what ever ,..
But i get a really strange error ,..
Like this ->
on_abort executing
STATE_FAULT
Tool Changer -- Took Too Long to Move the Carousel
Press RESET to Clear
RTAPI: Task 2[0xeec12800]: Fault with vec=14, signo=11 ip=fc69e07a.
RTAPI: This fault may not be recoverable without rebooting.
So my question to the experts how do i debug that if i open the gates of hell
Setting Debug mode to highes i get a lot of info but this isn't very helpful ,..
So any hint or link would be appreciated
thx
thomas
Please Log in or Create an account to join the conversation.
20 Apr 2014 21:08 #46136
by ArcEye
Replied by ArcEye on topic Strange error at debugging my ATC component
Hi Thomas
Will need to see your component to get any idea where the problem might be
I presume that this message
is coming from your component.
regards
Will need to see your component to get any idea where the problem might be
I presume that this message
STATE_FAULT
Tool Changer -- Took Too Long to Move the Carousel
Press RESET to Clear
is coming from your component.
regards
The following user(s) said Thank You: tkamsker
Please Log in or Create an account to join the conversation.
20 Apr 2014 23:11 #46142
by tkamsker
Replied by tkamsker on topic Strange error at debugging my ATC component
Hi,
thank you for the quick response ,..
This will be a little complicated i would then have to prepare an test and sizable setup (which i will for the docu)
Because it is basically an NGC and python setup for remap the M6 for Toolchange.
It does the errohandling and stuff.
And in the middle it calls the component and asks for turn me at position x
which works fine only if error occurs (timeout ) and i try to clear it i get this error.
I was behind the "RTAPI: "
Part of that error so if i could get an dump or an hint where the error comes from it would help me a lot.
Next week i prepare an simulation able set with that component ok ?
And the code needs also a cleanup because a lot of debugging messages are still there
thx
thomas
thank you for the quick response ,..
This will be a little complicated i would then have to prepare an test and sizable setup (which i will for the docu)
Because it is basically an NGC and python setup for remap the M6 for Toolchange.
It does the errohandling and stuff.
And in the middle it calls the component and asks for turn me at position x
which works fine only if error occurs (timeout ) and i try to clear it i get this error.
I was behind the "RTAPI: "
Part of that error so if i could get an dump or an hint where the error comes from it would help me a lot.
Next week i prepare an simulation able set with that component ok ?
And the code needs also a cleanup because a lot of debugging messages are still there
thx
thomas
Please Log in or Create an account to join the conversation.
21 Apr 2014 06:53 #46155
by andypugh
You are somehow using an uninitialised pointer, or possibly working outside the valid index range of an array.
Did you write the component in "comp"? It is possible that the actual problem is that one of your comp variables matches a variable internal to comp.
(you can't have a variable called "state" for example, because comp has one.)
Replied by andypugh on topic Strange error at debugging my ATC component
RTAPI: Task 2[0xeec12800]: Fault with vec=14, signo=11 ip=fc69e07a.
You are somehow using an uninitialised pointer, or possibly working outside the valid index range of an array.
Did you write the component in "comp"? It is possible that the actual problem is that one of your comp variables matches a variable internal to comp.
(you can't have a variable called "state" for example, because comp has one.)
The following user(s) said Thank You: tkamsker
Please Log in or Create an account to join the conversation.
22 Apr 2014 14:18 #46208
by tkamsker
Replied by tkamsker on topic Strange error at debugging my ATC component
Hi,
yes you have been right you shouldn't subtract from 0 and try to get that value from an array -
But at the end Successs !!!!!
Now intensive testing is to be done next film should be integration on the bridgeport
the component itself could be used at any given turret lathe or whatever
thomas
yes you have been right you shouldn't subtract from 0 and try to get that value from an array -
But at the end Successs !!!!!
Now intensive testing is to be done next film should be integration on the bridgeport
the component itself could be used at any given turret lathe or whatever
thomas
Please Log in or Create an account to join the conversation.
Time to create page: 0.078 seconds