Advanced Search

No, this is close. It should work. But I have sometimes noticed that the ethercat master
uses old settings and not the new ones. Keep 1a00 and 1600.
Try these in order
"ethercat rescan",
if no change "sudo systemctl  restart ethercat",
and finally if no change, restart PC and drives.
See error messages in syslog when you start linuxcnc

You should also, not causing the problem with the drive, but still, change the line order in the hal file to 

Ihr habt natürlich recht! 
Der Stift war doch wackeliger eingespannt als gedacht.
Eine Fräsung in einem Reststück ergibt ein schönes Ergebnis - damit bin ich zufrieden!

 

Die Mesa-Karte ist immer noch am Weg, damit spiele ich mich vermutlich im Winter mal.

Ich bin jetzt noch am überlegen ob ich die Ansteuerung der Spindel-Drehzahl auch über LinuxCNC machen möchte, einfach um unabhängig von der eingebauten Platine zu sein.

Laut dem Blog von Entropia brauche ich die folgende Ansteuerung:
Über SPI auf den Pins 14,16 und 17 wird die Drehzahl eingestellt.
Die Datenrate ist 30 kHz; die Daten werden in 16bit-Worten (Big Endian) übertragen.
Bei einem ATMega328p mit 128 kHz Clock haben die folgenden SPI-Settings funktioniert:
SPCR = _BV(SPE) | _BV(MSTR) | _BV(SPR0) ;
SPSR = 1 << SPI2X;

Die gesendeten Werte sind linear Interpoliert zwischen:
14000 RPM in Editasc -> 2866
20000 RPM in Editasc -> 4094 (0x0FFE -- erster Nibbel soll stets 0 sein!)

man kann die Spindelgeschwindigkeit auch mit 64kHz (= 8MHz F_CPU / Divider 128) senden.

Wäre das eurer Meinung nach eher ein Fall für einen externen Arduino, oder kann das der Raspberry ebenfalls erzeugen und ausgeben?

langdons wrote:

The reason I mentioned the 48V not being necessarily ideal is some electronics are made with almost zero headroom above their limits.

For example, I own a 12V DELTA power supply that can be adjusted to output 14VDC; however, its filter caps are only rated for 16V!

That's 2V of headroom!

Which is absolutely fine, that is the way the designers intended.

Discussion on voltage values
www.eevblog.com/forum/beginners/is-there...igher-rated-voltage/

Hello, this is my first post in the forum. Have used it a lot to set up my machine to the point it is currently at.

So far I have it all pretty much set up and good to go with the QTPlasmaC UI, but I need some help removing the Z-axis movement from the machine.

The machine is a 2 axis plasma tube cutter, one for the rotary motion, and one for the linear. The rotary axis is actually treated like a linear one. with some clever sheetcam post processing I have created something where you can input a flat profile of the tube, and get prompted to input the tubes diameter that will do some maths to get the correct feed rate at the surface of the tube, depending on the tube diameter that was entered.

My problem starts when the plasmac software tries to home the Z-axis, even though there should be no z-axis instructions in the g-code. Then when the g-code runs it sort of gets stuck at the homing of the Z-axis, that shouldnt exist....Is there a good way to remove it entirely from the machine, and maybe even the qtplasmac UI? 

I have tried to comment out all the Z-axis parameters in the .ini and .hal files, but then i just get errors when opening up the cnc software. This is for a school related project so go easy on me!  (I have added a screenshot of the machines design in cad)
Thanks! 

Thanks again

As always, thanks to all for your valuable feedback.

Don't change the functionality, just streamline it.

You should probably change the ip from 0.0.0.0 to 127.0.0.1 or something.

Also, a nice http error message is arguably better than a console print.

Your Exceptions might be getting lost along the way somehow.

You should probably put another try/except in the ss_reset_route method just in case.

I have the delay set to 0.2 or 0.3 always, depending on thickness, i would guess 80% of my machines are at 0.3.

Good idea! I'll add a locking mechanism to the route and see if that helps. I do already have try-except wrapping the entire endpoint.

Since I'm modifying Tormach's code directly, I'm trying to keep changes minimal to avoid breaking PathPilot's core functionality.

Pathpilot is v2.10.1

I would use Tormach's internal debugging system which would write to the status logs
self.error_handler.write("My message", ALARM_LEVEL_DEBUG). I wrapped the endpoint in a try catch block so that's why I'm also very puzzled. I do however run my flask application in development like this, so I'm not sure if I'm running into a locking issue:

class FlaskAppWrapper:
def __init__(self):
....
def run(self):
try:
threading.Thread(target=self.run_app_at_port, args=(mill_port,)).start()
except Exception as e:
print "error in threading: \n" + str(e) + "\n"

def run_app_at_port(self, port):
try:
self.app.run(host="0.0.0.0", port=port, threaded=True)
except Exception as e:
print "error has occurred when running flask: \n" + str(e) + "\n"

I got the files from this post
forum.linuxcnc.org/ethercat/55806-long-i...-drive-sv660n#337330

It was from a user hanz24 at the bottom of the first page. They too were using an inovance drive but a newer model.

I tried the 1. step but no luck. Maybe I am doing something fundamentally wrong.

¿Que modelo?

Buenos días, espero que todos se encuentren bien.
Mi nombre es Santiago, Soy de Argentina.
Estoy buscando ayuda para poder comprar unas placas de Mesa electronics.
El problema es que al entrar en Mesanet estas no están disponibles.
El único proveedor que encontré bien fue mesaUS, el problema con estos es que no ofrecen envío hasta Argentina, sino dentro de estados unidos y otros países.
Quisiera saber y contactar alguien del país que haya comprado placas, o similares en el formato que se me da, que sería comprarlas en estados unidos e importarlas por otro proveedor.
Desde ya muchas gracias.
Espero su respuesta.
¡Saludos!

Good, the UNMATCHED datagrams are gone. One more step done.

Nobody needs that xml file, maybe some geek is looking at it. Linuxcnc doesn't use it,
it can read all necessary info from the drive.

So what I look at are the linesInvalid input configuration. It can be several things, but it has to do with the Syncmanagers and the PDOs.
You said you got the files from another post here, do you have a link to it?

When I look in that esi/xml file you attached I see that you use a PDO index of a fixed PDO, and it looks like you don't have the correct pdoentries in there. There are two things you can do.
1. Use a configurable PDO and put in the existing pdoentries in there.
Simply change
<pdo idx="1b01">
to
<pdo idx="1a00">

and switch
<pdo idx="1701">
to
<pdo idx="1600">

2. Put that right pdoentries in the 1b01 and 1701 pdos. Let's try 1. first.

 

Instead of returning error codes, raise Exceptions, it's cleaner and makes more sense IMO.

Also, it makes the whole program more flexible.