Advanced Search

Ja ein Seperater RCD ist eine gute Wahl dann aber den richtigen
Nicht den 08 15 das Schütz soll stören seltsam dann müssten die
Störungen weg sein wenn man es brückt oder die Störung tritt nur auf beim ein und Ausschalten…
Ich habe nach wie vor das Netzteil im Verdacht erzeugt ja keine echte 5 V sonder eine PWM das läst sich aber rausfinden Netzteil weg und das Raspbery mit anderen 5 V versorgen ….


Gruß
Jürgen

ja der ich möchte sie gern "ursprünglich" halten 1 Servo 3 Kupplungen

It is relatively easy to have a halpin execute the current mdi command in gmoccapy.py:

create the pin:


Create the handler:

As mentioned above, you would want to remove all other events in 'hal_mdihistory.py' that currently execute the 'submit()' function (eg. double clicking on an entry):
github.com/LinuxCNC/linuxcnc/blob/master...l_mdihistory.py#L151

GUI development in LinuxCNC has, generally speaking, not been driven by industry standards but by what is convenient and the easiest way forward, which is also what most lower end users want.
Personally I would welcome a GUI that could at least be configured to only allow initiation of physical machine movement through hal pins. This would also remove the possibility to start a tool change by mouse click from the GUI.

Hi, 
@3404gerber
I am using this configuration and it works so far. There are only massive problems with security issues. But that's another matter.
Provided that homecomp.comp has not been changed, it should work.

@Konstatin
You have massive EMC problems. dmesg shows a bunch of errors even before Linuxcnc is loaded.
1. CAT5 cables are unsuitable > use CAT6
2. Use short cables, no loops!!!
3. Lay cables away from other wires
4. Attach Feritt cores
5. Servo interference suppression EMC filter

6. Only when “dmesg | grep ethercat” shows no more errors before starting lcnc can you focus on the lcnc configuration.

 

tar_san wrote:

And I think .. sometimes updating new ESI to older software version device is a little bit risky..
I'm considering a little bit about it.

Yes, the ESI file must agree with the firmware in the drive.
I thought about warning for that, but since you were in contact
with Yaskawa support I thought they must know, they should know.

I think the data looks okay for you Hannes, and it seems likely that the firmware on your pendant doesn't support the F/S indications. I am not setup to build linuxcnc on this machine right now, but here is a screenshot from Wireshark showing the same type of data as your terminal output:
 
The highlighted line is the last part of the report, where the feed and spindle overrides are given. For me, both were at 100% = hex 0x64. My pendant also shows the F/S values in auto mode when a program is running. Many different firmware variants, I suppose...

I've had LinuxCNC simulation running a long G-code program a couple of nights to see if I can find some issues with my dongle firmware. So far, no disconnects nor any other meaningful issues. Sometimes (around 0.0035% of the time) it send a zero-length package, which is not correct, but neither is it harmful. I will try to look over the USB handling to see if I can get rid of that one.

Das einzige ähnliche Umbau der ich kenne ist This Old Tony's Video Series, aber er hat sein MH400 umgebaut auf 3 getrennte Achsen Motoren, und KUS.

Hi everyone,I’m adding a C axis to my CNC lathe and running into an issue I can’t figure out.Previously, the axis would rotate (basic motion was working), but I hadn’t properly tuned the scale or step settings yet. Now, after adjusting parameters, I’m getting a consistent problem:As soon as I enable the machine and try to jog the C axis (C+ or C-), LinuxCNC immediately throws a “Joint 2 error”and disables the machine.Details:

• AC servo drive in step/dir mode
• Encoder is connected only to the drive (not to LinuxCNC)
• C axis is configured as ANGULAR
• SCALE = 27.78 (assuming 10,000 pulses per revolution)
• MAX_VELOCITY ≈ 60–72 deg/sec
• MAX_ACCELERATION ≈ 200–230 deg/sec²

The axis previously rotated before I changed scaling parameters, so I don’t believe it’s a wiring issue.I’m trying to understand:

• Why LinuxCNC is throwing a Joint 2 error immediately
• Whether this is a scaling issue, limits issue, or configuration issue
• What I should check next (HAL wiring, limits, FERROR, kinematics, etc.)

Any guidance from someone experienced with adding a C axis to a lathe would be greatly appreciated.
Also I did use ChatGPT to turn my ape thoughts into human ones, anyways any help would be appreciated thanks!!!

T3 ist das Netzteil für das Raspberry Pi. Ist das offizielle also hatte ich gehofft die Qualität ist etwas besser. Die Buskabel sind hochwertige von Lütze mit Siemens Profinet Steckern. Benutzen wir auf der Arbeit auch so.

Unter dem Metallsteg sitzen das Hauptschütz wo 3 Phasen und Neutralleiter dranhängen, ich tippe, dass das Probleme macht. Ist zwar suboptimal mit dem Metallsteg aber solange es funktioniert... Kommt eh ein Deckel drauf.

Mit dem RCD muss ich noch gucken, ich muss eh die Elektroinstallation neumachen da ich in der Werkstatt noch keinen Drehstrom habe. Hoffe wenn ich da einen extra RCD für die Maschine setze ist der Ableitstrom nicht zu hoch. Als ich so getestet habe (einfach temporär in der UV abgegriffen) hat der RCD ausgelöst aber da kamen ja noch ableitströme vom restlichen Haus dazu.

Run it again,

At the bottom once it completes running and you have an entry line again run the following command:

Sudo apt --fix-broken install

This will collect and install any missing dependencies and should complete the installation.

Here is two screen shots of the current state of the software, I am making it in python and will push it into the qtplasmac when its useable. im trying to keep it simple and easy/straight forward to learn/use. still is very buggy but am making progress. The goal is with the software is to bring the fabricator closer to the machine, its not to replace a real cad software just for drawing parts fast and easy. conversational cad.    

Yes, typically this is caused by  a wiring error or worst case,
a damaged 7I77D output chip.

Moved to "driver boards".
-
Check the wiring, or post pictures of the wiring here so we can have a look.

I am using a optocoupler (from amazon) between my 7i77D output and a solenoid valve for a spindle break in the sinking configuration, the output is over-temperature faulting for some reason.
using TB8 OUTPUT0. Field voltage is 24Vdc and driving the relay with the same 24 power supply. 
I set up the opto relay on the bench and it only draws 2.2ma on the input in low position.
I'm kind of at a loss, the manual says the outputs can take up to 350ma.

Please advise
John V.
 

Let's see how long it takes for such cr@p to reach Europe...