Advanced Search

Does anyone else have a tip as to what I'm doing wrong? I haven't found anything on the net until now. STLink with the instructions here from the thread didn't work, stlink with the hex file here from the thread flashed successfully, according to the display. NVEM v5 - Flashing not possible. I tried with DAP-link, J-Link, ST-Link v2 standard, firmware update and firmware from github. The result was the same every time, regardless of whether it was from the Raspberry Pi or with Windows 10. Either the board is fundamentally different, which I don't believe since it was recognized, or the programmers from AliExpress are all unusable.

the error messages are:
C STLink error (9): Get IDCODE error [__main__]
C Unexpected ACK value (0) returned by probe [__main__]
C Memory transfer fault (Unspecified error.) [__main__]
 

The last few days have been busy, but we added the fourth axis and build a new enclosure for the monitor. We repurposed the original base and just added an aluminium plate. The monitor enclosure is also from aluminium we had laying around.

Now the maho feels much more modern and with the physical buttons around the display we don´t have to manually switch the 19K1 relay (thanks to the hal or2).
We just started implementing the gear change as a python HAL component (that seemed faster, than trying to modify the C-Code from the MH400 gearbox) and got it to read the gears/speeds from the machine. But the machine is currently in a state of emergeny (stop) as our hydraulic pump is striking. Not quite sure if it is the pump or the hydraulic relais/pressure switch, but for now this is stopping us from further testing until it is solved. Has anyone else also experienced problems with their hydraulic pump (a HAWE FP12M-H1)?

 

I found someone to help me with that (YouTube channel talla83), thanks a lot!

Hallo.
Also da ist was gewaltig falsch. Ich vermute, dass du die Kalibrierung nicht bis zum Ende durchgeführt hast.

Mittendrin musst du um 180 Grad drehen und das Makro weiterführen (es stoppt nämlich über M0).

Die Werte in der Werkzeugtabelle müssten bei X und Y um 0 herum sein und Vorne und Hinten (blöde deutsche Übersetzung) bei irgendwas von etwas unter 6mm sein.

omg lol it was one of two things. a: loose connection at the driver (which one wire appeared so. b: the twisted pair wiring was the issue. im about to go back to the twisted pair to test. WHEW. im just glad i got some headway made. i was really losing my mind lol

Edit: not the twisted pair. it was just a loose wire. thank you so very much for helping me work thru this!

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