Hi Lcvette

Thank you so much for your help, it works perfectly. Thanks also for all the work you do here every day, helping out beginners like me. Fantastic!

The device name can be anything but must be consistent within the source file

Not sure about the addf issue, I will take a look at a working gs10- hal file later today

tommylight wrote:

Can you post from a phone or a tablet?

Das konnte ich leider nicht testen, sorry.

andrax wrote:

Geht mir genauso.
Nur dass das Forum fast einen 1/2 Tag nicht erreichbar ist. Und das jeden tag

Ja, das Forum ist oft nicht erreichbar oder reagiert sehr langsam.
Das finde ich sehr schade und es ist sicherlich auch nicht förderlich für die Community.
Daher habe ich ein Angebot erstellt. => forum.linuxcnc.org/36-using-this-forum-q...bility-and-structure

DEUTSCH

Erst einmal danke für Eure Einschätzung.

Dass mir Mesa oder Leadshine Support geben würden, davon bin ich ehrlich gesagt nicht wirklich ausgegangen. Umso besser zu wissen, dass Mesa hier offenbar gut unterstützt.

Leadshine kenne ich bisher noch nicht wirklich. Ich habe die Produkte aber vermehrt in Videos gesehen und frage mich aktuell, ob das tatsächlich etwas Hochwertiges und langfristig Brauchbares ist.

Ja, die Verkabelung scheint deutlich sauberer zu sein.
Das würde mir sehr gefallen und käme meinem Ordnungswahn definitiv entgegen.

Du hast recht, die haben sehr viele IOs. Tatsächlich habe ich mir noch nicht im Detail angeschaut, was die alles mitbringen.
Da ich 4 Achsen (XYZC) habe, kommt da schon einiges zusammen. Ich muss mir die Geräte noch genauer ansehen, was sie von Haus aus können. Manche scheinen ja sogar ihre Referenzfahrt über das Drehmoment erledigen zu können, was wiederum Sensoren und zusätzliche Verkabelung einsparen würde.
Eventuell ginge es auch kleiner als die EL8-Drives.

Zusätzlich habe ich mir einen EtherCAT-Treiber für Schrittmotoren angeschaut:
www.omc-stepperonline.com/de/y-series-et...schrittmotor-dm556ec

Ich bin bei diesem Thema noch recht unsicher, aber wenn ich mir diesen Treiber ansehe, kann ich weder die Stromstärke (Ampere) noch die Schrittauflösung direkt am Treiber einstellen, so wie man es von klassischen Schrittmotortreibern mit DIP-Schaltern kennt.

Wenn ich das richtig verstanden habe, erfolgt diese Parametrierung dann über LinuxCNC, beziehungsweise über die XML- bzw. ESI-Datei, die für EtherCAT verwendet wird.
Ist das so korrekt, wie ich das aktuell interpretiere?

Ich bin aktuell noch nicht zu 100 Prozent von einem neuen Weg überzeugt und muss mich erst noch entscheiden, welchen Weg ich letztlich gehen möchte.

Ich möchte mir dabei nicht nur die Funktionen anschauen, sondern auch die Preise. Leider sehe ich bei Leadshine bisher keine Preise.
Die Webseite scheint meine Mailadresse nicht zu mögen, da ich dort ständig einen Syntax-Fehler angezeigt bekomme.

Und ja, eine gute Dokumentation wäre definitiv wünschenswert.

VG
Mücke

ENGLISH

First of all, thank you for your opinions.

I honestly did not expect to get support from Mesa or Leadshine, so it is good to know that Mesa offers solid support.

I am not very familiar with Leadshine yet. I have seen their products more often in videos, and I am currently wondering if they are really high quality and suitable for long-term use.

The wiring looks much cleaner.
I would really like that, as it fits well with my need for order.

You are right, they have a lot of I/Os. I have not yet looked at all the details of what they offer.
Since I have 4 axes (XYZC), quite a lot adds up. I still need to take a closer look at what the devices can do out of the box. Some of them seem to be able to perform homing using torque, which could save sensors and additional wiring.
Maybe smaller drives than the EL8 would also be sufficient.

I also looked at an EtherCAT stepper motor drive:
www.omc-stepperonline.com/de/y-series-et...schrittmotor-dm556ec

