Advanced Search

Video of the screen and torch? So twice.

I do have the same problem, I see the ohmic probe is activated then when probe start it "find the plate" and try to go back however torch is in the up limit, then you have a error, I set the threshold to 18V and worked in probing but fail again during real cuts, mine is a water table.
please let us know if find the solution.

Thank you, that makes it more clear. I will measure all the cabling and ground connections.

- You need to mark the files 'M128' and 'M129' as executable (rightclick-> Properties -> Permissions).

I don't know about changing the key binding at run time but I would strongly advise against using keybord bindings to jog the actual machine. Much better to use hardware panel buttons connected to realtime hardware inputs.

Not sure what you mean by 'executing' a custom component. A 'custom component' refers to something that runs in HAL and as such runs periodically.
linuxcnc.org/docs/html/hal/comp.html

Do you maybe mean a 'remap' to create/redefine a g- or m-code?
linuxcnc.org/docs/html/hal/comp.html

I wouldn’t mind rewiring everything — my setup is quite simple, and the CNC machine is fairly small. For me, building and tweaking the CNC is part of the fun of the hobby.

I’ve read that many of you use various Mesa cards. I was hoping the 7i76EU alone would be a good starting point to learn how to work with Mesa hardware. Do you know if that’s the case? I saw some brutal shipment costs (like 200 dollar plus, so i will have to search for an European supplier, i'm in the Netherlands)

If the 7i76EU would allow me to completely move away from the parallel port, that would be a big plus — especially since I’m currently limited by base-thread latency.

[EDIT]

I see a seller with reasonable shipping costs, not sure if its a trusted compane EUSurplus?I think i am planning to switch to a Mesa board and wanted to check if the 7i76EU is the right fit for my setup. This is what I’m working with:

• 3x DM542A stepper drivers (they use step/dir signals)
• 3x LJ12A3-4-Z/BY inductive proximity sensors (used for homing)
• 1x Huanyang VFD (spindle, controllable via 0–10V or RS-485 Modbus (I think because i now use it over USB)

From what I’ve researched, the Mesa 7i76EU seems like the best option. Here’s why:

• It supports up to 5 stepper/servo axes via step/dir signals (perfect for my DM542A drivers)
• It has 32 opto-isolated inputs which should work well with the 24V NPN homing sensors
• It has 16 outputs, which are configurable (sourcing/sinking)
• It includes an analog spindle output (0–10V) for VFD speed control
• It supports RS-485 communication if I decide to use Modbus for the Huanyang VFD
• It isolates field I/O power from logic power, which helps protect the system

Important to note:

• The sensors might need a pull-down resistor to give clean logic signals when connected to 24V. I already solderd a pc to convert the 30V signal back to a 5V system with opto's
• I will need to supply 24V field power to the board 
• I understand the 7i76EU requires a second Ethernet interface on my PC (either a second NIC or a USB↔Ethernet adapter)
• I still need a PREEMPT-RT kernel, but I won't have to worry about tight base-thread latency anymore

Does this sound correct to those of you with experience using this board?Thanks in advance!

 

Unfortunately it happens 100% of every time.

It really feels like a bad setting somewhere, but AFAIK I haven't changed anything relevant since the last time I used it a few months ago. I've been cutting thick material for a while so I just was just using float switch probing.

What I can't get my head around is that there is no indication that the ohmic sense pin is ever on. This makes me think there is an unrelated setting keeping it from probing. I tried adjusting the probe height, but that didn't change anything.

Float switch probing continues to work fine.

langdons, sometimes it is better not to answer. It should be obvious from the post that this is an ethercat machine.

I don't see anything obvious wrong in the setup.
8000 is a lot, 8000 steps or ticks or whatever per mm but that is probably right since it moves right.
What you can do to debug this is to use "halshow" and look at all pins in the chain from joint.0.motor-pos-cmd to the cia402 pin, to the driver pin, and the return from the driver pin, to the cia402 pins, to joint.0.motor-pos-fb pin.

You would need a stiffer pullup so you get more than 12V at the 7I76E input

I would suggest 2.2K 1/2W

You could also use two separate inputs and an OR or MUX component
(the MUX component has the advantage of ignoring the other input
when not in use, but requires a signal to select which input shouls be active)

Thanks for the input. The softlimit not working with joint limits just with axis limits is sad :(I tried to include to millturn limit changer but LCNC reports: Unknown M code used. I assume somethings not right in the .ini ? Also is it possible to change the key binding dependent on TWP is active or not?

Also: How can a custom component can be executed from a custom M-Code? Background is, that a custom g code or m code is needed to rotate and lock the tool spindle. I feel comfortable creating my own component, but how to execute it from within m code i don't know.

Thank you and kind regards,
Jochen
 

Hello again!
My next problem to get my machine running (it's running but not as precise as I want it) has to do with two switches.
My tool length sensor is a quite normal mechanical switch, that is NC and put +24V into input-08-not. That's working perfectly.
If I put my 3d Sensor (NPN-NO) into the line as the picture shows, nothing works. The 10k resistor (R1) before the Tool length switch puts the voltage down to 12.xVolts, the Input-08-not is set to "probing" permanently.
The 3D Sensor does nothing at all, not even the LEDs are active (the output is an open collector, I presume). What about diodes?
 

So, my next thought is to disconnect the two sensors from each other and use another Input of my MEsa 7i76e just for the 3D Sensor. This input should not be inverted for correct funktion. How can I do this with or without using an OR2 funktion?
My lines for the tool length are as follows

#---PROBE-IN ---
net probe-in     <=  hm2_7i76e.0.7i76.0.0.input-08-not    
net probe-in     =>  motion.probe-input

AFAIK, I cannot just net another input to motion.probe-input. But how could a OR2 look like?

Thanks for your help, again!
Hanno
 

If Step/Dir resistor networks or driver chips are being damaged
it means a voltage considerably outside the 0 to 5V range is being
applied to the Step/Dir pins.

First thing I would check is drive grounding and Step/Dir wiring
Routing step/dir lines parallel to servo motor wiring might also
cause enough EMI to damage the drivers.

An intermittent short to 24V wiring is another possibility.

I did push some work to fix an error I found.

A while ago, my MESA 7i76E broke; one channel just stopped working. I wrote about that here . I then found someone who repaired the card, after which the machine ran fine for half a year. He said he "replaced the resistor network" of the channel.

Today, the exact same issue appeared again. Joint 2 stopped working and after a restart it worked for a minute and went away again. This is exactly the behavior I saw last time.

This time though I was better prepared and had a spare 7i76E ready to replace the other one. After replacing it the machine ran fine - but after an hour the new card displays the same behavior, too! Clearly something is going on that breaks this channel... sometimes.

What would you do to diagnose this? Replace the JMC servo (with the built in controller) and hope for the best?

I remembered there is a wifi PCIe card (different brand) in my desktop which won't be missed. I put it in the CNC computer and now it all works.
I also did a latency test. This is with 5 glxgears plus YouTube running a psychedelic video, plus streaming from my RPi camera. Pretty much the same as I had back in March.

In addition to my machine config described in the first post, my graphics card is a Radeon Firepro V5800. 

Thanks for the comments,
Steve

Can you give more detail of the load problem?
I'm guessing you want it to autoload at startup?

set_style is old code from a slightly different version.
IIRC if you use it then you can't override the style with the style editor.

Here are some of the things you can change from the style sheet editor:

I think it needs a way to change styles per macro as it's hard to get sizes to work with different macros.
If there is interest I can develop it more.