Advanced Search

I can make 7I76EU  + 7I85 + 7I74 firmware but not sure why you would need the 7I74
as there are 6 available Sserial ports with just the 7I76EU (1) and 7I85 (5).

7i76eu_7i76x1_7i85x1d.bin is the firmware for a 7I76EU and a 7I85.

 

Hello,

I am using a Mesa 7I76EU board and would like to know if a firmware configuration exists that supports simultaneous operation with a standard 7I85 board and a 7I74 board.

My planned hardware configuration is:

* Mesa 7I76EU
* Mesa 7I85 (standard 7I85, not 7I85S)
* Mesa 7I74
* Two Mesa 7I84U boards connected through the 7I74

I have successfully tested the following firmware:

7i76eu_7i76x1_7i85x1d.bin

The firmware was loaded successfully, and LinuxCNC correctly detected all six MuxedQCount channels provided by the 7I85.

After loading this firmware, LinuxCNC reports:

* 6 MuxedQCount channels
* 1 MuxedQCountSel channel

The 7I85 board will be used to connect four RS-422 linear scales (X, Y, Z, and W).

The 7I74 board will be used as a Smart Serial Hub for two 7I84U I/O expansion boards.

While reviewing the Mesa firmware archive for the 7I76EU, I could not find a ready-made firmware configuration for:

7I76EU + 7I85 + 7I74

However, I found the following VHDL source file:

PIN_7I76x1_7i85sx1_7i74x1D_51.vhd

which suggests that a configuration for a 7I85S + 7I74 combination exists.

I would appreciate advice on the following:

* Is there an existing firmware configuration for the standard 7I85 and 7I74 combination?
* If not, is it possible to obtain such a configuration from Mesa or build it from the available source files?
* Are there any FPGA resource limitations on the 7I76EU that would prevent simultaneous use of both the 7I85 and the 7I74?

Any information or recommendations would be greatly appreciated.

Thank you.
 

No ARCOK signal on those, use the derived signal (mode 0 or 1, i forgot) so no need for it, and it works perfectly fine with those plasma sources.
But first, check if the torch starts in mid air.

Hi everyone,
I'm currently building my plasma CNC setup with LinuxCNC and need some help with wiring. Maybe someone here has the same plasma cutter.
Hardware:
- Plasma cutter: Stahlwerk CUT 60 P Digital
- Motion control: Mesa 7i96S
- Voltage sensing: THCAD-2

My main question:

I'm trying to understand where to find the ARC starting signal on my plasma cutter. The signal that tells LinuxCNC: "The arc is burning, movement can begin."

In many tutorials or forums, I read about a dedicated ARC OK output on the plasma.
(See Attachment: the plasma cutter signal control has 4 pins 1, 2, 3 and 4)

On the Stahlwerk CUT 60 P Digital, I only find:
1. THC interface
2. The control socket (where the hand torch trigger normally plugs in) (pin 3 and 4)
3. I can´t find pins 1 and 2 or find anything to how to get the arc signal otherwise 

My specific questions:

1. Does the 2-pin THC output not only provide the voltage for the THCAD-2 but also a signal that tells me whether the arc is stable?

2. Do I need to get ARC OK somewhere else? I read in another forum that some plasma units don't have a dedicated ARC OK and you have to use a current sensor (e.g., Hall sensor) to detect whether current is flowing. Could this be the case with Stahlwerk?

3. What about the control socket? When I unplug the hand torch from the control socket, I have the contacts that previously connected the trigger. Does the Stahlwerk send any signal back through this socket that I could use as ARC starting signal? Or is it really just a passive input for the trigger?

4. Generally what should I do?

What I already understand:

- The THCAD-2 connects to the THC interface (the 2 pins) and then to the encoder input of the Mesa 7i96S. That's for THC voltage measurement.
- Torch start/stop ill get it directly of the cable
- But what about ARC starting signal output? How does LinuxCNC know the arc is actually there and can safely start moving?

How would you solve this with the Stahlwerk CUT 60 P Digital?** Is there a hidden ARC OK output I'm missing? Or are you all working with a current sensor?

