On 07/18/2016 04:19 PM, EBo wrote: > On Jul 18 2016 3:09 PM, Moses McKnight wrote: >> On 07/18/2016 03:19 PM, John Kasunich wrote: >>> >>> >>> On Mon, Jul 18, 2016, at 03:28 PM, Chris Morley wrote: >>>> >>>> I think the whole mode thing needs to be looked at.Needing to >>>> switch to mdi to do manual things like touch off and tool changes is >>>> annoying when building a gui. >>>> Why do we need separate modes? That is left over from legacy NC >>>> machines. >>>> It is restrictive and error prone. >>>> I think as much as possible the gui builder should be able to >>>> decide what is available and what is not. >>> >>> I think the MACHINE builder needs to decide what is >>> available and what is not. >> >> I agree - which is why I think that linuxcnc should have an option >> where the >> machine is never in a joint jogging mode - and not leave that up to a >> GUI. > > then would we provide a different interface for jogging joints? Or are > you saying that there are no cases where you need or should jog joints > -- I'm thinking of setup/calibration.
Well, I was thinking it would be an option so you could either have it in that mode or not. Obviously some types of machines would need to jog joints, and even some gantries. If the option is used I suppose there may be a need for an interface to jog joints. The gantries we have set up do not need that even for setup, we home to 2 switches and move the switches to get the gantry square. >> <snip some good stuff> >> >>> I can't see how you can eliminate modes. Jogging joints >>> and jogging cartesean axes are two completely different >>> and incompatible things. Imagine a hexapod - every axis >>> jog will move all six motors. >> >> I think what Chris is talking about (he can correct me if I'm wrong) >> is mostly >> the manual vs auto vs mdi distinction. If I understand him correctly >> I think I >> would agree with him. Right now the GUI has to make sure that it is >> in manual >> mode before it can jog, or mdi mode before it can execute some code. >> It would >> seem that the GUI could simply check if linuxcnc is running a gcode >> program, and >> if not then allow jogging or run an mdi command. >> Linuxcnc would have checks as well so that it would just reject a >> command to jog >> or run mdi commands if it was running a program. >> The whole mode switching seems a bit clunky and unnecessary. > > I would add that it should give a warning "program is currently being > executed. If you want to terminate the program hit stop..." or > something like that. > > EBo -- > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity planning > reports.http://sdm.link/zohodev2dev > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
