Advanced Search

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



 

Ther is no 2.10, where can i find it and i download the 2.9 now, and same problem help please

2.10 or 2.9 will work but you need a recent build.
(newer than 1 month ago)


 

Seems you would need 2.10 for it to work, see
buildbot.linuxcnc.org
but first try this
buildbot.linuxcnc.org/dists/buster/maste...fd6a133f8b_amd64.deb
download and install with gdebi

I try man hm2_modbus, command not found as you see in attachment i have linuxcnc 2.9.4, i check in linuxcnc official site this is the last version, i dont know where is the problem 

I try man hm2_modbus
and man mesambccc
not exist in my linuxcnc i have the last version 2.9.4 i see in linuxcnc official site this is the last version, if there is newest version tell me please