Ich hätte auch die Möglichkeit die Servos Drives über Ethernet anzuschließen.

für die GMS brauchst du dann wahrscheinlich ein Heidenhain EXE TTL Konverter.

Die JASD AC Servos haben step/dir input, ja. Vielleicht übersehe ich was, aber eine 7i77 hätte einen Encodereingang pro Achse, damit sparst du dir die 7i85, wenn du die Servos eh mit step/dir anbinden möchtest, und die Encodereingänge von der 7i77 sind dann für die GMS.

Danke für die Antwort. 
Die Frässpindel ist ein 3kw 400V Motor diesen möchte ich mit einem Fu ansteuern. Verbindung Fu - Mesa 24V Rechts/Links und 0-10V.
Was den Anschluss vom Servo-drives betrifft. Habe ich momentan noch keine Ahnung. Es sind Jasd Ac Servo mit 230V. Am Cn 1 Port sind gefühlt 50 Pins. 
In der Beschreibung von der Mesa 7i76Eu steht. Man kann bis zu 5 Achsen Step/Dir-Schrittmotor- oder Servoantrieben anschliesen.
Die Heidenhain Messtäbe sind LS 803 die allerdings kein TTL Signal ausgeben. Ich dacht ich habe mal wo gelesen das mit der 7i85 das funktionieren sollte?
 

the new lathe conversational is incredible it is nothing like either in the stock ui's completely stand alone with built in safety checks tool fitment, built in threads and thread classes, motion simulation with stock, parameter operation builder.. its like full cam pretty much. it is an add on not open source.

Yes I will give it a try on the Weekend., but let ne finish my changes first. I might have found a way to use the jog increments from the gui for my encoders.
Are the new ones more Like the Mill Version and create gcode? I think this was the goal all along when I started my First attempts to integrate the existing lathe macros.

Hi everyone,

after a lot of back-and-forth—and some inexperience on my part—I’ve finally got the tool changer up and running. Many thanks for your help. Now just a few optimizations remain, but the bulk of the work is done. Next up are the 4th axis, the central lubrication system, and the spindle oil cooler.


youtube.com/shorts/3rU7JE1qDNo

anfanger, would you like to beta test the new conversational? it is far superior to the existing macros based version, very powerful, pretty much can run the lathe with no cam software .. let me know!

Thanks FabLabRacing,

I upgraded to last version (reinstalled all from new downloaded iso) and, after copying the old config directory, it's now working without that

Thanks, have a nice day,
Alberto.

I found it. I used the 7i97T_7i74d2.bin and this one doesn't have PWM in version 1, they are in 0. If I understand correctly, I can use 7i97T_7i74d.bin since they are functionally equal, and plus, this one does have PWM version 1

Those errors are due to host network latency issues and this must be solved before proceeding.

You do not need to change any firmware unless you need to support an added parallel
daughtercard or add a feature like Modbus support or step/dir homing to index.

To get a rough idea where you are network latency wise, run this command:

sudo chrt 99 ping -i .001 -q -c 60000 [card_ip_address]

Where [card_ip_address] is either 192.168.1.121 or 10.10.10.10 depending on 7I95T jumpering.

The command will run for 1 minute and then print timing statistics,   please post the result here.

Also, what is the host hardware?

wäre wichtig zu wissen wie die Ansteuerung der Achsen ist bzw. welche Signale du benötigst. Die 7i76 hat nur einen analogen Spindelausgang die anderen sind Step/Dir.

Zum anderen liefern die Heidenhain Glasmaßstäbe oft als Signal 1Vss (analoges Signal). für die Mesa brauchst du TTL oder RS485.

steplengths 5000, 7000, and 15000 all give joint following or finishing read errors.
Obviously, my parameters for speeds, acceleration, and the values in [joint 0] are still far from the right ballpark.

In addition to this, my ini in section [MESA] has an empty parameter called firmware. I copied these files in the directory as assigned by mesact. I am not sure what is required here but I want to emphasize the 7i95t manual strongly recommends not to use firmware for the 7i95 ( no T at the end) board.

Does someone have any advice on this ?

Cheers

geebee

Isn't that what I said?
following error in LinuxCNC is merely the sum of position commanded - position reported by the servo drive, a value without timestamps, always lagging behind. following error in the servo drive is more accurate as it is calculated on the drive itself without a lag of one or more servo cycles.

I am also in Germany but in no way an expert.
But yesterday I used Claude to write me something for my gui after gemini flailed.
And it worked damn good and relatively quick.
I also then let him check and comment my hal files with great results.
I was lazy and hacked around badly commented. now at least the hal of my lathe is clean and easy to understand I have also an overwie which signals are going across hal files.. I also used it to clean my really messy folders where all the failed attempts from the past and qnd copying over from other machines of mine messed everything up.
Tidy up some of my really messy python scripts. gave good suggestions renaming some of my buttons (oil, test, and test2 are not really easy to unerstand what they are doing ).

I will also do this with my mill.

So long story short for trouble shooting AI worked great for me.
I dumped my ini, hal, parameter and pin export and the ui files of my custom gui parts in there and then had a nice discussion.

You have the step length set to 10 ns

STEPLEN = 10

I would try 5 usec to start:

STEPLEN = 5000