Advanced Search

Yes it is missing.
Maybe you already have fixed it by now. It's not a standard component so you need to "halcompile --compile cia402_homecomp.comp" to put the .so file in you config directory.
It's daring to try to get the servo working using a custom setup, I wouldn't do it. I would start with the simplest config possible from dbraun1981 and when that works I would build on with other functions.
But i understand this is part of a complete working setup, so you need to find the cia402_homecomp, compile it and hope for the best.

Thank you kindly PCW for your reply.

This might be a very stupid question, but how do I implement the link you provided into MesaCT?

Do Just download the last hostmot2.c and mesaflash.c files and swap them into the mesa flash-master folder?

Excuse my ignorance!

j

If you are using a standard 100 PPR MPG, it will count up by 4 every detent
with a standard quadrature counter. It looks like you are using the software
encoder, if so , try setting encoder.0.x4-mode false.

First Question.

For a 1mm jog, I originally set my MUX40.in1 to 1.0. This was resulting in an exact 4mm jog each count. To fix this I need to set the scale below to 0.25. While I can do this and get the result I want, it bothers me that I have to use a ratio instead of direct number and will be harder to decode at latter dates. It seem arbritary that each count would be 4mm exact.

setp mux4.0.in1 1 (jogs 4 mm per count)

setp mux4.0.in1 0.25 (Jogs 1 mm per count)

net encoder-counts  <= encoder.0.counts
net encoder-counts => axis.x.jog-counts

Question is, where is the actual jog value recorded in LinuxCNC.? I cold find nothing in the .ini or .hal files that seems to indicated it would jog exactly 4mm each jog count.



Second question,

Per the below, I am currently using mux4 to determine the jog scale. But my MPG switch does is not using an encoder switch but instead has 3 simple outputs of which I placed into input 26 (1x), 27(10x), 28(100x)

I got everything to work but can not find any details in .hal how to use something other than mux4 logic to place the correct scale into the axis jog. This seems like it should be simple. More or less just want if one of those pins are true, the correct scale is selected. Below is partial code referancing the scale portion. Note. Only using pins 26 and 27 at the moment due to the mux4 requirements. Other than this, everything is working fine.

# This sets the scale that will be used based on the input to the mux4
setp mux4.0.in0 0.025
setp mux4.0.in1 0.25
setp mux4.0.in2 2.5

# The inputs to the mux4 component
net scale1 mux4.0.sel0 <= hm2_7i76e.0.7i76.0.0.input-26
net scale2 mux4.0.sel1 <= hm2_7i76e.0.7i76.0.0.input-27

# The output from the mux4 is sent to each axis jog scale
net mpg-scale <= mux4.0.out
net mpg-scale => axis.x.jog-scale

---

Basically want:

if Pin 26 true then axis.x.jog-scale == 0.025
if pin 27 true then axis.x.jog-scale == 0.25
if pin 28 true then axis.x.jog-scale == 2.5

Note that as the schematic says, there's an even/odd swap
because the schematic is for the flat cable, (which plugs on to
the reverse side of the FT4232H),  _not_ the FT4232H

github.com/LinuxCNC/mesaflash/commits/master/

Currently 3.5.13

After further testing and focusing on the Z axis, it is related to the limit switch. If I Z+ to the limit, then re-zero the non-zero value increase (G54). Each time I bump up to the limit switch, the value increases. Strangely, the actual (G53) remains the same (within a few tenths)

Also, if I "power off", meaning use the power button of the UI, and then power the system again, I can then correctly zero the Z. Meaning if I then press the zero Z axis, it will then set to 0.

Hey all, have accidentally corrupted the firmware with an old mesaflash on a Tormach controller and am trying to bring it back.

I've read a few threads here on the forums and gathered what I could, but I'm still having issues.
I've got the current efinity software (2025) and a FT2232H Mini Module. I've attempted to wire some of the JTAG up according to the specifications in the datasheet for JTAG, but was unsuccessful with that, and also via the wiring diagram here: www.forum.linuxcnc.org/27-driver-boards/...-the-fallback#318881
However, I can't make sense of the diagram.. It seems to mention that pins 1, 3, and 5 are ground, but according to the FT4232H and FT2232H datasheets, those pins are 3.3V VCC. I've tried a couple combinations of wiring but haven't been able to find one that works.

Is there any mapping between the actual bus names (AD1, BD2, etc) and the JTAG pins on the board? I don't mind doing a writeup on the procedure if I can get it working, but I'm just out of ideas here.

Thanks for anyone who can help.

Did this end up selling? I'm asking because I found it on marketplace in Canada, I did a search and found it here after I replied to the ad, seemed fishy. Thanks

www.facebook.com/marketplace/item/172213...anner&referralCode=2

Hi!

I know this is an old thread, but I too am having issues getting Mesact to communicate with my 7i97. It will ping okay.

I have mesaflash 3.4.9 installed and am aware that I may need a higher version, however I can't seem to find it. Does anyone have any tips on finding the latest Mesaflash? I can only find 3.4.9 on the GitHub link. Perhaps I'm missing something here!

Any help would be appreciated.

J

For a pure Unbuntu install, you will have to install your flavour of Ubuntu then install from source, unless you can get the debian packages to work.
If your Ubuntu install uses wayland rather than X11 those guis of Linuxcnc that depend on X11 libs may require a "compatibility" layer, that I've found is somewhat slower than native X11.

Personally I would recommend a the Debian ISO and stick with something that is straight forward and simple to install.

Actually there has been some talk about Canonical using a third graphics subsystem in the furture....and replacing all the basic Linux\Unix utils with Rust equivalents. What's next the return of Unity ?

Thank you so much! I will reply back with my experience. Several days, maybe...

github.com/ventoy/Ventoy/releases

Thank you so much! Where do I get the Ventoy download?

In this case the encoder resolution is 10 counts/mm (0.1mm) so I use a deadband = 0.05, This eliminated the oscillations that occurred simply by enabling LCNC.