Advanced Search

Search Results (Searched for: )

  • karlhe
  • karlhe
24 Aug 2024 14:10
durchmesser stimmt nicht was created by karlhe

durchmesser stimmt nicht

Category: Other User Interfaces

Hallo liebe cnc Freunde,,

ich habe noch einmal versucht meine maschine mit ease probe  zu erstellen.

Die probe_tab  maschine läuft, alle Achsen fahren, cnc programme  sind ausführbar.
Die easy probe panels sind sichtbar. Die Buttons lassen sich drücken, es passiert aber nichts.
Ich habe alles mögliche probiert, finde keine Lösung.

Viele Grüße karlhe


 
  • itsemast
  • itsemast
24 Aug 2024 13:52
Replied by itsemast on topic Remora for RP2040

Remora for RP2040

Category: Computers and Hardware

I have found an example of communication between RPi5 (RP1) and RP2040 over SPI:  rpi5-rp1-spi . Perhaps it can be useful?
  • Lcvette
  • Lcvette's Avatar
24 Aug 2024 13:49
Replied by Lcvette on topic Trajectory Planner using Ruckig Lib

Trajectory Planner using Ruckig Lib

Category: General LinuxCNC Questions

i Lcvette,

Yes, will check the mm to inches.

To test the scurve motion planner in linuxcnc i added a new repository, based on lcnc stable version 2.9.3.
Inside the repository we have the cmake framework to build one the current motion planner  "tpmod" and 
two a motion planner called "tpmod_scurve".
Conclusion: very compact code enviroment to test scurve motion planner.

Now to make the new motion planner work in linuxcnc, we have to add some logic because the new planner works a little
different then the current motion planner.

Main differences :
1. New motion planner loads gcode itself. Old motion planner, recieves gcode in chunks over the servo cycle.
2. New motion planner calculates "look ahead" before gcode execution, Old motion planner does this at runtime.

Possible difficulties:
1. New motion planner loads gcode itself, this can take a few seconds for big files. This could result in creating a multi-threading process.
2. The clothoid & spline fillets are not shown by lcnc gremlin on forehand. Validation and debugging is more difficult.

Next week i will add the code to make this work.

awesome!!  just let me know if you need anything from me, im willing to test things is need be on my end!  we are using VTK for the QtPyVCP gui backplotter so if you need any testing with that as well or way to figure how to draw updated plots we could have a look at that.  although i assume you are trying to solve how to feed the planners modifie gcode out instead of the file gcode.

thanks again for such awesome work Grotius!!
  • Aciera
  • Aciera's Avatar
24 Aug 2024 13:45 - 24 Aug 2024 17:31
Replied by Aciera on topic Python/NC routine just stops executing

Python/NC routine just stops executing

Category: Installing LinuxCNC

Not sure if this is the root of your problem but it's certainly possible.
The problem with '.wait_complete()' is that it does not work the way many of us think it does. It's not as simple as just slapping it in after an '.mdi()' because it's purpose is not to actually ensure that the command has been executed. Also many are not aware that it works with a timeout that has a built in default value of 5 seconds.
 
linuxcnc.org/docs/stable/html/config/pyt...inuxcnc_command_code

So '.wait_complete()' actually returns a value (-1 if timed out, RCS_DONE if the command has been executed successfully or RCS_ERROR if not).

If you now look at this snippet in your code as an example:
            sCommand.mode(linuxcnc.MODE_MDI)
            sCommand.wait_complete()
            sCommand.mdi("o<vacuum> call")
            sCommand.wait_complete()
            sCommand.mode(saveMode)
            print("vacuumTable finished")

It becomes clear that whenever you are calling '.wait_complete()' you are really not doing much at all because no matter the return value you just continue anyway and if the MDI command takes more then 5 seconds your code also just carries on and changes the mode. So if '.wait_complete()' is not used to actually receive its return value and make decisions upon that value it's basically nothing more than a timer with the benefit of allowing code execution to go on before the timeout occurs if the mdi command either executed successfully (RCS_DONE) or failed (RCS_ERROR).

Have a look at this example from '/lib/python/qtvcp/qt_action.py':

 

