Hello...
I just wonder how to measure if stepper lost steps and come to idea to use
home switch.
But I have no idea how to implement this. The idea is simple:
1'st home the machine
2'nd make test moves
3'rd rehome machine
In rehoming the EMC just need to read position before setting new home
posi
On Wed, 2010-04-07 at 16:59 +0200, Slavko Kocjancic wrote:
> Hello...
>
> I just wonder how to measure if stepper lost steps and come to idea to use
> home switch.
> But I have no idea how to implement this. The idea is simple:
> 1'st home the machine
> 2'nd make test moves
> 3'rd rehome machine
2010/4/7 dave
>
> The accuracy of that system depends on how good your home switch is.
>
> I've always used a dial indicator against the spindle for that type of
> measurement. Same concept but easier since you don't have to home.
>
> Dave
>
> The accuracy should be good enought. I put the mark o
On 4/7/2010 5:59 PM, Slavko Kocjancic wrote:
Hello...
I just wonder how to measure if stepper lost steps and come to idea to use
home switch.
But I have no idea how to implement this. The idea is simple:
1'st home the machine
2'nd make test moves
3'rd rehome machine
In rehoming the EMC just n
2010/4/7 Alex Joni
>
>
> On 4/7/2010 5:59 PM, Slavko Kocjancic wrote:
>
>> Hello...
>>
>> I just wonder how to measure if stepper lost steps and come to idea to use
>> home switch.
>> But I have no idea how to implement this. The idea is simple:
>> 1'st home the machine
>> 2'nd make test moves
>>
Controller (EMC)"
Sent: Wednesday, April 07, 2010 5:38 PM
Subject: Re: [Emc-users] Homming error
> 2010/4/7 dave
>
>>
>> The accuracy of that system depends on how good your home switch is.
>>
>> I've always used a dial indicator against the spindle for tha
throughout your job.
>
> Greg
>
>
> - Original Message -
> From: "Slavko Kocjancic"
> To: "Enhanced Machine Controller (EMC)"
> Sent: Wednesday, April 07, 2010 5:38 PM
> Subject: Re: [Emc-users] Homming error
>
>
>
>> 2010/4
d made up steps throughout your job.
>
> Greg
>
>
> - Original Message -
> From: "Slavko Kocjancic"
> To: "Enhanced Machine Controller (EMC)"
> Sent: Wednesday, April 07, 2010 5:38 PM
> Subject: Re: [Emc-users] Homming error
>
>
>>
Dave pravi:
> In my experience with steppers that are running on the edge
> (mechanically or electrically), they almost never lose steps the same
> amount in both directions.
>
> Best thing I can think of doing is to put a 1" dial indicator on the
> questionable axis, write a test program or be
Jan de Kruyf pravi:
> Oh boy am I truly glad I am not a statistic!
>
> So the solution to the statistical dilemma is to put a mark on the
> shaft and bearing housing.
> Since we know how many mm the table moves per steppermotorrevolution
> we travel a multiple of that distance
> And the stepper sha
> I just wonder why every time I post something here got feedback (that's
> not good, just use this and .., you don't need that.. etc etc...) and
> near none gave solution?
You asked for a way to test your axis, and got 3 solutions:
* use a dial indicator
* use the home switch for probing
* mark t
Alex Joni pravi:
>> I just wonder why every time I post something here got feedback (that's
>> not good, just use this and .., you don't need that.. etc etc...) and
>> near none gave solution?
>>
>
> You asked for a way to test your axis, and got 3 solutions:
>
Maybe that is the problem. I
Slavko,
1. I understand you have a desperate need, but at the same time you
cannot hope to solve the issue with software that is still pre-alpha
stage, unless the developer of that software is willing to assist you
heavily.
2. These problems (over 30 years of working with CNC, I might say)
have al
On 04/07/2010 04:42 PM, Slavko Kocjancic wrote:
> 2010/4/7 Alex Joni
>> I would connect the home input to the probe input.
>> Home first, then do some moves, then do a probe towards zero, and look at
>> the point where the probe (home switch ) tripped.
>>
>> Note: you might have to have this connec
0,0 will not guarantee that you have not
>> lost and made up steps throughout your job.
>>
>> Greg
>>
>>
>> - Original Message -----
>> From: "Slavko Kocjancic"
>> To: "Enhanced Machine Controller (EMC)"
>> Sent: Wednesday, April 07, 2010 5
>> You asked for a way to test your axis, and got 3 solutions:
>
> Maybe that is the problem. I didn't ask for solution. (My english is not
> so good so maybe I ask by mystake.)
Ok, I didn't understand that like that.
> I propose solution. The software solution to just show message with home
> di
On Thu, Apr 8, 2010 at 11:57 AM, Alex Joni wrote:
> >> You asked for a way to test your axis, and got 3 solutions:
> >
> > Maybe that is the problem. I didn't ask for solution. (My english is not
> > so good so maybe I ask by mystake.)
>
> Ok, I didn't understand that like that.
>
> > I propose s
On 4/8/2010 7:06 AM, Bernhard Kubicek wrote:
>
> First of all, I am currently 100% ok with the way emc development is
> handled.
> For the filtering, there are two things:
> )First, the patches in axis.
> I proposed this filtering menu. The idea is to have external programs, aka
> filters, that exp
Dave pravi:
> is great, everybody should be thankfull for others work, and obviously work
> together and not against each other.
>
> I agree..
>
> Bernhard, I really appreciate your efforts at the filtering.. and the
> interaction with the other developers, Epler, Alex, Cradek, SWPadnos.and
On 9 April 2010 08:28, Slavko Kocjancic wrote:
> I do have more wishes for EMC functionality but a lot of them public
> doesn't need it. But thing's as webcam or home repport I think the
> public want just doesn't aware the benifit's of it.
I can see the value of the "homing report". Perhaps if
Andy Pugh pravi:
> On 9 April 2010 08:28, Slavko Kocjancic wrote:
>
>
>> I do have more wishes for EMC functionality but a lot of them public
>> doesn't need it. But thing's as webcam or home repport I think the
>> public want just doesn't aware the benifit's of it.
>>
>
> I can see the va
On 4/9/2010 6:46 AM, Andy Pugh wrote:
> On 9 April 2010 08:28, Slavko Kocjancic wrote:
>
>
>> I do have more wishes for EMC functionality but a lot of them public
>> doesn't need it. But thing's as webcam or home repport I think the
>> public want just doesn't aware the benifit's of it.
>>
On Fri, 09 Apr 2010 15:40 +0200, "Slavko Kocjancic"
wrote:
>
> While I'm not C programmer I throw view in source to check how to manage
> that. But I'm lost. The home routines are in separate file but are
> little complicated. I have simple aproach in mind. When home move is
> ended just ca
On 9 April 2010 15:38, John Kasunich wrote:
> it might be possible to do the detection in an external (custom) HAL
> component. The homing state is brought out on a HAL pin, so the
> component
> can know what is going on.
Thinking about it, I am not sure it needs even that. I suspect that
you c
Dave pravi:
> I agree that the "homing report" could be a valuable thing.I think
> you are assuming there is no support for a "homing report", but I didn't
> notice anyone asking if anyone thought it was a good idea or not.
> Sometimes noise will get on Servo encoder cables also and cause
The problem with the homing report is the destruction of data. When the
home position is found, the machine position count is set to zero (or
whatever the HOME_OFFSET value is). So, the old home position is
destroyed by that operation. To stay with the canonical encoder
definition as it is,
On 9 April 2010 16:41, Slavko Kocjancic wrote:
> After that I start Camera window. I right click camera window and select
> always on top and move that window over AXIS preview place. (just fit
> inside)
> After that I start Learn.py and make that window always on top too and
> move over code win
Andy Pugh pravi:
> On 9 April 2010 16:41, Slavko Kocjancic wrote:
>
>
>> After that I start Camera window. I right click camera window and select
>> always on top and move that window over AXIS preview place. (just fit
>> inside)
>> After that I start Learn.py and make that window always on top
Jon Elson pravi:
> The problem with the homing report is the destruction of data. When the
> home position is found, the machine position count is set to zero (or
> whatever the HOME_OFFSET value is). So, the old home position is
> destroyed by that operation.
>
>
Just that. Before writing
On 4/9/2010 12:04 PM, Jon Elson wrote:
> The problem with the homing report is the destruction of data. When the
> home position is found, the machine position count is set to zero (or
> whatever the HOME_OFFSET value is). So, the old home position is
> destroyed by that operation. To stay with
On 4/9/2010 12:13 PM, Andy Pugh wrote:
> On 9 April 2010 16:41, Slavko Kocjancic wrote:
>
>
>> After that I start Camera window. I right click camera window and select
>> always on top and move that window over AXIS preview place. (just fit
>> inside)
>> After that I start Learn.py and make th
You could implement a similar function using a contrived method, that is not
part of the G28 command or other homing function.
Basically you would have a subroutine to deliberately move the machine to
the home switches and write the x,y,z values to file as the switches are
crossed. Assuming they s
Dave pravi:
> On 4/9/2010 12:04 PM, Jon Elson wrote:
>
>> The problem with the homing report is the destruction of data. When the
>> home position is found, the machine position count is set to zero (or
>> whatever the HOME_OFFSET value is). So, the old home position is
>> destroyed by that op
Roland Jollivet pravi:
> You could implement a similar function using a contrived method, that is not
> part of the G28 command or other homing function.
>
> Basically you would have a subroutine to deliberately move the machine to
> the home switches and write the x,y,z values to file as the switc
> But how from Gcode Open file, add coordinate to the end and close file?
> The way can be custom program M1xx. That can open and close file and
> even write betwen. But how to retrive machine coordinate ?!? I know M1xx
> can be uset easily for output. But how to get input from HAL? I looking
> tha
On 9 April 2010 18:00, Dave wrote:
> Just has to be worked out.
This seems to pretty-much work. Note that it doesn't work unless you
put the mux and the oneshot into a thread before the motion functions.
The axis position on hitting the limit is pretty consistent (enough to
show a position loss)
Slavko Kocjancic wrote:
> Jon Elson pravi:
>
>> The problem with the homing report is the destruction of data. When the
>> home position is found, the machine position count is set to zero (or
>> whatever the HOME_OFFSET value is). So, the old home position is
>> destroyed by that operation
37 matches
Mail list logo