I am still quite unsure about this topic, but when I look at this drive, I cannot set the motor current (amps) or the step resolution directly on the drive, like on classic stepper drivers with DIP switches.

If I understand this correctly, these parameters are configured via LinuxCNC, or via the XML / ESI file used for EtherCAT.
Is this interpretation correct?

I am currently not 100 percent convinced about choosing a new approach and still need to decide which path I want to take.

I want to look not only at the functions, but also at the prices. Unfortunately, I cannot find any prices from Leadshine yet.
The website seems to have a problem with my email address, as I always get a syntax error.

And yes, good documentation would definitely be appreciated.

Best regards
Mücke

Ok,

in that case I would try setting the outputs in HAL Show and verify it with a multimeter.
If that does not work, you probably know what signal does not work, it is unlikely that everything does not work, and you said that the drive enables.
If it works but over the normal GUI it does not, I am out of ideas as well.

So i have created my XML and a halfile which i think has some problems but i cant seem to get it to load i have attached the report and all my configs   

I've built linuxcnc from source many times, but since upgrading to trixie, it no longer works. I'm following the instructions at  Building LinuxCNC . I don't think they are entirely correct. In section 4.2 (Building Debian Packages) it says the following: The result of ./debian/configure is bash: ./debian/configure: No such file or directory
If I don't cd into src, like it says in the previous step, then configure works.
The result of sudo apt-get build-dep . is Error: Unsupported file . given on commandline
The result without the . is Error: Unable to locate package build-dep
If I just go ahead anyway and run the last line, it seems to compile but ends with:

Since it appears buildbot is not building debs for trixie, my only option is to build from source. What is the correct procedure for building deb files for trixie? Thanks,
Jim
 

Hey PCW,
thank you. I updated LCNC from 2.9.4 to 2.9.8 to use mesambccc.
I saw some comment of your gs10 vdf and tried to edit this.
I created a mbccs file only with "run" and "heatsink-temperature" to test

My first question:
in my Omron_MX2.mbccs file. there is some device name. I tried to use a different name like "OmronMX2" but it seems, only gs10 or wj200 should work. [/code][/code]

[/code][/code][/code][/code]
[/code][/code][/code]


[/code][/code][/code][/code][/code][/code]

OK I figured it out almost
The analog pins are PWMs
But if i put this into my HAL:
setp hm2_[MESA](BOARD).0.pwmgen.00.dither true
setp hm2_[MESA](BOARD).0.pwmgen.00.output-type 1 #PWM pin0
setp hm2_[MESA](BOARD).0.pwmgen.00.offset-mode 1 # offset mode so 50% = 0
setp hm2_[MESA](BOARD).0.pwmgen.00.scale 10
setp hm2_[MESA](BOARD).0.pwmgen.00.value 1.0
I get 4.2 volt
Why? I have just double-checked 10/1 = 1

Using the index as home in hal is not what I meant, LinuxCNC does support homing to index:

linuxcnc.org/docs/html/config/ini-homing.html#_configuration

See homing type = index only
 

Thank you for your response.

I forgot to mention that before installing it on LinuxCNC, I tested it with a potentiometer powered by an external 10V source and a 3-position switch for enable and rev, and it worked fine. The problem arises when I try to connect it to the Bob and LinuxCNC. I'm using the Probe Basic interface, but I've also tried it with Axis and the same thing happens.

 

 

7I97 analog outputs are generated from PWM
which requires some setup:


 ---PWM Generator signals/setup---
setp hm2_7i97.0.pwmgen.pwm_frequency 75000
setp  hm2_7i97.0.pwmgen.00.output-type 1 #PWM pin0
setp  hm2_7i97.0.pwmgen.00.offset-mode 1 # offset mode so 50% = 0
setp  hm2_7i97.0.pwmgen.00.scale  10
setp hm2_7i97.0.pwmgen.00.enable true

setp hm2_7i97.0.pwmgen.00.value 1.0


 

I don’t know that specific driver, but what I would try is separating the drive from LinuxCNC first.
There is probably a manual mode to turn the drive by using the front panel on the drive itself.
After that, you can set the needed inputs directly (wired to your DC sources) and use a low voltage (AA battery or similar) to give the analog input directly.
Then, if that works but still not in CNC control, you at least know that LinuxCNC is actually the problem.