On Wednesday 11 November 2015 07:59:32 Peter Blodow wrote:
> Gene,
> telling from my rusty experience from waybackwhen (and the RCA
> transmitting tube manual of 1962) I suspect that the one glowing tube
> has too much positive DC grid voltage, maybe resulting from a faulty
> driver (suspect: capa
On Wednesday 11 November 2015 07:57:03 Dr. Nikolaus Klepp wrote:
> Am Mittwoch, 11. November 2015 schrieb Gene Heskett:
> > On Wednesday 11 November 2015 05:36:22 Dr. Nikolaus Klepp wrote:
> > > Hi Gene!
> > >
> > > > Ok, I killed the Autostart file, and the delay & message lines &
> > > > made th
On 11/11/2015 12:23 PM, andy pugh wrote:
> On 11 November 2015 at 16:32, Dave Cole wrote:
>> That's basically a crankshaft position sensor.
> Some CPSes use a magnetic track (I have a few in a drawer).
> They typically use a missing tooth (normally just a shorter tooth,
> when it is a tooth) for i
On 11 November 2015 at 17:10, John Dammeyer wrote:
> In that case a switch signalling clear or midpoint would be the best option.
> If you even wanted to do speed things up a tad.
Outside of Brother demos on Youtube the tool-change time is normally a
tiny proportion of the total machining time.
On 11 November 2015 at 16:32, Dave Cole wrote:
> That's basically a crankshaft position sensor.
Some CPSes use a magnetic track (I have a few in a drawer).
They typically use a missing tooth (normally just a shorter tooth,
when it is a tooth) for index.
It would be nice to add missing-tooth index
In that case a switch signalling clear or midpoint would be the best option.
If you even wanted to do speed things up a tad.
John
> -Original Message-
> From: r...@superiorroll.com [mailto:r...@superiorroll.com]
> Sent: November-10-15 7:13 PM
> To: Enhanced Machine Controller (EMC)
> Subje
In my past life I worked with the CNC guys at Milacron in the early 90's
before the company fractured into several parts. For a period of time
Siemens sold them containers full of Servo motors and drives on a
regular basis. They were a huge Siemens customer.
Those guys were sharp. If they cou
That's basically a crankshaft position sensor.
I got the link from another guy asking if we could use it on a machine.
The gear pitch needed is .160 so at full quad the resolution should be
.040 or about a mm. There is a data sheet link on the Allied
Electronics page.
The price I think was $2
On 11 November 2015 at 13:54, Rick Lair wrote:
> How will your carousel component handle that "0"?
I don't actually know...
This is the problem with writing components that you don't actually need.
Looking at the code, it will enter state 1 then not move. Which is
probably about right.
enable g
How will your carousel component handle that "0"?
On 11/11/2015 8:42 AM, andy pugh wrote:
> On 11 November 2015 at 13:38, Rick Lair wrote:
>> I am not sure how to use the M6 command to put the currently loaded tool
>> away, back into the carousel.
>
> M6 T0
>
--
Thanks
Rick Lair
Superior R
So far I know you use a MDI_COMMAND in the .ini file and then you
connect that through halui.mdi-command-01
-- Original Message --
From: "Rick Lair"
To: "Emc Users"
Sent: 2015-11-11 15:13:57
Subject: [Emc-users] Call an M Code from a Classic ladder output
>Good Morning Gentleman,
>
>I
On 11 November 2015 at 13:38, Rick Lair wrote:
> I am not sure how to use the M6 command to put the currently loaded tool
> away, back into the carousel.
M6 T0
--
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto
---
On 11 November 2015 at 13:13, Rick Lair wrote:
> The M40 is going to "sets return-tool true", and I was going to use the
> the M39 to "sets return-tool false". Unless there is a better way to
> reset the signal without calling the M39?
Why not net a classic ladder output directly to whatever pin
I did answer my own question, I added a dwell time, then called the m39
from the m40, using subroutines.
John,
I am not sure how to use the M6 command to put the currently loaded tool
away, back into the carousel.
I am just doing this that way if the operator knows he needs to shut
linuxcnc d
I just have to wonder why your not using iocontrol.0.tool-change and
iocontrol.0.tool-changed or am I totally off track and not understanding
the application?
JT
On 11/11/2015 7:13 AM, Rick Lair wrote:
> Good Morning Gentleman,
>
> Is it possible, to call an m-code using a classicladder output?
Good Morning Gentleman,
Is it possible, to call an m-code using a classicladder output?
Now that I have my tool changer working, I am trying to work into my
ladder logic the ability to call a M40, and it will put the tool that is
in the spindle back into the carousel, and then when the logic is
Actually this is simple single axis move. Ok, so, the receipt is to
change it to Y (possible this time) and use digital out M6... commands?
Are there any plans for TP to support 6 or all 9 axes?
11/11/2015 02:51 PM, Robert Ellenberg rašė:
> Hi Marius,
>
> The problem is not the digital IO, but t
Gene,
telling from my rusty experience from waybackwhen (and the RCA
transmitting tube manual of 1962) I suspect that the one glowing tube
has too much positive DC grid voltage, maybe resulting from a faulty
driver (suspect: capacitors). The ouput power you are measuring comes
from the other 83
Am Mittwoch, 11. November 2015 schrieb Gene Heskett:
> On Wednesday 11 November 2015 05:36:22 Dr. Nikolaus Klepp wrote:
>
> > Hi Gene!
> >
> > > Ok, I killed the Autostart file, and the delay & message lines &
> > > made the link. Is this the final version? :)
> >
> > Almost :-) If you want to be
Hi Marius,
The problem is not the digital IO, but the A axis. Currently the TP does
not support arc blends between rotary axis moves, so it falls back to
parabolic blends (which can be slower for short segments).
Rob
On Wed, Nov 11, 2015, 7:31 AM Marius Alksnys
wrote:
> I want to control two d
I want to control two digital outputs while in motion without slow-down.
Now I use G1 with A axis. Neither Arc Blend TP settings in ini nor M62,
63, 64, 65 seems to help - I get a slowdown at the switching point.
--
On Wednesday 11 November 2015 05:36:22 Dr. Nikolaus Klepp wrote:
> Hi Gene!
>
> > Ok, I killed the Autostart file, and the delay & message lines &
> > made the link. Is this the final version? :)
>
> Almost :-) If you want to be almost absolutely sure that the
> xresources are changed after TDE l
Hi Gene!
> Ok, I killed the Autostart file, and the delay & message lines & made the
> link. Is this the final version? :)
Almost :-) If you want to be almost absolutely sure that the xresources are
changed after TDE loads it's theme then you should use this fragment:
# LINUXCNC
(
sle
On Wednesday 11 November 2015 03:25:09 Dr. Nikolaus Klepp wrote:
> Am Mittwoch, 11. November 2015 schrieb Dr. Nikolaus Klepp:
> > Hi Gene!
> >
> > > > or place this fragment in .xinitrc (all in one line) or any
> > > > script that gets executed when you log into your X session:
> > > >
> > > > xrd
On Wednesday 11 November 2015 03:11:17 Dr. Nikolaus Klepp wrote:
> Hi Gene!
>
> > > or place this fragment in .xinitrc (all in one line) or any script
> > > that gets executed when you log into your X session:
> > >
> > > xrdb -all -query|sed -e 's#[A-Z_]*BACKGROUND# gray90#' -e
> > > 's#[A-Z_]*FO
Am Mittwoch, 11. November 2015 schrieb Dr. Nikolaus Klepp:
> Hi Gene!
>
> > > or place this fragment in .xinitrc (all in one line) or any script
> > > that gets executed when you log into your X session:
> > >
> > > xrdb -all -query|sed -e 's#[A-Z_]*BACKGROUND# gray90#' -e
> > > 's#[A-Z_]*FOREGROU
Hi Gene!
> > or place this fragment in .xinitrc (all in one line) or any script
> > that gets executed when you log into your X session:
> >
> > xrdb -all -query|sed -e 's#[A-Z_]*BACKGROUND# gray90#' -e
> > 's#[A-Z_]*FOREGROUND# Black#' -e 's#[A-Z_]*HIGHLIGHT# White#' -e
> > 's#[A-Z_]*LOWLIGHT# B
27 matches
Mail list logo