Sorry, this line
*bldc.**N**.drive-offset* float rw (default: *0*)
The angle, in degrees, applied to the commanded angle by the drive in
degrees. This value is only used during the homing sequence of drives with
incremental encoder feedback. It is used to back-calculate from commanded
angle to
What does # before line mean ?
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users
*bldc.**N**.encoder-offset* s32 rw [if personality & 0x0A] (default: *0*)
The offset, in encoder counts, between the motor electrical zero and the
encoder zero modulo the number of counts per electrical revolution
I believe it's this line , my encoder is set to 1000 ppr , 1/2 revolution
per
Try this
https://photos.app.goo.gl/wk5hmCqTuujFq9vc8
Thank you
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
On Mon, Aug 13, 2018, 9:09 PM Gene Heskett wrote:
> On Monday 13 August 2018 21:52:44 jeremy youngs wrote:
>
> > I loadrt hostmot2
> >
> > And 7i90 at the top so it can find the 7i90 pins ( it was failing to
> > do that )
> > Now it gives this , I'm close , I can feel it , but I'm also ignorant
Is not you. The links are wrong.
In Google drive, if you right click the document and click share link,
it will copy the share link to the clipboard.
Then paste into your email.
Dave
On 8/13/2018 10:06 PM, Gene Heskett wrote:
On Monday 13 August 2018 21:52:44 jeremy youngs wrote:
I loadrt
On Monday 13 August 2018 21:52:44 jeremy youngs wrote:
> I loadrt hostmot2
>
> And 7i90 at the top so it can find the 7i90 pins ( it was failing to
> do that )
> Now it gives this , I'm close , I can feel it , but I'm also ignorant
> ant trying , lol. Sometimes that's all a steer can do to .
>
I loadrt hostmot2
>
And 7i90 at the top so it can find the 7i90 pins ( it was failing to do
that )
Now it gives this , I'm close , I can feel it , but I'm also ignorant ant
trying , lol. Sometimes that's all a steer can do to .
terminal qi.jpg
On 08/13/2018 09:39 AM, Chris Radek wrote:
So I encourage you going to LinuxCNC with an open mind and
not trying to implement everything your old control had,
whether it makes sense or not.
Yes, I agree. The way the 3D preview and bounds checking is
implemented in Axis, you get a lot of
On Monday 13 August 2018 10:39:03 Chris Radek wrote:
> On Tue, Aug 07, 2018 at 08:17:03PM -0600, Brent Loschen wrote:
> > And now for my question.?? The old Bridgeport had a button on the
> > front panel titled "No Z" that turned off all z motion and let me
> > "air mill" a part as a sanity check
On 13 August 2018 at 15:34, jeremy youngs wrote:
> Got the pin naming figure out , now to assign the pins to mesa card. I'm
> rather unclear about that , I would like them to come out to the pwm/
> direction pins currently assigned on 7i90
That is the only ones it makes sense to assign to.
On Tue, Aug 07, 2018 at 08:17:03PM -0600, Brent Loschen wrote:
>
> And now for my question.?? The old Bridgeport had a button on the front
> panel titled "No Z" that turned off all z motion and let me "air mill" a
> part as a sanity check of my X & Y boundaries/fixtures.??
First
Got the pin naming figure out , now to assign the pins to mesa card. I'm
rather unclear about that , I would like them to come out to the pwm/
direction pins currently assigned on 7i90 I think just copy and paste out
of current 7i90 config to the bldc config then attempt a start and see if
it goes
On 13 August 2018 at 01:54, jeremy youngs wrote:
> At 4.2 hal tutorial, connect pins to signals , the bldc docs don't give any
> signals , are there none to be net commanded ?
Signals are something that you make yourself. There are _no_
predefined signals in LinuxCNC.
The stepconf and pncconf
14 matches
Mail list logo
