Advanced Search

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