Advanced Search

Not a lot of info to go on.
If your PC uses a realtek NIC I would search the forums for what to do. That would be a good starting point.

Next thing would be to ensure no "noisy" wires are crossing signal wires.

Next thing would be to ensure that the PSU that are powering the Mesa baord are giving a clean voltage. A good quality PSU, such as Meanwell or Weidmuller are good choices. Ensure the servo drivers are wired according to the manuals, don't skip the recommendations fro any filtering, not a cheap exercise, but well worth worth it.

Keep power wiring away from signal wiring. Don't expect a "rat's nest" to operate trouble free.

Don't wire every at once, wire one section at a time and test, trouble shoot and fix as you go. If something stops performing as it should it makes trouble shooting easier as you can start at the last addition you made.

Where ever possible terminate the ends of bare wires with "bootlace ferrules" makes inserting wiring into screw connectors easier and prevents start strands of wires floating in the breeze.

If you have implemented all these measures and have "noise" issues you will need to provide far more information. PCW may chime in and ask for you to do some "ping tests" and such, as this is his domain I shall leave it to him to guide you through that part.

Hello everyone, 
I am using mesa board 7I76E to control 5 axis cnc with servo motors 
I installed the linuxcnc on a laptop when i run linuxcnc with the mesa board on the laptop everything works well i got some wired interference like loosing Ethernet communication with the board or the mouse pad will be crashed all the time but i was ignore them because they didn't really influence on my project.
After that i installed the same version of linuxcnc on a desktop computer in fact i used the same ssd so it was the same software, the same configuration at this moment the noise issue became more than usually now i lost the communication every 5 min around ana that's a big problem. Do you have an idea what is the exact issues happened to me , how could i decrease those noise 
Thanks in advance 

Hi all!

first of all, great work! I managed to get everything running just by reading all the great posts here! All the nice HowTo´s and so on... 

But now i got stuck...

what do i have?

i´m running a RPi 5 with LinuxCNC (latest Preempt Version) 
a Mesa 7i76EU (everything working)
a Pendant WHB04-6 (everything working)
and some Beckhoff EtherCat modules (everything working)
and last i got my self an EtherCat Module for the Omron MX2 (partial working)

I can´t figure out how to drive the Omron MX2, there is some mismatch in the type of the controlword
my ethercat xml has only the Modulelist, no special entries like syncmaster and so on... 

the Device shows up in the HalShow under lcec, all "Pins" are viseble, ethercat slaves shows the device... so i think its just a small config problem in the xml

maybe someone out here who has it running...

Thanks for looking / helping...

Cheers Einar 

 

Hello all... I am looking at retrofitting a Prototrak DPMV5 mill, its supposed to have electronic handwheels as well as full CNC mode.
I am making new electronic handwheels- instead of using the 100ppr units you can get cheap, i want to use a 1024ppr encoder and custom made wheels. Bringing me to the main question: Can i use the 7i95T Mesa boards 4,5,6th axis encoder inputs as MPGs? Arguably with real good encoder counts? Or am i limited to using the 8 inputs as MPGs for the normal 100ppr units?
The machine I have is electrically stripped, so imagination is the limitation (okay maybe wallet too).

ps: I have retrofit a VMC and converted a manual lathe to CNC using 360ppr encoders on the handwheels to make a similar manual/cnc mode. Sometimes it misses counts when i spin fast using a 7i76e MPG inputs.

Thanks!
 

Thanks for checking things over PCW!

I can't setp the value since it's linked to a signal, but when gcode runs M67 E0 Q0, GPIO 017 does go false.

'setp hm2_7i76e.0.pwmgen.00.scale 100' has been added, this may yield better results. Since I didn't set the scale, all values (1-100) were sending full power. This tip right here may be the biggest sanity check, thanks PCW!

The connections look OK

If you set the PWM value to 0, does GPI0 017 go false?

I don't see that the PWM scale was set so anything >= 1 will be full scale
(default PWM scaling is 1.00 = full scale)

If the PWM values are in percent, you probably wantsetp hm2_7i76e.0.pwmgen.00.scale 100

in the hal file



 

I've got to get better at asking the right questions... Using the old config:

