Advanced Search

I have a small HP ProDesk 400 G3 SFF. From your suggestion i have looked at both devices (same pc type) bios settings, as of now nothing sticks out yet.

One step forward. After some digging on the internet I went into custom_postgui.hal and changed this:

net spindle-vel-cmd-rpm gmoccapy.spindle_feedback_bar

To this:

net spindle-vel-cmd-rpm-abs gmoccapy.spindle_feedback_bar

And it now shows a green status bar in the GUI in forward and reverse.
Still working on the rpm issue.

I had a couple of Mesa cards laying around for years and finally found some time to put it into operation.
Especially because the RPi5 comes with this massive performance boost <3
It’s all basically working, except for the pinout (had to solder an adapter), and everything seems to work in auto or MDI mode,
although I only tested a few moves; but manual control is extremely choppy.

The constant movement is just interrupted, as I would have stopped pushing the the button.
Acceleration/deceleration is working, so it’s not a communication issue.

Here: 


Probably unrelated, but strange:

At the end of rapid moves, controlled via MDI, the controller or LinuxCNC creates some extra steps.
I did not count them yet, but will check this after the rest is okay:

 


Are these “user space” issues? Currently I exclusively have older RTAI setups working;
never used this one kernel thingy.

Did I set up anything incorrectly?


thx
AS

 

You are correct, Peter. When pncconf generates the configuration HAL file it include two lines that prevent LCNC from launching. A search on the forum identified the culprits and suggested the two lines be commented out. In my zeal to get on with my project, I commented out the wrong lines. Correcting the issue resolved the problems.

Kind Regards -

 

Hallo zusammen,ich stehe am Anfang eines Projekts ähnlich dem von Rüdiger und möchte meine gebrauchten Rexroth IndraDrive HSC01 in LinuxCNC über EtherCAT betreiben. Aktuell sind die Antriebe jedoch mit PROFINET-Firmware ausgestattet, weshalb ich dringend die korrekte EtherCAT-Firmware benötige.Folgende Eckdaten zu meinen Regler:

• Typ: HSC01 E1 W0003 A02 B ET EC PB L3 NN FW
• Aktuelle Firmware: FWA INDRV MPB 20V28 D5 1 NNN NN

Meine Fragen an euch:

• Ist R911330278  "FWS INDRV MP* **VRS NN ETHERCAT" tatsächlich die passende EtherCAT-Firmware für diese HSC01-Variante?
   

Rexroth selbst hilft mir nach  Nachfragen nicht weiter. Ich freue mich über jede Bestätigung, Quelle oder Hinweise zum Vorgehen!Vielen Dank im Voraus für eure Unterstützung.Viele Grüße Thomas

Hi, yes that is possible. I would actually reccommend the esp32 over the Arduino, as if I remember correctly the ADC resolution is better on the ESP.
I only ever used it with USB interface.
If you know what you are doing I guess you can run it in ttl2USB too.

Memory at d1000000 (32-bit, non-prefetchable) [disabled] [size=64K]

is suspicious, Sometimes this is BIOS option related.

Not entirely sure if this is the correct category of the forum for this question, but here goes:I've just done a completely fresh install of LinuxCNC and I'm running into a few issues — some related to EtherCAT, but also with.I'm trying to usewith a 5i25 board. I installed it and ran the following command:But I get this error:The 5i25 itself isn't broken — I’ve tested it on another PC and it works fine.When I run, I can see the board:It feels like something went wrong during the software installation. Has anyone seen this before or know what might be wrong?

As Tommy said, it's difficult to say without seeing all of your settings and such.  The sputtering is likely a connection issue of some sort, but the dive looked to me like there's something set incorrectly.  Looked like a move to cut height that was in the part rather than above the part.

Alright. I went from:

P = 2
I = 2
D =0
FF0 = 1
FF1 = 0
FF2 = 0
BIAS = 0
DEADBAND = 1
MAX_OUTPUT = 3000
ENCODER_SCALE = 4096

to

P = 0
I = 0
D = 0
FF0 = 1.0
FF1 = 0
FF2 = 0
BIAS = 0
DEADBAND = 1
MAX_OUTPUT = 3000
ENCODER_SCALE 4096

By just changing the ini I now have same forward and reverse spindle control.
However two things are different. The speed is a fraction of what is being commanded, S300, it's closer to S25 and it doesn't show a scale on the GUI in reverse, a minor issue I can address later.

I'm not sure what to # and where to add:

"PID command = signed commanded spindle speed in RPM
PID feedback = encoder RPM
PID output --> ABS --> analog out
ABS sign (of PID output) determines the FWD/REV pins"

This is definitely a step in the right direction.

I'm going to go ahead and try this. I'll let you know what it does.
The one thing I'm having a hard time wrapping my head around is even with analog control, I have speed control forward. The GUI bar turns green and moves goes up and down with the override buttons, just not in reverse. In reverse goes to a set number, a number I cannot find and stays put regardless of what's pressed. However, if I reverse the forward and reverse signals to the VFD I have the same forward control as before, now in reverse. I don't see why the same forward and reverse control shouldn't be possible,

If it's necessary to convert this to PWM to gain the same forward control as reverse, so be it, this Mitsubishi VFD is capable.
I'll cross that bridge when I reach it.
I need to gain a better understanding of Linuxcnc spindle control.
I appreciate your help.

Change pierce delay to something much smaller, like 0.2 for up to 5mm thick, 0 for up to 2mm and 0.5 for 5-10mm, etc.
Also show us other settings and the main screen while cutting.

It*s the usual things with isolcpus, coalesce waiting and so on. 

I don't think you can get rid of the jitter sound completely.
The underlying reason is that the position data sometimes misses to update the drives every DC cycle.
Let's not dive into why because we can't fix that here and now, instead see what you can do about it.
Reduce jitter is the start.
Can anything be done with the drive parameters? The drive will see a steadily changing position, every dc cycle a new delta - that's normal. Then suddenly there is a dc cycle without updated position - the drive see this as a full stop and starts doing the electric things to stop the servo. A few dc cycles later the position delta is restored but that means double delta in a dc cycle. The servo drive put the pedal to the floor to increase the speed. So that's what happens. Are there any settings in the drive to handle this essentially very high acceleration? Maybe max acceleration? Match that with the setting in linuxcnc (25% higher is a guideline there). That will reduce the speed change and the jitter noise.

There is a test you can do to see if this mechanism is the problem. Add a ddt component, connect position feedback from one of the servo drives to ddt.in and plot ddt.out in halscope. At a constant travel speed this should be a straight line more or less. When jitter happens you will see the ddt.out making a jump to zero or double value. It's a way to verify but unfortunately not to solve.

Hallo zusammen,

erinnert durch dieses Thread hier, dass ich meine Glasmaßstäbe noch nicht zu 100% am Laufen habe,
hänge ich mich mal hier dran.

Ich habe die Ditron DC11 an meiner Drehmaschine verbaut, diese funktionieren soweit auch,
allerdings bekomme ich kein Indexsignal, also muss ich mit Referenzschaltern arbeiten, was
wieder zu Ungenauigkeiten führt. Das würde ich gerne noch ändern und hoffe, dass ihr mir dabei helfen könnt.

Hier ist die Pinbelegung welche ich an der 7i85 (ohne S) benutzt habe:
 
 

und hier die HAL und INI:
 
 
 

thanks for the hint with the wiki! -). I just added this under "Misc stuff".