[edit]
In your case it may be as simple as extending the timeout of the second '.wait_complete()' to say 200s, depending on how long 'vacuum.ngc' takes to complete as it clearly does not seem to be as simple a task as switching on a vac:
            sCommand.mode(linuxcnc.MODE_MDI)
            sCommand.wait_complete()
            sCommand.mdi("o<vacuum> call")
            sCommand.wait_complete(200)
            sCommand.mode(saveMode)
            print("vacuumTable finished")
  • Ismacr63
  • Ismacr63
24 Aug 2024 13:44

probe basic problem with manual tool change and 3d touch probe

Category: QtPyVCP

The subroutines folder is in place, but your message made me think that possibly the path in the ini file contains some error.

After checking, I saw that I missed 2 errors in the file path. Now it works fine.

Let's see what the next problem is...

Thank you.
  • dabiaoge6699
  • dabiaoge6699
24 Aug 2024 13:13
EtherCAT IO设置 was created by dabiaoge6699

EtherCAT IO设置

Category: EtherCAT

 

File Attachment:

File Name: ethercat-c...24-6.xml
File Size:3 KB
Hello, I have a parallel port Macro3 card and I would like to expand my IO. I have an EtherCAT IO with 16 inputs and 16 outputs, and my XML file is ready. Can you tell me how to make my program use HAL files and how to write them
  • Kirvesmies
  • Kirvesmies
24 Aug 2024 11:20
Replied by Kirvesmies on topic Lathe turret tool changer

Lathe turret tool changer

Category: Advanced Configuration

Hey Erik, any progress?
I'm currently retrofitting the same model and thought I might ask you first before reinventing the wheel. It would be really nice to get automatic homing, as well as reverse jogging for slightly faster tool changes. Your machine does have the retractable pawl that allows reversing the turret, right?

Perhaps even better than a homing cycle would be to read the turret position on M6 instead of asking linuxcnc for the current tool number (and if for whatever reason the turret is not aligned, reverse until it is) and then proceed to the rest of the tool change routine.
  • Moutomation
  • Moutomation
24 Aug 2024 09:59
Replied by Moutomation on topic Computer Shutdown

Computer Shutdown

Category: General LinuxCNC Questions

Hello,
I use gmoccapy. When I turn on the machine, the computer starts first, then gmoccapy. How can I shut down Linuxcnc first and then the computer when I press an external key?
Can I do this with a button on the machine?
  • rodw
  • rodw's Avatar
24 Aug 2024 09:50
Replied by rodw on topic The blacksmith's plasma table

The blacksmith's plasma table

Category: Plasma & Laser

Its getting exciting for you.
 2 M Ohm resistor will give you a full scale  reading of 210 volts. (per the THCAD manual p 6)
The Thcad full scale is 10 volts so you have a 21:1 divider.
  • Moutomation
  • Moutomation
24 Aug 2024 09:29
Replied by Moutomation on topic İnstall glade

İnstall glade

Category: Gmoccapy

wonderfull thanks a lot
  • Aciera
  • Aciera's Avatar
24 Aug 2024 09:06
Replied by Aciera on topic İnstall glade

İnstall glade

Category: Gmoccapy

Actually there is a much easier way to do this as GladeVCP has a built in module for saving panel state on shutdown:
www.linuxcnc.org/docs/html/gui/gladevcp....on_gladevcp_shutdown

To try this you need to:
1. Delete 'gladevcp-handler.py' in your 'python' folder (since you seem to have more than one panel it makes more sense to name the handler file like the panel it serves)

2. Save this as 'testpanel-handler.py':
#!/usr/bin/env python3

import hal
from gladevcp.persistence import IniFile,widget_defaults,set_debug,select_widgets

debug = 0

