Advanced Search

Hello,

We created the `toolchanger_index_new` HAL file to map all the M-codes for `toolchange.ngc`; this kept things reasonably organized and allowed us to track what codes like M66 actually do.
Then we built the NGC file.
Once that was done, we integrated everything and added the remap section to the INI file.
When we started LinuxCNC, we got the error message mentioned in the previous post.
We suspect there might be an issue with the file path or something similar.
As soon as we comment out the remap configuration, everything runs without problems again.

The only exception is the `conv-float-32` converter; it used to work, but now LinuxCNC claims it already exists.
That is likely a separate issue and unrelated to the mapping setup mentioned above.

Tom, I tried everything, inverted the home encoder phases and all the possible settings... if I set the correct axis (reversed) everything is fine but the plot is mirrored and home moved to the left outside the frame.

MIN_LIMIT = -380
MAX_LIMIT = 0.01
Wrong for Y axis, should be reversed.
Might also need to change direction and/or homing directions, by adding - in front of the scale and HOME_ values.

Never mind I was able to figure it out.

Here they are, I changed TCL with a modified one but it's not its fault, it does the same with the original one.

hal and ini ?

I've had this CNC with a closed-loop DC servo for a long time, and it works well for both movement and backplot with the home dot at x0 y0 as seen in the photo. The only problem is that it only works well with the y-axis inverted; the y-axis moves away in a negative direction. I decided to set the axis to positive as the x-axis, but the home dot moves to the left, and I haven't found a way to set them in step... basically, the plot moves outside the work area. Could it be that I changed the order of the pwmgens to match x and spindle on a 7i40hv and y and z on another to use two different voltages for the motors?

Hello PCW,

Thank you for your advice.

You were absolutely right — I did not need the 7I74.

I connected the 7I85 to the 7I76EU P1 port and then connected two 7I84U boards directly to the Smart Serial ports on the 7I85.

Everything is now working correctly:

* 7I85 is detected and provides the expected MuxedQCount resources.
* Both 7I84U boards are detected through Smart Serial.
* Inputs and outputs on both 7I84U boards have been tested successfully.
* LinuxCNC sees both boards after enabling the corresponding Smart Serial channels.

The final configuration is:

* Mesa 7I76EU
* Mesa 7I85
* Mesa 7I84U #1
* Mesa 7I84U #2

using the firmware:

7i76eu_7i76x1_7i85x1d.bin

Thank you for pointing me in the right direction and helping me simplify the system.

Best regards,
Roman

Ich persönlich würde ganz von vorne anfangen und direkt alles erledigen was in den Antworten bereits geschrieben steht.
Jetzt versuchen alles aufzuräumen und die Gefahr etwas "entscheidendes" zu vergessen, ist einfach zu groß m.M.n.
Wahrscheinlich gehts sogar schneller.

Gruß
Olli

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