Advanced Search

If you use shielded tips so the bare electrode does not connect the material, I would use a second THCAD for material probing.
ONe user here stated it was crazy fast and saved a lot of time...

There you go. I've spent a few hours today updating this to add cutting forces as it was initially built for plasma table design.I don't know what kind of machine you are planning but I have put it beside my drive X (yours is Y, Z ignore.)This is based on the work energy method and assumes a 3 second cut with a 1% trapezoidal profile. eg 1% accel,  (98%) cruising and 1% decell at a cut speed of 5000 m per minute. 150 N cutting forces. Assumes a 45mm dia pinion (40 tooth Mod 1.25 gear) with 5:1 gearbox they don't seem to make a 30mm (20 tooth) pinion for a 14mm dia output shast which is the normal  one found on a planetary gearbox.It draws a trapezoid profile of the test cut.I almost left your power supply at 24 volts as it actually would do the job for those specs. I put a derating to 24v in and it shows no reduction. But it halves the available power to the same as my 2 amp motor @ 48v. So the sheet goes through all of the physical power and torque requirements

We calculate motor Average power and RMS power. I would use Average power with cutting forces. This number must be less than the available power  lists further down

So we can see that your drive under these conditions only needs 2 amps RMS at 22 volts. Further up there is a magic ratio, the System to Rotor Inertia Ratio. It should be 1:1 but not exceed it. In your case, its massively oversized for my project. And so is mine but the price is right.

Finally, we calculate the ambient heat rise. It must not exceed the drive's rating which is usually around 130 deg C when the insulation could melt. SO you can see that is not an issue and that 100deg C is usually safe.

So all in all both motors simply idle and will never be called upon to exceed their available power at which point you could loose straps. SInsummary, they can run 24/7 without the risk of loosing position!

my1987toyota wrote:

Does anybody know if the forum was actually down or is the USA starting to limit how it's citizens can interact
with others in the world? 

It's down for me as well regularly... in the USA.

QtPlasmaC updates - Master (v2.10):

• refactor button interlocking
• fix laser button state if bounds error during laser dry run

There is some mismatch with the numbering.
The pattern is lcec.<master idx>.<slave idx>.halPinName
master idx is always 0 for you. Slave idx is 0-3 in ethercat-conf.xml
but 3-6 in the hal file. They must agree.
Go through the hal file and compare with ethercat-conf.xml so you
refer to what you intend to.

Oh, wait! There is the name="D1" field used. Then the hal pin is called lcec.0.D1.halPinName.
With that info, rename the lcec variables in the hal file. D1, D2, D3 etc.
Many of us use a descriptive name like X instead of D1 and so on.

I'll add the missing pictures / manuals here since i could only attach 8 to the original post.

tommylight wrote:

Can you post from a phone or a tablet?
 

Ich habe es heute getestet, denn das Forum war wie so oft nicht erreichbar. Es war auch nicht vom Handy oder Tablet-PC aus erreichbar! 

So i changed that and it still shows the same thing

Try just changing #<_inc> to 28.8 degrees (and see what the preview looks like)
That's 360 / 12.5 though it sounds a bit too large without testing, and I don't know what it will do at 120.
(Sorry, not at a LinuxCNC machine at the moment to test it)

I found some specs for my LC60HS112 motors in the catalog:
model: LC60HS112
step angle 1.8
holding torque 4.0NM
rated current 4.0A
phase resistance 1.56 ohms
phase inductance 3.9 mH
rotor inertia 1200 g.cm2
motor weight 1.807 Kg
shaft dia. 8mm

Here are details on my motors that don't match the above catalog specs to some degree:
motor weight 1.79 Kg
shaft dia. 10mm

I messaged Lichuan to see what they say.
 

The first surprise I see is in the INI file where all the P, I and D parameters are set to zero.

