Hello! Thank you for your support! I only use 7i91th.

Can someone help me create a Python script to record positions in the event of a power loss or LinuxCNC error?

I plan to create an external real-time position logger with an update interval of 0.001 seconds. I use this feature for a wirecut machine. I'm using a Python script and have tried activating log_position_to_txt.py with the M-code command, but the position logging process results in a code overflow, causing the .txt file to grow uncontrollably.

Here's the code for log_position_to_txt.py:

##############################
#!/usr/bin/env python2.7
import linuxcnc
import time

stat = linuxcnc.stat()

with open("position-log.txt", "w") as outfile:

while True:

stat.poll()
x,y,z,a,b,c,u,v,w = stat.actual_position

outfile.write("X ")
outfile.write("{:.4f}\n".format(x))
outfile.write("Y ")
outfile.write("{:.4f}\n".format(y))

time.sleep(0.001)
####################################


Can someone help me fix my Python script so that... position recording does not result in code accumulation?

I'm afraid we really don't have enough information to help you.

We have to assume that the new drive isn't configured the same as your old one. Are both the new and old drives the same model and version? (There are different models of Delta Servos that are the same size and look simular, but the motors from an older one are not compatible with a newer drive or vice versa.)

Do you have a back up of all of the parameters from the old drive? Assuming that your new drive is the same model as the old one, you would need to load the parameter settings from the old one to the new one in order for it to behave as before. If you don't have either a software backup of the parameters, or written down paper copy of the parameter settings, then you will have to figure out what they need to be. We can't really help you with that though unless you tell us how the motor/drivev is mis behaving.

I found this link there is probably working configuration of your drive ... there is output from raw config ... it should works

Hi Gartenzwerg,

ich habe deinen Post leider zu spät gelesen. Ich hätte noch einen Tipp für ein passendes Mainboard:
Asrock-n100dc-itx   inkl. CPU   -  und Parallel Header
Ich setze das bei meinem CNC Umbau einer Langlochbohrmaschine (Zinkenfräse) ein und macht einen guten Job. (Latenzen um die 8000), nur verwende ich nicht den Par. Port sondern über Lan.
Nur weil ich neugierig bin - von wo bist du im Osten Ö? : ich komme aus dem 3 Länder Eck: Stmk - Bgld - NÖ

lg 

 

Yes more info is needed. I think you had that type of problem before, endian?

There is one setting. After reading through the esi file I see there is only DC sync supported, no async or sm sync.
Add this line to the xml file after the     <slave idx="0" line

Edit. You already have that. It's early...

I think Intel is now promoting PREEMPT_RT and have their own optimized RT kernel so the linuxcnc/ethercat stuff is just a tutorial for their users...

Thanks for the documentation and this details, I'll read it carefully.

As for G-code, I'll have to delve deeper into it; for now, I'm far from mastering it.

I put a simple stepper motor in the last row to show visitors that it can drive Ethercat motors along with stepper /dir motors.

YOu can find detailed information at;
www.egerobotics.com/ethercat-dig32-io-interface
www.egerobotics.com/ethercat-digital-analog-io-board
www.egerobotics.com/ethercat-encoder-interface
www.egerobotics.com/ethercat-pwm-rc-servo-interface

try 

then 

show current config 

Doesn't anyone use a rotary axis anymore, and does no one know what the problem might be?

Not really, it's codes in Python in the vtk, and any updates will over write your edits.

Because there are different methods to measure diameter and different toolsetter types, it's a very per situation basis. You just need to write in the macro code for it. There is allot of previously functionality for it already in basic. Start by reading the rs274ngc code documents and looking over the existing subroutines for probing. It's really not too difficult if you have a decent gcode understanding. Nothing like writing program python for example.

The manual is short, look at the section reviewing subroutines. I have attached it for your reference. Also view the linuxcnc docs section regarding owords.

 
 

Thanks, chips are being made as we speak. And I am feeling more comfortable now it is working again (it is amazing how edgy having bits of the workshop broken makes me feel.