Advanced Search

Hmm. it does seem i want the 7i84. ill have to figure out where it is.

Start LinuxCNC from a terminal window and the error messages will be displayed there.

Firstly, let me say, thanks for the help so far. You are a star. On Xmas and Boxing Day. Thank you. I know I'm a bit obsessive, but don't expect it from others, so know that ti was appreciated.

So I decided to do a new build based on what I have learnt to date, and I realised during that process that I had made an error in where I got the core files from. I am not a muppet often, but this was good example. I incorrectly used the files from the Probe_Basic directory. So I did a rebuild using the correct files from the Machine_setup_files.

And guess what??? It worked. So forgetting the chair-keyboard interface issue, the instructions are solid with some caveats.

So here is some feedback from me on the setup instructions to help with the documentation for the muppets out there who may not have experience in Linux etc...

a) You need to instruct to delete the comments from the replaced lines. This is for non-linux people.
b) I would recommend commenting out the existing items from the hal and ini files and made comments about the replacement items. My understanding this is good Coding 101. And should help anyone reverse engineer the problems.
c) I have MESA cards, and found that the setup of these was best achieved using the MESACT configurator and not the pncconf. NOTE: pncconf taught me a lot about the different aspects of the configuration items, however, MESACT was better for me for a holistic setup for MESA cards IMHO. It allows you to select all of the cards manually and then verify them.

Separately I noted that when I did the configuration this way, I did NOT need to add the GEOMETRY statement. It was not there initially, and not in your files for transfer, and it started ok, no errors. I still need to do some more testing, however, looks better from atm.

So where are we at:

I could start, no errors. Was able to Jog per my setup and return to home easily. The Switch gear seems to work, and I need to sort out how the Axis limits work when I get this onto a machine. I am bench testing atm.

So we are off to a good start.

Because I am completely new to this sort of thing... CNC setups etc.. and CNC machining... What would be a good reference for learning about how to set up a machine, XYZ coordinates, tool offsets, etc.. that would apply to the Probe Basic layouts. This would include how to start off a simple Conversation job.

Thanks again.

So, what's an easy way to add IO to my 7i96s?

ATC, probe, laser tool setter etc are gonna need a dozen or so more IO than I have.

I can piggyback the 7i77, but I kinda want to leave that for use on the larger machine. I did have a 7i84(?) but it seems to have gotten lost or packed away when I moved from the shop and I can't find it.

Is there an alternate simple cheap option?

Thankyou so far for the help PCW
but unfortunetly no luck with the coding side of things

managed to eventually sucessfully flash the mesa board with the 7i96s_2pwmd.bin after a few complications of mesaflash not being able to detect my board.

but afterwards all seemed to operate my existing cnc with no issues,

however as soon as i tried to update any of the hal or ini for the laser, linuxcnc failed to boot giving me the debug prompt.

is there any way to determine from the debug prompt message it provides what it doesnt like??

have provided my current working hal and ini, does not have any of the new additonal code that id need to run laser off spindle

Hi Aciera,
Thank you for reply.

Update......
Now I delete  " ; "    and try  again.
result is  no error about   " ; "
but error   "syntax error in VERSION script"

Thank you,
Asis

 

Currently running Ubuntu 10.04 and Axis 2.5.4 with the RTAI kernel on a P4 3GHz with 2 G RAM going out to a G540 controller with close to 1000 programs ran.
Latency: Servo 7k (ns) Base 22k (ns) running glxears and accessing directories, etc.
Tried the latest ISO for 2.9.3 RT-Preempt kernel live from an almost-full flash drive
Latency: Servo 77k to 90k(ns) Base 72k (ns) running glxears and accessing directories, etc

Computer is currently standalone, no web surfing or networking. Currently it is partitioned for Ubuntu and an old Windows install.

Wondering if there is hope with this PC or if I am better off getting something else. And if get something else, what? I am not so PC and Linux savvy.

