Advanced Search

rodw wrote:

1. Somewhere in your ini settings kinstype=both lets you jog before homing unless you have 2 motors on an axis
2. Refer to my Ethercat install sticky for the rules to start the ethercat service on startup
3. No idea
4. It may have changed but probe basic requires a 1080p monitor so I could never used it. QT dragon is the same. I had to upgrade to a 1080p monitor.

I'm at a loss to understand what any machine needs moving before homing. Are your home switches set up so they stay triggered to end of travel?

Thanks

Progress so far:

1: that interesting, its not in my ini right now. ill see if it changes anything. not that axis and qtdragon both work as expected.
2: i reinstalled the whole system, were back on 2.9.8 and everything is so far fine.
3: this is actually the drives reporting zero for one frame when resetting. i remove my filter which was filtering that bad value. it is curious, and i think only the omrons do it. its not important, but perhaps there is a setting or pdo that manages this. Or i can just re-enable the filter but only to trigger on controlword changes. (this is the same basic "bug" with the drives that cause the random joint and home errors).
4: in fact probebasic requires 2077x1080 for reason unknown, i set my res to that and its fine. Lcvette has some thoughts, but after running through them nothing has changed so far. My undestanding is after their server migration something is borked. Fonts are also wrong, too larger, which i assume is related. We will revisit it another day, it is fine for now.

So really we are just needing to fix the jog. I will try what you just said and report back.
Thanks
 

Hey,I retrofitted my CNC mill a while back and since then had a more or less ugly touchscreen built into the original housing.Since the touchscreen now stopped working as well, I decided it was time to make something more modern.It features a 21" touchscreen monitor, a full keyboard, some rotary encoders for overrides and 19 custom made buttons (for on/off, homing, coolant etc.) that can be illuminated separately with a custom hal component.The angle of the keyboard can be adjusted and the back has connectors for HDMI, USB, Power and the emergency stop signals (I don't wanna send the via USB for safety reasons).The frame is made from aluminium, the front and back is matte acrylic. It can be mounted using a standard vesa mount.I already did a v1 of it when I retrofitted my lathe, so I could make some improvements.Let me know what you think   

whats the current situation?

Thanks I did it with help of AI ... It was worse then Preemt-rt in default non custom stuff ... I left this idea when I saw how much custom thing I need to code alone to run something and it saves be 3us ...

great idea but much stuff around it

I have a lathe with a 9-speed gearbox that is manually selected. The motor is always running at its maximum speed of 1360 RPM, and the speed is manually changed using the gears. I'm using your gearchange component, which supports up to 32 speeds. I've already implemented the logic to select each speed. In each range, I'll control the speed with a VFD between the lowest value of the previous speed and the maximum, according to the original lathe's speed chart. For example, the first speed is 36 RPM, the second is 90 RPM, and the third is 155 RPM. Then, in the first speed, the spindle would rotate between 0 and 36 RPM, and the motor would rotate between 0 and 1360 RPM. In the second speed, between 36 RPM and 90 RPM, the motor would rotate in that gear between the speed that the gear provides, resulting in 36 RPM and 90 RPM at the spindle. This pattern is repeated for the other speeds. My question regarding this component is how to adjust the scale on each device; I don't know if it's always done relative to the first one or relative to the previous one.

Thank you for the help
moved the post to there

Over the last year I have been building a gantry plasma table with leadshine el8 servos and Beckhoff modules for I/O, I struggle a lot with software but with help from rodw over on the ethercat forum and some guides I managed to get ethercat working and a basic QTplasmaC config.
but im still having some troubles:

I managed to get these things working:
-QtPlasmaC interface
-motion on all axis when jogging the machine
-external E-stop
-torch break detection switch
-machine enable output turning on a light

what isnt working:
- cant get a torch on output signal when I do a torch pulse
- the ohmic probe enable doesn't output any signal
-when I hit cycle start the G code pauses without moving the machine

I have a EK1100 coupler, an EL1008 digital input, an EL2008 digital output and EL3102 analog input to read the divided arc voltage.

what are the best ways to debug this situation and what should I be looking for?
all config files in a zip file below

previous post:
forum.linuxcnc.org/ethercat/59024-integr...khoff-modules#348066

Thank you all for your help

The spindle-at-speed signal was the issue. The command is correct for a full circle cut. I did add P1 to insure that a full circle is cut though the documentation indicates that P1 is implied if not provided.

Thanks for you help.

Spindle-at-speed was the issue. I had added a near function to the spindle-at-speed signal in an attempt to get away from the extra dwell after M3. However when I examined the near function input signals the feedback rate was 0 causing spindle-at-speed to never to active.

I removed all of my near function code and put spindle control back to the original configuration and the spindle-at-speed now goes active, but at a significant delta from the commanded speed based on the VFD display and the sound of the spindle. Consequently, I'm back to the additional dwell after M3. Not a real issue since this is a hobby machine and I'm not in any hurry to make cuts.

Thanks for the insight and support.

Kind regards,

You can use the MUX16 component and assign an overall feed value to each of the 16 combinations. It's very simple: you just need to use 4 inputs on your mesa board for each rotary switch. Let me know if you need further assistance.

I don't know what is going on here.
Is it possible that you have modified the G-code to support angled facing?.

github.com/andypugh/LatheMacros/blob/Py3_GTK3/facing.ngc

Says that angled facing isn't supported, and there is no indication of the #6 input being used in the standard G-code.

Hi, would you be willed to share the comp you linked above again? It’s 404 on codeberg

Many thanks

PCW = owner of Mesa, Peter Wallace and a very active forum member

Many thanks for every answer. Who is PCW?
Hans

This is actually pretty easy, the 7i76e comes with 2 mpg inputs and you can have them on the 7i96 as well but you have to give up a couple of pins or a Stepgen.I can't quite remember what. If you ask PCW nicely, I'm sure he will sort out the correct solution.

Once you have that sorted, there is a good example of a MPG using parallel port pins in the docs. linuxcnc.org/docs/stable/html/examples/mpg.html

But in your case, you can ditch the axis select knob because you will use a dedicated MPG for each axis. Just implement the scale select knob... I have not thought about it but you may be able to use the one scale select for both MPGs. Using digital knobs lets you minimize the number of pins you need for the scale hence the mux4 components.