Advanced Search

Joco wrote:

And that behaviour continues under scurve planner?  That was what I was referring to. Not what standard planner does.

@Joco - my apologies, I completely misunderstood your original warning.  I thought you were concerned that the current TP maybe didn't lock out FH and motion-inhibit as advertised, and perhaps that situation was carried in to Grotius' s-curve TP.

I have not tested the s-curve TP's behavior.

Sorry to all for the unnecessary tangent.

I've failed to work out how to use a spare encoder input on the 7i77 as a Limit switch input.
I've started out by telling PNCConf that the switches are connected to the I/O Field inputs so I can see the syntax, for instance 
net min-x     <=  hm2_7i92.0.7i77.0.0.input-00     for the X limit minus.
Was planning then to edit this line to match an encoder.

But when I study the hal file posted here, I cannot see how the encoder input pins are called. I was expecting there to be similar 7i92..7i77 references in the Joint 0 section for instance and there are for the analogue outputs, but not against the encoders.
Can you help please.
Thanks

Well done!
I will update/patch and try some more codes on my testmachines this evening (living in Germany btw.). I will report back then.

@Julian,

The file seems to run now under -> ./start_axis_9
I removed some segment length checks like : < 1e-12
This is a very tiny value, but it was enough to halt the planner so now and then.
Code is updated.
 

Hello
i have a similar problem. What was the solution ? where connection PUL+ PUL- DIR+ DIR- on the servo drive ?

Hallo, ich habe mal wieder ein paar Detailfragen. Heute der "motor-0-position error"

Mittlerweile läuft meine Maschine unter Probe Basic - ich habe die Werkzeugvermessung unter Dragon einfach nicht hin bekommen. Die Routine von TooTall18T in Version 5(dev.) läuft jetzt auch, der Support von ihm war top.

Folgendes Problem nervt mich gerade: Ich verfahre per Handrad die X Achse, tw mit vollem G0=7,5m/min, das läuft gut, aber beim Bremsen aus Feeds ab 4m/min kommt fast immer der Fehler motor-0-position error. Auf allen Achsen kommt dieser Fehler.
Ich habe 400W Servos von OMC Stepperonline, die autark ihre Rampen steuern, LCNC bekommt davon nichts mit, die sehen für LCNC ja aus wie Stepper. Keine Glasmaßsstäbe/Encoder zusätzlich.

Was ist die Ursache dafür? Muss ich die Beschleunigung rauf oder runterdrehen? Ist jetzt bei 1000. Eigentlich ginge noch mehr.
Ist etwas ganz anderes dafür verantwortlich?

Meine Steplen/stepspace Einstellungen sind bei 2500/2500, die Servos können bis 500kHz am Eingang und wollen mindestens 2 bzw 1 µsec Periode/Pulslänge haben.

Die Latency Tests sind ausreichend  und die Netzwerk Pings auf die Karte ebenfalls. ODer was meint Ihr?
Latency: Servo Jitter 14646, Base Jitter 11328 after 10 minutes. Pings to 10.10.10.10 ~ 0.066-0.081

Noch was: Mein Handrad habe ich etwas gedämpft mit jog-accel Werten von X 0.4 Y 0.25 Z0.2 - hat das evtl eine Auswirkung?

Ich hänge mal meine HAL und INI an.   
Leider kann ich keine Fotos anhängen, obwohl die unter 1MB groß sind.


Vielen Dank fürs Draufgucken und Hinweise! Hanno

Now i have change the entry STEP_SCALE in the *.ini file and the scale in *.hal file but it changes nothing.

Any ideas?

Greetings

Hi everyone
I need some help with ATC.
I used remap m6 Python and need some button to change the tool (M6 TX).
I can't use MDI for some reason
Do you have any thoughts on this?

Your screen shot looks correct. I added multi state labels on the 20th, how are you updating?






JT

Take a look at this thread for the coordination of an external E-Stop with LinuxCNC
forum.linuxcnc.org/47-hal-examples/25861-external-e-stop

I have not tested an external E-Stop so the colors may not stay in sync.

machinedude wrote:

you might want to try a feature in CAM like smoothing. that will reduce the number of line segments in your geometry which might help with acceleration.

i think when you get into the fine details of your cuts you just don't have enough space to get up to speed. it seems like you are getting a lot of heat buildup at the top around the head and at the base around the feet on your project.

fine details like yours are probably more suited for laser cutting and would produce what i think you are looking for, but you can try some stuff tommy pointed out to see how far you can get with plasma. i would try looking into the design and try to keep your geometry as simple as possible to keep your cuts flowing the best you can too. give the machine the best chance it can to maintain cutting speed aided by design choices.

Thank you, i understand. What i am trying to figure out is if i have problems that i need to fix as for the machine/hardware so i stay only to figure out the best i can do by settings/software.

STEP_SCALE in your ini file sets the number of steps per mm (assuming metric units)
Determine the resolution of your encoder in steps per revolution
Allowing for any gear reduction and ball screw pitch, calculate the distance travelled per motor revolution
Calculate the number of steps travelled per motor revolution
Calculate the number of steps per mm. 
Enter this as your STEP_SCALE

you might want to try a feature in CAM like smoothing. that will reduce the number of line segments in your geometry which might help with acceleration.

i think when you get into the fine details of your cuts you just don't have enough space to get up to speed. it seems like you are getting a lot of heat buildup at the top around the head and at the base around the feet on your project.

fine details like yours are probably more suited for laser cutting and would produce what i think you are looking for, but you can try some stuff tommy pointed out to see how far you can get with plasma. i would try looking into the design and try to keep your geometry as simple as possible to keep your cuts flowing the best you can too. give the machine the best chance it can to maintain cutting speed aided by design choices.

Probably ought to point out the misprint in your Basic Hal Tutorial Link.
linuxcnc.org/docs/html/hal/basic-hal.html (above)
linuxcnc.org/docs/html/hal/basic_hal.html (should be)

Also jetz versteh ich es langsam. Der Motor dreht zumindest mal wie er soll. Ethercat-Config verstehe ich jetz langsam auch. Wie kann ich nun aber den Weg einstellen, das der Motor bei angeforderten 5mm auch die 5mm zurück legt? Mit stepconf war das ja relativ simpel aber wie mach ich das beim Ethercat?

Besten dank für die Hilfe.