Refurbished i5 desktops start around 130$ in my market Dec 2024  but would need a card for the parallel port.

I saw on another thread where a solution was to load a Wheezy ISO which gets one up to 2.7.X LinuxCNC IIRC (yes?)

Thanks, I appreciated the input.





 

Hello, thank you very much and a very Merry Christmas!...
Since I would like to see your project, maybe share it on your YouTube channel, I want to learn and I was really happy with the news that I could use Ubuntu to work seriously.
Thanks a lot!...

Hello, thank you very much and a very Merry Christmas!...
It doesn't have that port, what board do you recommend for this little one?
Thanks a lot!...

I did some more testing and milling and everything seems to work for me know. There are some differences to your setup: this is how I measure the tool 

    #<touch_result> = #5063
    #<setterheight> = #<_hal[qtversaprobe.probeheight]>
    #<blockheight> = #<_hal[qtversaprobe.blockheight]>
    (print, #<touch_result>  #<setterheight>  #<blockheight>)
    ;(DEBUG, %fTouch Result: #<touch_result>)
    ;(DEBUG, %fProbe Height: #<_hal[qtversaprobe.probeheight]>)
    ;(DEBUG, %fBlock Height: #<_hal[qtversaprobe.blockheight]>)
    ;(DEBUG, %fnewtool: [#<touch_result> - #<_hal[qtversaprobe.probeheight]> + #<_hal[qtversaprobe.blockheight]>])

    G10 L1 P#<newtool> Z[#<touch_result> - #<_hal[qtversaprobe.probeheight]> + #<_hal[qtversaprobe.blockheight]>]
    G43

Whole file can be found here . Main remap is base on user Guihue and versaprobe macros for axis  adopted to my needs in qtdragon. 
github.com/zieluch22/sorotec_cl0604/blob...cros/rack_change.ngc 
From ini check section 
[RS274NGC]
#PSNG parapeters
RETAIN_G43 = 0
INI_VARS = 1
HAL_PIN_VARS = 1
SUBROUTINE_PATH = macros 
RS274NGC_STARTUP_CODE = G17 G21 G40 G43H0 G54 G64P0.0127 G80 G90 G94 G97 M5 M9
and I am using python3. 
whole file 
github.com/zieluch22/sorotec_cl0604/blob...d_sorotec_cl0604.ini 

hope you can find something and you can enjoy the software.

beauxnez wrote:

hello
i have an nvem card based on rt1052 but i can't flash it with st link, the card is not detected, i tried with a card with a stm32f401 and it is detected?
 

Hello beauxnez,
First and foremost, you should be able to see the ST-Link as a probe using PyOCD. I would suggest enabling the Windows default Administrator account and trying it from there. In my case, I couldn't get PyOCD to detect either the ST-Link or CMSIS-DAP even when running the terminal as an Administrator!

So, I'd recommend giving the Administrator account a shot. If the "pyocd list" successfully recognizes the ST-Link probe, let me know and we can proceed from there.

Good luck!

Hi,

I've been spending the last couple of days trying to figure out how to make the "software estop" work together with my safety relay. But i'm going in circles and i need a kick from someone, maybe you?

First off, i have this physical circuit to handle the emergency stop logic in hardware:
 
...the idea is that estop should work without any software involvement. And everything should be as redundant as could be. I have dual (safety) contactors(KM1 + KM2) that cuts power to all drives and at the same time prevents resetting the estop-circuit in cause of failure. I have a proper estop-button(it's redundant contacts, but only shown as one here in S5). On top of that i have added an inline relay, K13, which can be triggered by software, aswell as the wire "1" which goes to an input in LinuxCNC in order to tell it the state of the safety relay. There is a short delay(~0,5sec) between the two sets of relays in the safety relay, so ideally the signal to LinuxCNC should be able to tell the servos to emergency stop just before the power is killed. 

So far, so good. Everything works just like i want it. The latching works excellent and the signals to and from LinuxCNC also works as expected....

However, i'm totally going in circles when i try to add an estop latch inside LinuxCNC to work in conjunction with the hardware safety relay. I took inspiration from a thread from the user Unlogic  who seem to have it working. But i end up having a latch #1 that depends on latch #2 that depends on latch #1 again....ehh... so currently i'm just having the inputs tied into LinuxCNC like this:
..this "sorta works" and prevents anything powering on before LinuxCNC has booted properly. However the UI experience is kinda bad as i have to press a button extra and there is not really any feedback to the user

SO, the question: Has anyone got a combination of a physical safetyrelay and an estop latch to work "like it should"? I'd be very interested in seeing how others have solved this issue...

/Thomas

1. Convert an ST-Link to a CMSIS-DAP probe by using a a second ST-Link and the ST-Link utility to flash the CMSIS-DAP firmware.

mvdlande.wordpress.com/2015/10/05/cmsis-...ink-v2-mini-adapter/

2. Use pyOCD with the newly flashed CMSIS-DAP probe to flash the firmware to the controller board

python -m pip install -U pyocd
pyocd flash .\remora-rt1052-3.1.3.bin --target mimxrt1050_quadspi

github.com/scottalford75/Remora-RT1052-c...ora-rt1052-3.1.3.bin

Hello,
I am converting a Biesse Rover 13s over to LinxCNC and am testing the remap functions with Python and the commands take about 5 seconds to process each one. It's nearly instantaneous from MDI and I don't see any errors in the terminal output when the python command runs. It also works just fine when I reference a straight ,ngc file with REMAP=M201 modalgroup=10 ngc=m201.

Any ideas as to why Python is so slow? I can use the direct ngc remaps but would like to experiment with python also.

Terminal output when running Python
is_callable(oword.remap_m201) = FALSE
Executing remap_m201: Loading m201...
Wait 10 seconds
m201 executed successfully.
task: main loop took 65.045437 seconds

toplevel.py
import sys
import remap

My INI file
[RS274NGC]
PARAMETER_FILE = linuxcnc.var
USER_M_PATH = ngc
SUBROUTINE_PATH = ngc
#RS274NGC_STARTUP_CODE = G21 G40 G90 G94 G97 G64 P0.025
#REMAP=M201 modalgroup=10 ngc=m201
REMAP=M201 modalgroup=10 python=remap_m201
#ENABLE_EMBEDDED_PYTHON=1
DEBUG = 5

[PYTHON]
TOPLEVEL=/home/wrhammer/linuxcnc/configs/Rover13s/python/toplevel.py
#PATH_PREPEND=/home/wrhammer/linuxcnc/configs/Rover13s                                   
PATH_APPEND=/home/wrhammer/linuxcnc/configs/Rover13s/python/     
LOG_LEVEL=10


Python Test Scipt:
def remap_m201(prolog, params=None):
    """
    Python-based remap for M201 to manually load and execute m201.ngc.
    """
    print("Executing remap_m201: Loading m201...")

    import linuxcnc
    cmd = linuxcnc.command()

    try:
        cmd.mdi("M64 P0")
        cmd.wait_complete()
        cmd.mdi("M64 P1")
        cmd.wait_complete()
        cmd.mdi("M64 P2")
        cmd.wait_complete()
        print("Wait 10 seconds")
        cmd.mdi("G4 P10")
        cmd.wait_complete()    
        cmd.mdi("M65 P0")
        cmd.wait_complete()  
        cmd.mdi("M65 P1")
        cmd.wait_complete()  
        cmd.mdi("M65 P2")
        print("m201 executed successfully.")

    except Exception as e:
        print(f"Error in remap_m201: {e}")

    return

There is a problem with linebreaks in the code above from pasting. I'll post the file tomorrow. Or you can fix it in a text editor in the mean time.