The stepper motor withstands temperatures of 120 degrees Celsius.
This is, of course, the maximum parameter and during normal operation it should be cooler.
On the other hand, if the motor is cold, it means that the current is too low, resulting in less shaft torque.
Without a thermometer, this can be assessed by stating that the engine should be hot, but should be able to be touched by hand.

Sörry for eventually annoying anyone. Some reading I certainly did, it is just a lot of stuff. I have used several motors both of the same and different types and two different drivers. I can limit current at the tb6600 and certainly did. The cs-d508 does not provide any switch to do so. Its datasheet mentions overvoltage and overcurrent protection. Apparently the current nevertheless is too high, not too low. The motors heat up quickly when not moving. I lost a second one even though I have become more careful after the first one burned. I certainly do know how to wire a 2 phase stepper. Mistakes might happen, but I will not repeat them every time I reconnect the stuff. I have been working with steppers and arduino but not yet on a professional basis.

So at the moment, I suggest its more likely a latency issue. It is gonna take me a while to go through the stuff pcw has told me. After that, I will let you know what I did and what were the results.

Cheers

The stepper motor pins can be checked without any tools.
Disconnect the motor from the controller.
Jump any two pins together.
Turn the motor shaft by hand.
If you feel a clear resistance, the pins belong to the same coil.
If the shaft rotates freely, the pins belong to other coils.
Shaft vibration instead of rotation is a typical symptom of confused wiring.
However, if the engine stands still and squeaks, it is a matter of settings, either the controller or the program.

The ping times show that the host is set to a 10.10.10.11 IP address and the 7I95T is set to 10.10.10.10

With and Intel MAC you should disable IRQ coalescing:

man hm2_eth

For testing, you can temporarily disable IRQ coalescing with this command:

sudo ethtool -C eno1 rx-usecs 0

( replace en01 with your Ethernet device name if different )

For testing general host latency,  when a base thread is not used (like with Mesa cards), 
you should run the latency test with the base thread disabled:

latency-test 1ms

or

latency-histogram --nobase -sbinsize 500

Also you should go through all the standard latency reducing methods here including the isolcpus grub setting:

linuxcnc.org/docs/html/install/latency-test.html


Just to get things going you should make sure the step time is 5000
and worst case you may need to increase the servo tread period to say 2 ms
(2000000 ns)




 

 Please note that according to the advice from tommylight I set the ip adress of the mesacard to 10.10.10.11 instead of 10.10.10.10.In opposition to the ones above the ping results are now with mesacard on the Intel adapter, not the Realtek.

--- 10.10.10.11 ping statistics ---
60000 packets transmitted, 60000 received, 0% packet loss, time 59999ms
rtt min/avg/max/mdev = 0.004/0.005/0.103/0.001 ms
geebee@debian:~$ sudo chrt 99 ping -i .001 -q -c 60000 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.

--- 10.10.10.10 ping statistics ---
60000 packets transmitted, 60000 received, 0% packet loss, time 59999ms
rtt min/avg/max/mdev = 0.139/0.253/0.368/0.010 ms
geebee@debian:~$ 


 

You are pinging the host PC, not the 7I95T
try:

sudo chrt 99 ping -i .001 -q -c 60000 10.10.10.10

( It will run for 1 minute then print timing statistics )

 

I changed the network adapters: Mesacard is now Intel 82579V, internet Realtek RTL8111/8168/8411
ping times now are 0.019 - 0.022 ms compared to approx. 0.03 ms before (see attachment).

No change in behaviour. The motor vibrates when it is supposed to move but I cannot see or feel, respectively, any movement.

sind die Glaasmesstäbe noch "original" an der Maschine? Dann sind dass ggf analoge, es gibt konverter (die habe ich auch) hat bei mir aber nie ganz sauber funktioniert. Habe die dann gegen neue getauscht. Weiß aber nicht was das nen Haus weg hatte die Konverter oder die Stäbe.
Ich würde die Endschalter der achsen nicht zusammenfassen. Macht die Fehlersuche leichter.
Ich persönlich würde auch mehr Ausgänge machen, wie reglerfreigabe und ggf Schütze für die Stromversorhung der Hochspannung an den Treibern.

Bzw das ist ja eine die schon ne steuerung hatte, da würde ich mir die Liste der IOS aus den Manuals / Stromlaufplänen ziehen.