signal 'sj'
motion.analog-out-00, and
hm2_7i76e.0.pwmgen.00.value

All these values update as M67 changes the output.

hm2_7i76e.0.gpio.017.in toggles to True when the gcode starts running.

Does everything seem mapped right for the PWM to reach pin 1 on a 5 axis breakout board? Should that be on hm2_7i76e.0.gpio.017.in? Maybe the code is fine, and I should be chasing down a hardware issue?

Agreed, this has had me stall posting for a few weeks...Pretty sure I was using 2.7.14 when setting up the 7i76e, and 2.8.2 most recently.I've not been great with version control, while moving across computers and machines. These might be the last working files, but unsure...  Laser signal as 'sj' in line 39

Long story short, I need help getting laser control working again.

Setup was functional with the main diode laser (which failed one day), then edited to use a cheaper diode laser.  I tried switching everything back over after repairing the main laser, and it's been a downward spiral.

I'm now pot committed to starting from scratch.  Setup is a 7i76e, with a 5 axis BoB on expansion port P1.  OS has been upgraded to 2.9.4, and 7i76e_7i76x1_5abobpD.bit has been flashed to the board.   

The attached config is just a basic pncConf output.  Any guidance for implementing PWM would be greatly appreciated.
 

Good evening gentleman,
I am almost done with my new setup (printnc "pro", mesa 7i76eu, probe basic, jianken ATC) and everything seems to be working now, except the tool length measurement.
When I start a measurement with G38.2.... and then press the toolsetter with a finger (just to test it), the system errors out with "probe tripped during non-probe movement".
So it recognizes that the toolsetter is triggered, but for some reason it thinks its the 3d probe...  

This is how my probe and tls signals are linked:

# --- PROBE-IN ---
net probe-in     <=  hm2_7i76e.0.7i76.0.0.input-08
# --- TLS-Normal-IN ---
net tls-in       <=  hm2_7i76e.0.7i76.0.0.input-09-not

addf or.probeortls servo-thread
net probe-in or.probeortls.in0
net tls-in or.probeortls.in1
net probe-tool or.probeortls.out
net probe-tool motion.probe-input

What am I doing wrong ?

Here is my full config...
github.com/SebastianMusser/LinuxCNC/tree/main

regards
Sebastian

Another remark.. not sure if that me misunderstanding anything or if its another bug, but witih MesaCT I generated a config to set my outputs 0-7 to sinking and 8-15 to sourcing.
This were the generated lines:
setp hm2_7i76e.0.7i76.0.0.output_sink 0xff00
setp hm2_7i76e.0.7i76.0.0.output_source 0xff

isnt this "the wrong order"? imho this sets 0-7 to source and 8-15 to sink.. right?

That's a bug with the 7i76eu I/O section. I'll fix that.

JT

good afternoon!
today I played around with MesaCT for the first time, and I saw that the generated configuration (for my 7i76eu) has a different naming / nomenclature for my outputs than pncconf...

pncconf outputs lines like this:
net dust-removal-out motion.digital-out-03 => hm2_7i76e.0.7i76.0.0.output-03

while mesact creates these lines:
net flood-output iocontrol.0.coolant-flood => hm2_7i76e.0.gpio.031.out

where does this "gpio" come from? is this redundant or did I do something wrong in the tool?

regards!

Typically, unless you need linear encoder feedback, you can use servo/closed loop drives that
just have local feedback, (no feedback to LinuxCNC) so you don't need encoder inputs, other than
one for the spindle if you want to do spindle synchronized moves.

For a simple system, I would consider a 7I96S or 7I76EU (the main difference is the the 7I76EU has
more digital I/0.) If you are sure you want to add encoder feedback a 7I95T would make more sense,
though you can add an encoder daughtercard to a 7I96S or 7I76EU (7I85/7I89 = 4/8 added encoders)

You cannot use the standard release as they are only updated about once a year.
For a binary update, you need to use the image built by the LinuxCNC buildbot:

buildbot.linuxcnc.org/

(The page is a bit old as 2.10 is the current LinuxCNC master version and 2.9
is the current release version)

 The other option is to build from source:

www.linuxcnc.org/docs/devel/html/code/building-linuxcnc.html