Any help is appreciated – photos or pinouts would be great if anyone has them!

Thanks in advance

eigentlich nicht.
Solange du nicht irgendwelche Systemeinstellungen verbogen hast, solltest du erst mal die Schritte von rodw ausführen.
 

github.com/persei802/QtDragon_hd

Zunächst einmal danke fürs Feedback. Ich habe den Eindruck, dass es sich um etwas Größeres handelt, da ich bei der Installation von Ethernet recht viel herumprobieren musste. Ich habe so langsam den Eindruck, dass ich mir einige Stolpersteine selbst in den Weg gelegt habe. Wie bekomme ich das System wieder aufgeräumt?Oder wäre es besser, das System neu aufzusetzen und von vorne anzufangen?Noch ist keine Maschine darauf, die darauf laufen muss. Es ist ein neues System, das erst noch hochgefahren werden muss.

Maybe look in to extra joints:

linuxcnc.org/docs/stable/html/man/man9/motion.9.html

You can set the joint to home-in-place in the INI file so LCNC doesn't try to move it.  

Thanks Rod, I wasn't aware of that utility, I shall investigate.

The rest of the machine is under G code control, I use it to set the bending depth and the horizontal and vertical position of the backstops, so I'm not sure a DRO alone will cut the mustard.

Hello everyone,

I am looking for the electrical schematics (wiring diagrams / Stromlaufplan) for a Deckel Maho DMU 50M, equipped with a Heidenhain TNC 310 control.

I am currently troubleshooting the machine and would greatly appreciate it if someone could share the electrical documentation, schematics, or any related service manuals.

Thank you in advance for any assistance.

Best regards

I have not visited the facility where the machine is located yet to test it out.

snowgoer540 wrote:

This sounds like an autorepeat issue I've experienced in the past.

To test if it is, open a terminal window, and enter the following command:

xset -r

Launch LinuxCNC and jog around. If the problem goes away, that's the issue and we can come up with a more permanent solution.

To turn autorepeat back on:

xset r

Did this yield any results yet?

Use the software Tommy linked to to burn the ISO to a USB stick.
check the BIOS is set up to allow booting from USB
Disable UEFI/Secure boot while you are there.
Plug the USB in and boot your PC which should load the installer from the USB

Error finishing read means that the time to read the Mesa card did not finish before the end of the servo thread cycle.
Usually, this will disable the Mesa card until reset or restarted.
Follow these steps. 
1. Uninstall Ethercat just in case (but could do this as the last step if required)
2. if you have a Realtek NIC, install the correct Realtek driver r8168-dkms or r8125-dkms
4. If Intel NIC, disable coalescing. type man hm2_eth and follow the instructions adjusting for your Mesa ip address
5. Set isolcpus = your_last_core in the grub parameters. The LinuxCNC ISO install grub_customizer to make this easy (sudo grub_customizer)
6. Set the CPU affinity on the IRQ used for the Ethernet NIC to be your_last_core (same as isolcpus)
7, disable EEE (energy efficient Ethernet)
8 set the governor to performance

Some of these settings don't persist on a reboot so you'd need to run a script on startup to lock them in 

der Fehler kommt erst, wenn ich auf ausführen klicke.

Der 'Ausführen' button ist in deinem Fall nicht von Belang. Der ist dazu da Hal-Commands, die in die Zeile daneben eingegeben werden, auszuführen.

]Wenn ich die Endschalter drücke, ändern sie nicht die Anzeige,

Solange die Pins der Referenzsignale sich nicht ändern wenn du die Schalter drückst kann das Refernzfahren nicht funktionieren.

Wenn nun plötzlich keiner der Schalter mehr zu einer Veränderung in der Halshow führt, dann würde ich stark vermuten, dass der Fehler in der Verkabelung oder der Elektronik (zb Mesakarte) zu suchen ist.
Also mal gucken ob sich an der Karte die Spannung am entsprechenden Eingang ändert wenn du die Referenzschalter drückst.