>On Sat, Jan 16, 2016, at 12:23 PM, Niemand Sonst wrote:
>> I do not want to jog in Auto mode, but why not in MDI Mode?
>
>Internally, Auto mode and MDI mode are the same thing. Machine
>motion is controlled by the g-code interpreter. The only difference
>is where the g-code comes from, progra
I believe the hostmot2 ethernet drivers only work (or at least have only been
tested) with PREEMPT_RT.
Alec Ari
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3
On Jan 16 2016 3:20 PM, andy pugh wrote:
> On 16 January 2016 at 16:01, Lakshman Naresh Coimbatore Annadorai
> wrote:
>> Yes, it is the same project.
>>
>> You have mentioned that "The changes to do this are already included
>> in the
>> Machinekit project, I believe.". If this were true, it woul
On 16 January 2016 at 17:23, Niemand Sonst wrote:
> I do not want to jog in Auto mode, but why not in MDI Mode?
I think that the confusion here is that "MDI Mode" means different
things from the user persepctive than it does from the developer
perspective.
I think that the original questions was
"Do you really mean it" prompts are so very annoying I hate them.
On 1/16/2016 12:28 PM, Darren Conway wrote:
> Hello
>
> If this is a common problem and if it could have harmful effects (eg
> injury, damaged workpiece) then the HMI should provide some protection
> from user errors. Something equ
> Date: Sat, 16 Jan 2016 14:49:23 -0500
> From: ler...@se-ltd.com
> To: emc-developers@lists.sourceforge.net
> Subject: Re: [Emc-developers] Why is it not allowed to jog in MDI mode?
>
> John's original response contains two aspects:
>
> 1 -- A technical reason why that would not be consistent
On 16 January 2016 at 16:01, Lakshman Naresh Coimbatore Annadorai
wrote:
> Yes, it is the same project.
>
> You have mentioned that "The changes to do this are already included in the
> Machinekit project, I believe.". If this were true, it would be of great
> help.
In a previous email on the sam
> A -- The tool is dull and we need to move to a new position and replace the
> tool with a sharp one. In that case, we might want to also touch off the
> new tool to measure it's length and also change the tool length in a tool
> table.
B -- You are cutting a stringy material such as plastic and n
On 01/16/2016 09:15 AM, Marius Liebenberg wrote:
> I have to agree with that. It is most irritating to have to switch to
> manual if you want to jog and that for no apparent reason.
>
>
>
A jog dial (MPG) works in MDI. The keyboard keys <- ->
(and up and down arrows to select lines to recall) ar
John's original response contains two aspects:
1 -- A technical reason why that would not be consistent with the present
design
2 -- An argument (made by some) why that would be a bad idea.
To add to this:
1 --
The interpreter reads the gcode and outputs canonical instructions to a
queue that i
switch to manual mode to jog
On 1/16/2016 11:23 AM, Niemand Sonst wrote:
> I do not want to jog in Auto mode, but why not in MDI Mode?
>
> I do agree, that jogging during a machine movement is not a good idea.
> But in MDI MOde the machine is very often in the idle state and jogging
> should be al
I have to agree with Norbert here. On my mill I mostly do one-offs. I
have jog wheels for each axis, making it possible to operate the machine
very much like a manual with DRO. For simple stuff like facing off or
squaring up an edge I'll use the jog wheels. If for instance I want to
drill a hol
Hello
If this is a common problem and if it could have harmful effects (eg
injury, damaged workpiece) then the HMI should provide some protection
from user errors. Something equivalent to a mechanical missile type switch.
Adding the option to include a pop up "Do you really mean it" type
mess
Hallo Len,
if you hit the wrong command, that is your fault!
Please be carfull!
But that behavior would not be changed if you also allow jogging in MDI
mode and machine being idle.
I have attached to my pendant a "dead Man Switch" so if that button is
not pressed, no movement will ocure, but if
Am 16.01.2016 um 18:29 schrieb John Kasunich:
>
> On Sat, Jan 16, 2016, at 12:23 PM, Niemand Sonst wrote:
>> I do not want to jog in Auto mode, but why not in MDI Mode?
> Internally, Auto mode and MDI mode are the same thing. Machine
> motion is controlled by the g-code interpreter. The only diff
Dave, yes it make sense if you want to go to a defined position, but
what if you just want to jog around a fixture by hand. I like to use my
handwheel for that, but it will not work, because jogging is not allowed
in MDI Tab / Mode
Norbert
Am 16.01.2016 um 18:27 schrieb Dave Caroline:
> A jog
I think the issue is that selecting the MDI tab places it in auto mode.
I would agree that simply selecting that tab should not change modes,
but actually running an MDI command should. Its just as dangerous
allowing a double click from an MDI history to run that command. I have
double clicked
On Sat, Jan 16, 2016, at 12:23 PM, Niemand Sonst wrote:
> I do not want to jog in Auto mode, but why not in MDI Mode?
Internally, Auto mode and MDI mode are the same thing. Machine
motion is controlled by the g-code interpreter. The only difference
is where the g-code comes from, program or ke
A jog is not well defined, in MDI mode you are generally doing
something with some accuracy, therefore it makes sense then to jog
with gcode to exactly where you need.
Dave Caroline
--
Site24x7 APM Insight: Get Deep Visib
I do not want to jog in Auto mode, but why not in MDI Mode?
I do agree, that jogging during a machine movement is not a good idea.
But in MDI MOde the machine is very often in the idle state and jogging
should be allowed.
There could be a status check for machine is idle to allow jogging.
Norb
On Sat, Jan 16, 2016, at 10:15 AM, Marius Liebenberg wrote:
> I have to agree with that. It is most irritating to have to switch to
> manual if you want to jog and that for no apparent reason.
>
>
> >Hy to all,
> >
> >I am pretty sure it has been discused allredy, but I do not remember
> >the
Yes, it is the same project.
You have mentioned that "The changes to do this are already included in the
Machinekit project, I believe.". If this were true, it would be of great
help.
On Sat, Jan 16, 2016 at 5:52 AM, andy pugh wrote:
> On 15 January 2016 at 19:18, Lakshman Naresh Coimbatore Ann
I have to agree with that. It is most irritating to have to switch to
manual if you want to jog and that for no apparent reason.
>Hy to all,
>
>I am pretty sure it has been discused allredy, but I do not remember
>the
>reason, why jogging is not allowed in MDI mode.
>
>I do not see any reason,
Hallo,
If you use GladeVCP to load a file, the file will be loaded with
hal_filechooser.py.
This file does not load prior to the file the INI Code [RS274NGC]
RS274NGC_STARTUP_CODE
So my question is:
- Should not be loaded the startup code prior to any loaded file?
Imagine a user running file
Hy to all,
I am pretty sure it has been discused allredy, but I do not remember the
reason, why jogging is not allowed in MDI mode.
I do not see any reason, why to keep that limitation.
Norbert
--
Site24x7 APM Insight:
On 15 January 2016 at 19:18, Lakshman Naresh Coimbatore Annadorai
wrote:
> Dear All,
>
> I'm a graduate student at NC State University. I'm working on a research
> project to develop a feedback based compiler for CNC machines. This
> compiler is proposed to accept StepNC file and directly control
26 matches
Mail list logo
