Advanced Search

You have a lot of synchronization errors.
What kind of cable are you using?
What is your topology?
Do you have EMC problems?

[70592.094690] EtherCAT ERROR 0-0: AL status message 0x001A: “Synchronization error”.

Was it this?
forum.linuxcnc.org/12-milling/33035-retr...-maho-mh400e?start=0

This worked pretty good for me

There i still a but... if you have a look at the attached photo why do i have no mm after my coordinates or depth? Ist the axis_mm from the sim

Hi,

@Rotary: I tried the minimal HAL you provided. I had to change the number of encoders from 5 to 4, but then it starts up fine as well. However, it does not change the Smart Serial problem—only channel 4 detects any cards.

The one 7i84 that was detected but gave undervoltage errors now works flawlessly. I did not change anything, so I am not sure why it did not work two days ago, but I will take the small win.

I also made some images of the wiring. I am not sure how clear they are. All the yellow cables are 24V, the red ones are 5V, and the black ones are GND.

I suspect interference, so pictures of the wiring from Mesa to drives might help.
-
Why are there two posts with the same hardware and same issues by two members?
Are you the same team?
If yes, continue here.
Thank you.

I suspect interference, so pictures of the wiring from Mesa to drives might help.

Sounds like a hardware or wiring issue with the drives or 7I96S step/dir outputs, as there is no motion
and no obvious errors.

Is there a common enable for the drives?

Can you increase the following error limits and try jogging in each direction to see if the DIR outputs
are  at valid voltage levels and change direction on reversals?



 

Short Update.
Fortunately, I had a second MESA 7I96s here. I flashed it to the right firmware and installed it.
After that, it seems that everything works fine now.

Will replug the old one just to check if there was no connection-problem.
I will give a feedback how it will go.

 

Hi all,

We are working on a retrofit of an older Fryer lathe. We are using a Mesa 7i95 board and are trying to connect our SGDH-10AE Yaskawa drivers to the board in position control mode. We have managed to make the axes move in what seems like position control, but when changing the jog speed in AXIS, it also changes where the motion stops. I believe that I have made a mistake, or many, in trying to set up our HAL code. We generated the HAL code from Pnfconf and then made adjustments to try to change the Stepgen to position control mode. I was hoping that we could get some help in looking at our Hal and Ini files to see where we may have gone wrong. Or if someone has successfully implemented it, we could look at their files to see if we can figure it out. 

Thanks!

Jblanscett

I tried to copy the whole starting-log out of the Terminal, but i can`t becouse i got the error-message "there are too many links in this post...." 

So i attached an file.
 

Also here the readhmid from the MESA 7i96s
 

Hi andy,

there is no movement at all.
At the wizard i testet every axle (X, Y, Z) and not just one moved.
At the HAL-Scope i could see the feedrates on every axle, but no movement. 

Every tim I try to do the reference, i get this error
In the Terminal is the following:

Johnbl,

I am working on a lathe with SGDH-10AE drives and a Mesa 7i95 using step and direction with position control on the drive. Would you be willing to supply your hal, ini files from Linuxcnc and your parameter files from your drive?

We have some control over the drives and have the step and direction wired up as suggested here. Our linuxcnc is not working as we would like and the drive isn't producing consistent results. I think the pulses are coming out of the 7i95 too quickly. we do have some level of speed control through jog limit, but not what we would like and for some reason we don't get consistent distances depending on speed. We are having to tune the drive for position control which I thought would not be required initially. We aren't using feedback to the mesa, only internal to the drive.

Thanks,

Howard

I think that for Yaskawa, the safest approach is to use Yaskawa’s own tool (SigmaWin+), since it knows the hardware and the drive’s constraints, and it’s also the approach their support can reproduce and help with if something goes wrong.

Ja EMV ist ein großes Thema und man sucht im dunkeln was da stört kann man messen aber nur die Industrie hat die Möglichkeit Datenkabel können in frage kommen hatte ich schon mit ein Monitor-Kabel.Da du ein Metalsteg eingebaut hast ist in dem Bereich was nicht ganz sauber.
Ich tippe auf die Grünen Datenkabel oder ist T3 ein Netgerät ? Vielleicht das.
Auch können die China Komponenten schuld sein hatte ich schon mit
ein Handylagerät das hat total das Fungerät gestört.
Was mir auch aufgefallen ist dein Netzfilter der ist ja ok aber es könnte
mit RCD Probleme geben muss nicht . Das ist heute auch ein großes Thema weil jede LED-Schaltung Ableitstöme produziert und irgend wann sind 30mA erreicht und dann macht es klick.

Gruß
Juergen

Do you mean 2.4.8 or 2.8.4 ?
(2.4.8 was released around 15 years ago)