Advanced Search

in the linuxcnc documentation this example of gcode is provided
G49
G38.2 Z-100 F100
#<zworkoffset> = [#[5203 + #5220 * 20] + #5213 * #5210]
G10 L1 P#5400 Z#<zworkoffset> (set new tool offset)
G43
i want to understand this equation #<zworkoffset> = [#[5203 + #5220 * 20] + #5213 * #5210].
any help is appreciated

das habe ich gesehn. aber dann müsste ich wieder verkabelung und konfiguration ändern... das wollte ich eigentlich nicht. von daher suche ich ausschließlich eine 7i76E

You have not assigned a pin for the Z axis switch in the pinout page.

Es gibt keine im Deutchland
www.welectron.com/navi.php?qs=7i76
oder im Portugal
eusurplus.com/index.php?route=product/search&search=7i76
Aber die 7i96S mit ein 7i84 ist die selbe wie 7i76E
www.welectron.com/Mesa-Electronics-7i96S...thernet-Controller_1
www.welectron.com/Mesa-Electronics-7i84D...ard-Sinking-Output_1
etwa 10 tage
oder
eusurplus.com/index.php?route=product/pr...t_id=159&search=7i96
eusurplus.com/index.php?route=product/pr...t_id=104&search=7i84
beide im stock

Hi everyone,I used to work with linuxcnc 2.7.1 for some time on my self build 3-Axis mill. All axis have Ref-switches and everything worked fine, referencing and working.I got a new PC and wanted to upgrade to the newest linuxcnc. Installation went perfectly smooth and the system is incedibly fast and such.Stepconf however doesn't let me configure a Ref-switch for my Z-axis. X and Y - no problem, I can configure them as on my old system and both axis reference without any problem. On the setup page for the Z-axis however is everything around the ref switch greyed out, 
I attached 2 pictures. These configurations were standard from stepconf and even then the Z-axis is greyed out. Any Idea anyone?

Thanks,
Sebastian

Hallo, ich bin auf der suche nach einer Mesa 7i76E vielleicht hat hier noch jemand eine zum verkaufen.

Meine ist leider kaputt gegangen, wird zwar repariert soweit möglich aber eine 2. auf Ersatz wäre nicht schlecht.

 

Sample pic:

Thank you for the good OpenGL Tip

I did some research and now have two pieces of information.
When you mentioned OpenGL, a light bulb went off in my head.

First info, concern OpenGL:
When I had installed Linux Mint 20.3 on the current ASUSTeK Mini PC PN50-E1 (Barebone PC) and worked exclusively with Firefox and used the online CAD "ONSHAPE" very often, one day I received a message in FF that I could not use "ONSHAPE" due to the lack of an OpenGL driver.
I tried to adjust the settings in FF for OpenGL, but that didn't bring any improvement.
I then tried to 3D CAD drawing with "ONSHAPE" with other browsers like Brave, Opera and so on, but this was not possible due to OpenGL. I also researched in forums, but nobody really knew how to help. Since the PC had no problem with the Open Source 3D CAD FREECAD and other graphics programs, I decided to use this actual PC as a CNC PC.
I can imagine that OpenGL is a theme on this PC, but I don't know how to check it here in LinuxCNC. Or may it be that the PC is defective?
As far as I know the Radeon Graphics are integrated in the motherboard.

Second Info, concern UEFI/ASUS BIOS (Power saving):
I'm not sure anymore, but I think that in the beginning I had an ASUS BIOS with a more graphical interface where I could make more settings. Currently I have an AMI standard BIOS as seen earlier in this thread. I have searched all menuepoints in the BIOS for those menupoints you suggested.
I could try switching on or off here and there, but I'm not sure if the PC would still start. Above all, I do not understand the terms and do not know the possible effects.
I will list the menu below, perhaps you can tell me whether I should make a setting at a menu item? I think that the menuepoint "APM Configuration give that what we need? Of course I take responsibility as I need a solution for the PC.

Main
Advanced

• Trusted Computing
• GFX Configuration
• USB Configuration
• Netzwerk-Stack
• Onboard Gerätekonfiguration
  • Realtek LAN Controler
  • Wi-Fi Contoler
  • Onoard CIR
  • HDMI CEC Control
  • NVme Configuration
