On Thursday 11 February 2021 18:31:31 Jon Elson wrote:
> On 02/11/2021 04:37 PM, Gene Heskett wrote:
> > So, looking at pid.error with a 100mv/div scale, 1 div would be .1
> > degree?
>
> If you look closely at the Halscope screen, you will see
> that it does NOT show a "v".
> So, you would get a
ok.. This is my take... This is why I like
linuxcnc>-a/d>- analog drive>-servo>-encoder>-linuxcnc...
The enables are controlled by motion. The power is controlled by estop.
The PID within linuxcnc has a lot of power - saturation, following error
and so on. It can detect most all faults a
On 02/11/2021 04:37 PM, Gene Heskett wrote:
So, looking at pid.error with a 100mv/div scale, 1 div would be .1
degree?
If you look closely at the Halscope screen, you will see
that it does NOT show a "v".
So, you would get a 100m/div scale, 100 milli-somethings.
If the INPUT_SCALE or SCALE
On Wednesday 10 February 2021 23:09:36 Jon Elson wrote:
> On 02/10/2021 07:08 PM, Gene Heskett wrote:
> > But is the error also in degrees? The halsope is
> > measuriing volts and I have not found anyplace where it
> > states the error is in the same sized unit the rest of
> > that particular
I will pass this along to the FreeCAD path chat on gitter. I’m sure some people
wouldn’t mind the info in here. There is a good chunk of work being done on the
Path workbench but the feature freeze will slow things down as they try to
stabilize it for the 0.19 release.
-Thorhian
> On Feb 11,
On Thursday 11 February 2021 10:40:12 Jon Elson wrote:
> On 02/10/2021 10:37 PM, Gene Heskett wrote:
> > I went to take the bs-1 off its table, and found I can't
> > take it very far as I have negleted to build a 2nd set of
> > inline connectors so I can disconnect the encoder and
> > really take
On 02/10/2021 10:37 PM, Gene Heskett wrote:
I went to take the bs-1 off its table, and found I can't
take it very far as I have negleted to build a 2nd set of
inline connectors so I can disconnect the encoder and
really take it away. And I've yet to come up with a scheme
to detect that it is
On Thursday 11 February 2021 07:28:51 andy pugh wrote:
> On Thu, 11 Feb 2021 at 04:39, Gene Heskett
wrote:
> > I've yet to come up
> > with a scheme to detect that it is plugged in, and if not, disable
> > linuxcnc's ability to see an error because its not there
>
> I have a GPIO pin looped up
On Thursday 11 February 2021 07:17:20 andy pugh wrote:
> On Thu, 11 Feb 2021 at 03:20, Bari wrote:
> > https://dspace.mit.edu/bitstream/handle/1721.1/29225/50140264-MIT.pd
> >f
>
> One of the better PhD theses I have read. (Not that I have read all of
> it)
>
> It is interesting to think back to
On Thu, 11 Feb 2021 at 04:39, Gene Heskett wrote:
> I've yet to come up
> with a scheme to detect that it is plugged in, and if not, disable
> linuxcnc's ability to see an error because its not there
I have a GPIO pin looped up to the connector socket and back. A jumper
in the plug completes
On Thu, 11 Feb 2021 at 03:20, Bari wrote:
> https://dspace.mit.edu/bitstream/handle/1721.1/29225/50140264-MIT.pdf
One of the better PhD theses I have read. (Not that I have read all of it)
It is interesting to think back to what the state-of-the-art was in
2001. I think that I was still using
I've attached the app node pdf from Practical Micro Design for their PMDX-126.
My system is set up as in Figure 1 and at the time it seemed like a really good
idea. The trouble is a fault from any of the drives into the PMDX-125 or 126
effectively removes the ChargePump which results in all
12 matches
Mail list logo
