Advanced Search

Yes, 7i76e.

Awesome, generous offer, thanks! From what I hear Mesa boards are very robust so I don't anticipate that anything will fail with that system. But, it is a mission critical machine for their production.

HH

My commercial machine re-homes the C-axis each time it's engaged.  Homing is to the 1:1 spindle encoder index.

My LCNC machine uses caxis.comp (Andy Pugh wrote it) and that also re-homes each time C-axis is engaged.

If you have any missed encoder pulses or a little noise, relying on an initial homing and then math to G10 the C-axis position would result in C-axis misalignment between C-axis engagements.  Prolly not much at first, but imagine a long run of parts if you've got a bar feeder.

I think taking the slight time hit homing would cost is worth it to avoid an accumulating error.

I assume you're talking about a 7i76e board and it's being replaced with a 7i76eu. Last I checked on 6/27 the 7i76eu was 2 months out so maybe it's getting close. If something happens to your 7i76e before the 7i76eu is available I do have one in reserve in case someone breaks down.

JT

I changed the verify button enable so after a successful flashing the verify button is disabled until a successful reload.

JT

PCW wrote:

I wonder if there is a file name error of some kind?
 

I downloaded the firmware file and copied the bin and pin file to the .local/lib/libmesact/7i96s and flashed, reloaded then verified so I suspect they skipped reloading.

 
 
 

JT

I built an Industrial CNC (my first system using LinuxCNC) system back during the pandemic using a 7i7e board. This system runs all day everyday and has proven totally reliable. Many thanks to this forum for making that project a success. The company that runs this system is wanting spare parts but Mesa will not respond to request about stock status. I also just purchased a newer 4X8 CNC with an HD100 controller that I am going to convert to LCNC and wanted to use the 7i7e since I have experience with it. With the new CNC I want the option to add a 4th axis and ATC.

Since the 7i7e seems to unavailable for the unforeseen future, are there any drop-in replacements for the existing machine I built and a Mesa board that can support a 4th axis with ATC for my new router?

Thanks!

I just looked at the documentation and the open loop estimation is a bit tricky

After a fair bit of research,  looks like it's easy enough to incorporate into the m106 code that will engage the c axis do some math to read the spindle position and do a g10 l20 to set the c axis  in reference to the spindle encoder.  I will have to work out how to subtract the whole number from the spindle position and just use what's after the decimal place to get a reference to 360degrees. - more reading....

OK smart serial if it detects no devices it reverts to gpio.

To work out the pins v gpio
mesaflash --device 7I95T --addr <ip address of card> --readhimd

Warning:
Just beware that you will gain 1 Input & 1 output due to the RS422 chip on board, ie they wont be the same as a normal GPIO pin. I'd wait for Pete from Mesa to chime in regrading voltage levels, current draw and whether this is a good idea.

I'm currently playing Discord. You can add me as a friend. My username is: onceloved.cn

Give me your contact information and I will install it for you remotely

hallo julian,

hier die werkzeugdatei...

Regarding a possible ethercat addition. I have made a custom ethercat board with lan9252 and that is definitely doable. Started a year ago and it's all here github.com/MetalMusings/MyOwnEtherCATDevice

 I'm using the Mesa 7i95t, and I just need a few simple output pins. So, I wanted to disable the smart serial port to gain those pins as GPIO.

In my hal file, I have...

loadrt [HM2](DRIVER) board_ip=[HM2](ADDRESS) config="num_encoders=6 num_stepgens=6 sserial_port_0=xxxxxxxx"

However, at start up I get errors...HAL: ERROR: pin_new(hm2_7i95.0.stepgen.00.counts) called with already-initialized memory
HAL: ERROR: pin_new(hm2_7i95.0.stepgen.00.velocity-fb) called with already-initialized memory

Why does unloading the sserial module cause stepgen errors?

Also, where do I find the .pin file mentioned by members of the forum - where the gpio pin numbering lives.

Note: if I change the last "x" to "0", like this ....
loadrt [HM2](DRIVER) board_ip=[HM2](ADDRESS) config="num_encoders=6 num_stepgens=6 sserial_port_0=xxxxxxx0"
Then the errors go away.

Thanks all.p, li { white-space: pre-wrap; }

  

Thank you very much