Try increasing P to see if that helps.
(You can do this interactively in Halshow, though that won't save to the INI file)

linuxcnc.org/docs/html/man/man1/emccalib.1.html will save to the INI and is a menu option in the Axis GUI. I don't know if there is a way to run it from the other GUIs.

i hve not used it before, but i think others have.. you will need to pay attention to the timer function in the postgui hal file and i think maybe something else in there but i don't remember. im sure someone using it can better directly assist with whats needed or a search in here may bring something up.

spindle.0.speed-out is clearly there in the screenshot.

Two possibilities spring to mind, one of them rather wierd.

1) You have the net commands for the spindle too early in the HAL file, ie before the motmod module has been loaded.

2) The - in speed-out is the wrong sort of dash. Though it looks right in this case. Maybe try re-typing it using the minus key. I think I typed out the example text on my Mac on a train, and it likes to be clever with typography.

spindle.0.speed-out is clearly there in the screenshot.

Two possibilities spring to mind, one of them rather wierd.

1) You have the net commands for the spindle too early in the HAL file, ie before the motmod module has been loaded.

2) The - in speed-out is the wrong sort of dash. Though it looks right in this case. Maybe try re-typing it using the minus key. I think I typed out the example text on my Mac on a train, and it likes to be clever with typography.

Hallo,
die gute Nachricht ist, es fängt an zu funktionieren.
Über die vermutlichen Ursachen werde ich demnächst noch etwas schreiben, ich habe momentan einen anderen PC verwendet, ich denke das das nicht das Problem ist. Die für das Projekt vorgesehene Hardware (MSI Windbox) hat scheinbar ein Bios Problem, Linux macht da Bootprobleme. Das ist aber eine andere Baustelle.
Der Reihe nach, geflasht wird der NVEM über einen STlink Adapter, ich verwendete hier eine Software unter MXlinux zum Flashen, ich grabe das jetzt mal nicht weiter aus. Interessant war das die Software das Flashen dieser Firmware hier zeitweilig verweigerte:
github.com/scottalford75/Remora-NVEM/tree/main/Firmware
Es gibt aber ein weiteres Verzeichnis hier:
github.com/scottalford75/Remora-NVEM/tre...-NVEM-STM32/Firmware
Diese ließ sich flashen, und die hatte ich bis gestern verwendet. Linuxcnc konnte mit dieser Firmware zumindest den NVEM finden, das Einschalten der "Maschine" fuktionierte, jeder Bewegungsversuch endete in obengenannten Fehlermeldungen.
Gestern hatte ich nun noch einmal den NVEM zerlegt, um den STlink anzuschließen und noch einen Versuch mit der erstgenannten Firmware zu machen. Das Ergebnis war dasselbe Flashen verweigert mit einer nichtssagenden Fehlermeldung. Noch ein Versuch, auf einmal Flashen erfolgreich. Keine Ahnung was da schiefgelaufen ist.
Heute den Testpc mit Linuxcnc und der Anpassung nach der Youtube Anleitung vom Scott aufgesetzt, Controller dran und siehe da: Alles gut.
Die Ausgänge liefern die Signale, keine Fehlermeldungen etc..
Es ist also so das der NVEM beim Flashen bereits eine Grundkonfiguration bekommt, die dann auch ansprechbar ist.
Ein Hinweis, bitte, das ist keine Kritik, vielmehr ein Hinweis auch die Akzeptanz dieser Software beträchtlich zu steigern, vielleicht kann Scott mal das Installationsvideo hier etwas anpassen:

Hier verwendet er alte Verzeichnisstrukturen und es fehlt ein wesentlicher Schritt, der halcompile Befehl beinhaltet hier nur das Compilieren der eth Komponente, es fehlt das Compilieren der Remora-nv Komponente, ohne diese läuft Linuxcnc ebenfalls nicht mit dem NVEM.
Ich bin also der neuen Steuerung und vor allem dem Handrad (GRBL hat das nicht) ein Stück näher. Ich denke das war noch nicht der letzte Post, danke auch an Luca bis hierhin ,
Gruß
Mario