• APM Configuration
  • Restore AC Power Loss > is power off
  • ErP Ready > is enable S4 S5
  • Power on by PCI-E > disabled
  • Einschalten durch Ring > disabled
  • Power on by RTC > disabled
• Platform Configuration
• AMD CBS

Monitor
Boot
Tool
Exit

 

Ok here is a rough test. Put this qtdragon folder in your configfolder/qtvcp/screens/

There will be a new HAL pin 'qtdragon.mpg-in' connect that to an MPG S32 output pin.

Set the styleesheet for the _local_ 'qtdragon.qss' or ''brushed_metal_color.qss'
They have been modified a bit for some added hints.

Notice there is a new button near the AXIS buttons to select 'scrolling'

Now click on the gcode editor, gcode display, file managers, or override sliders.
Should get a colored border that moves to each selected (listed above) object.
If the scroll button is selected then moving the MPG will scroll/move the selected object.
In the gcode display you can select pan or rotate with the existing button.

Still rough but let me know what you think.
also interested in your opinion of the axis buttons menu buttons.
X  Y and user coordinates use the press and hold
Z use a little icon for the menu.

Chris

Slowly but steadily I'm wiring everything I need for the first test : limit switches and Y and X motors (the Z axes will be configured later with the THCAD wired in).

All the shield of the shielded cables that goes outside the box have a ground connection through the aviator connectors casing and the frame. There is room for a fifth axis If I want to add a tube cutting option later. There is 4 hole left on the left side for 2G aviator connector (emergency stop and the connection to THCAD-2 and Mesa 7i96s once I start to wire the plasma).

I feel a bit more confident now that I've started all the wiring about this THC thing.

Could someone confirm that I need :
- access to the arc voltage (which will be 1:1 ratio), to the THCAD-2 through a 2.5MOhm resistor on the negative wire
- a way to start and stop the plasma through a normal relay (via the Mesa 7i96s)
- an arcOk signal which I can access through a reed relay with the torch cable wraped three time around it (signal also read by the Mesa 7i96s) 

I'm still wondering about the Stamos or the Stahlwerk, maybe it could be worth it to try with the sthalwerk I already own now that I understand the electronic better...

I'm really enjoying this part, the machine starts to look like a real thing. I'm going slow because I'm always waiting for connectors or cable I forgot to order and I want to do it right from the begining because I know myself : if it works I will never go back to finish it cleanly.

Some pictures (if someone see a blattant mistake dont hesistate to tell me please ): 
 
 
 

Start a new topic with details about the hardware in use.

Hello friends, has anyone tried to connect the WHB02 remote to linuxcnc? I would like to connect it to a qtplasmac. Before buying, I decided to ask on the forum. Thanks.

Why not use an MDI_COMMAND:
forum.linuxcnc.org/38-general-linuxcnc-q...parallel-port#292850

Note: you can use any mdi command, it does not have to be an m-code. ie you could also define:
[HALUI]
MDI_COMMAND = G38.3 Z-20 F100


and then connect it to your button in hal:
net run-probe <= your_pin_here => halui.mdi-command-00

That would be the ideal solution, unfortunately it does not exist yet. That would need a modified interpreter which I have not looked at doing.
Alternatively, checking a gcode program at load time can be done by examining the line segments of the preview. That is what axis gui uses to check for limit violations on program load and I have modified that before.
The bigger challenge would be filtering the MDI command entry in the gui as you would have to examine that before it gets passed to the interpreter. Although being in python world it seems quite possible. In your case it should actually not be so difficult since you could simply reject arc moves instead of having to calculate way points to check if a G2 or G3 move would take the machine over a limit.

[edit]
Mind you once you start to introduce work and tool offsets things are going to get very complex very quickly.

As I stated previously, my knowledge of electronics is somewhat dated.

I thought if I connected the V- (48v PSU) and COM (5v/12v PSU) to earth, I was potentially creating a Ground Loop, which I understood was potentially harmful to electronics. But I do realize that this means I have a floating ground.

So, I tied V- and COM to earth. However, this did not resolve the issue I am having.

I did find that my spindle contactor was closed as soon as I powered the system, so I have something misconfigured there.