I was not really aware of latency issues since according to my understanding the signals are provided by the mesa card. Whether mine does so correctly I cannot tell ( and dont know how to test ) so far. In the attachments the information you asked for.The latency test was done while in the internet but no more additional load for the computer. Neither a latency test done in the past nor hardware recommendations from the web gave me any hint this could in my case be a problem. Next, I will do some research about how to adjust the bios in order to improve things.

Cheers

geebee

Ich habs jetzt mal etwas genauer durchgedacht:

Lenovo Thinkcentre als Pc
Portables18,5 Zoll Touch Display (wird gerade getestet)

Sew Movitrac MCLTEB0022-5A3-4-00 für die Hauptspindel, Ansteuerung 0-10V/rechts/links
3x Ac Servo Driver 230V Model: JMC - JAND 10002-20B
3x Heidenhain Glasmaßstab

3x Ausgang für die Achsklemmung x/y/z
1x Ausgang Werkzeugspannen sk40
1x Ausgang Kühlmittelpumpe
2x Ausgang für Getriebeschaltung Motor Rechts/Links

7x Ausgänge gesamt + einige Reserve. Die aktiven Taster am Bedienpult sollten wenn möglich Leuchten.

3x Eingang Endschalter
1x oder 3x Eingang Hardware Endschalter. Ich denke man könnte alle drei Achsen zusammenfassen.
5x Eingang Programm: Start, Pause, Stop, Vorschub Stop, Spindel Stop
5x Eingang Achse verfahren: +/-, Eilgang, x, y, z
2x Eingang Getriebeschaltung, Getriebestellung mit zwei Taster (Zweigang Getriebe)
1x Steuerspannung Ein/Aus
1x Not Aus

18x Eingänge gesamt + Reserve

3x Poti Eingang: Eilgang, Vorschub, Spindel

Ich habe keine Ahnung wie man am besten die Servos ansteuern sollte? Im Endeffekt muss die Position von den Glasmaßstäben kommen. Ich hoffe Ihr könnt mir dabei helfen. 

(venv) engin@engin:~/litex-work/liteeth/bench/ESC$ ethercat slaves -v -p 0
=== Master 0, Slave 0 ===
Device: Main
State: PREOP
Flag: E
Identity:
 Vendor Id:       0xdeadbabe
 Product code:    0x00c0ffee
 Revision number: 0x00000001
 Serial number:   0x00000000
DL information:
 FMMU bit operation: no
 Distributed clocks: no
Port  Type  Link  Loop    Signal  NextSlave
  0  MII   up    open    yes             -
  1  MII   down  closed  no              -
  2  N/A   down  closed  no              -
  3  N/A   down  closed  no              -
Mailboxes:
 Bootstrap RX: 0x0000/0, TX: 0x0000/0
 Standard  RX: 0x1000/128, TX: 0x1080/128
 Supported protocols: CoE
General:
 Group: Colorlight5A75E
 Image name:  
 Order number:  
 Device name: Colorlight 5A-75E EtherCAT Device
 CoE details:
   Enable SDO: yes
   Enable SDO Info: no
   Enable PDO Assign: no
   Enable PDO Configuration: no
   Enable Upload at startup: no
   Enable SDO complete access: no
 Flags:
   Enable SafeOp: no
   Enable notLRW: no
 Current consumption: 0 mA

Update: PREOP reached, full SII EEPROM interface workingQuick update on the Colorlight 5A-75E EtherCAT slave.Since my last post, quite a bit has moved:What works now:

• SII EEPROM emulation fully implemented and verified with IgH master
• Code:

  ethercat slaves -v
  reads identity correctly:
  • Vendor Id:
    Code:

    0xDEADBABE
    , Product code:
    Code:

    0x00C0FFEE
  • All SII categories parsed: STRINGS, GENERAL, FMMU, SYNCM
• AL state machine:
  Code:

  INIT → PREOP
• IgH configures SM0/SM1 and accepts the slave in PREOP

Current limitation:
CoE mailbox is not implemented on the FPGA side yet, so IgH fails on
CoE SDO upload ( PDO assign) and never reaches SAFEOP/OP.Next steps:

• Remove CoE declaration from ESI to bypass mailbox requirement for
  Phase 1 (bring-up with LinuxCNC and quadrature encoders)
• Then decide: implement mailbox via VexRiscv + SOES (Phase 2), or
  keep CoE-free with PDO mapping from ESI

Repository:
github.com/romanetz/liteethercat Architecture and roadmap: in the repo.The project continues the same modular LiteX approach. Once the slave
is in OP and HAL pins react to encoder movement, I'll post a video.