class HandlerClass:

    def on_destroy(self,obj,data=None):
        # note: save_state(<object to fetch attributes from>) only:
        self.ini.save_state(self)

    def __init__(self, halcomp,builder,useropts):
        self.halcomp = halcomp
        self.builder = builder

        self.ini_filename = __name__ + '.ini'
        self.defaults = {  IniFile.vars: dict(),
                           IniFile.widgets : widget_defaults(select_widgets(self.builder.get_objects(), hal_only=False,output_only = True))
                        }
        # note extra self.builder parameter
        self.ini = IniFile(self.ini_filename,self.defaults,self.builder)
        # note - only the object which gets attributes set is passed:
        self.ini.restore_state(self)


def get_handlers(halcomp,builder,useropts):
    global debug
    for cmd in useropts:
        exec(cmd, globals())

    # get some detail what save/restore etc are doing
    set_debug(debug)

    return [HandlerClass(halcomp,builder,useropts)]
 
2. Update the tab command In the [DISPLAY] section of your ini to this:
EMBED_TAB_COMMAND= halcmd loadusr -Wn testpanel gladevcp -c testpanel -u python/testpanel-handler.py -H ./gladevcp/testpanel.hal -x {XID} ./gladevcp/testpanel.ui

3. Open 'testpanel.ui' in glade and select the 'hal_spinbutton1' widget
 a) Remove the handler from 'GtkSpinButton.value-changed' signal (that is the one we added last time):
 

 b) Add 'on_destroy' as handler for the 'GtkWidget.destroy' signal :
 

That should be all.
Note:
- The 'on_destroy' handler only needs to be added to a single widget in the panel, does not matter which one as they all get destroyed when the GUI is closed.
- This will save/restore the state of the whole panel
- The data is stored in a file named 'testpanel-handler.ini'
- If you have more than one custom panel you can copy this handler file for each of them and replace 'testpanel' in the filename and the 'EMBED_TAB_COMMAND' with the name of the panel.
 
  • polskleforgeron
  • polskleforgeron
24 Aug 2024 08:58 - 24 Aug 2024 09:01
Replied by polskleforgeron on topic The blacksmith's plasma table

The blacksmith's plasma table

Category: Plasma & Laser

Hi everyone, and hi @tommylight ! I'm here for an update after a while using the table.
I'm very glad I built this machine, it saves me a ton of time. It already paid for itself as I had an order of 50m of guardrail with a lot of sheet metal. It would have drove me crazy cutting it with the grinder.

I did some changes though. Upgraded the X axis motor from a nema 17 (65Ncm) to a nema 23 (1.26Nm) as it was sometimes missing steps due to a lack of torque. I also removed all the cable to the limit switches (exept the float ofc) as there where not really necessary and added a lot of cable which could get stuck during movement. I can easily put them back if needed though.

I'm really impressed on how clean it cuts thin sheet metal when you got the setting right, even with my cheap chinese plasma cutter. I have almost no post grinding to do and the slag just go away easily with a scrapper. I feel, again, I'm saving so much time and health using less the grinder.

I have a bit of time ahead of me so I started to set up the THC (I wasn't using it until today). Of course i doesnt work and I have no idea why.

First I'm not sure what I should enter when asked for the voltage divider. I'm using a THCAD-2 with two 1MO resistor on both + and - cable. I've entered THCAD-2 with W1 UP when asked during the configuration. By default there is a 20 ratio voltage divider. I would say I have no voltage divider and should enter 1 but I'm not so sure...

Anyway, I'm pretty sure it isn't what makes it not work. When cutting, even though I have enabled the THC (both in QTplasmaC and in sheetcam) the "active" indicator on QTplasmaC never turn on. I'm not sure where to start to know what's wrong (the physical led on the THCAD-2 board is turned on though).

I'd like to again thank the linuxCNC community for helping me to build this plasma cutter. It tremendously help my small buisness to be profitable.
  • MarkoPolo
  • MarkoPolo
24 Aug 2024 08:11
Replied by MarkoPolo on topic QtDragon, 2 modifications

QtDragon, 2 modifications

Category: Qtvcp

I'm trying to change the names of the buttons "action_spindle_rev" and "action_spindle_fwd" in the style sheet. But the text change function only works on two buttons "action_mist" and "action_flood"
What is the way to make it work on the other buttons?
Displaying 22126 - 22140 out of 25290 results.
Time to create page: 0.621 seconds
Powered by Kunena Forum