Advanced Search

Many thanks for the quick support.now it works.
I found time today to compile and install Linuxcnc 2.9.3.
After the git clone ... I searched the linxcnc-dev directory for scara and edited all files where
d1-d6 were defined with my values.
In some places the build and installation was a bit stuck, then I asked Windows-copilot and it went on.
For those who have similar plans, I have entered my terms:

For build:
git clone --branch v2.9.3 github.com/LinuxCNC/linuxcnc.git linuxcnc-dev

cd linuxcnc-dev
sudo apt-get build-dep linuxcnc
sudo apt-get install build-essential

root@cnc:/home/cnc/linuxcnc-dev/debian#
root@cnc:/home/cnc/linuxcnc-dev/debian# ./configure
successfully configured for 'uspace-Debian-12'..

sudo apt-get install libgpiod-dev xvfb

dpkg-buildpackage -b -uc

For install:

sudo apt-get install iptables mesa-utils python3-numpy python3-opengl python3-configobj libgtksourceview-3.0-dev tclreadline python3-pyqt5 python3-pyqt5.qsci python3-pyqt5.qtsvg python3-pyqt5.qtopengl python3-opencv python3-espeak python3-dbus.mainloop.pyqt5 python3-pyqt5.qtwebengine python3-pyqt5.qtwebkit espeak-ng pyqt5-dev-tools gstreamer1.0-tools espeak python3-poppler-qt5 python3-serial
sudo apt --fix-broken install
sudo dpkg -i *.deb

Hi, 

I have made some progress and have successfully connected a python script to my machine.  This script right now is just turning a LED on and off but I will use it in the future to run my PID loop on my feedrate.  

I have run into a problem though.  I am trying to get the PWM signal into my software using hal, but when I used mesaflash --read I am getting the name on pin 29 (this is the pin that is supposed to read the PWM signal according to Peter) of (unknown-gtag-200).  

It seems like this error means that the name is not set correctly, but that it might still be possible to read the pin.  However, I do not know how to find the hal name of this pin.  I was only able to find the hal name of the ssr pin because of you PCW.  I feel like there should be a list somewhere that gives the hal names and associated physical pin numbers...

I would greatly appreciate any guidance. Thank you.

Best,
-Dylan

No problem at all! Just wanted to make sure. Thank you!

Hi,

I have version V2.10.1 here.
The tp.c file is last modified :17-05-2024 19:40

 

Thanks, that was helpful. I am still not used to the coordinate system but the locations are now ok and it starts without errors but when I run M6 it goes to the tool change position but stops there with no prompts like there are in the demo.
I think manualtoolchange.glade isn't being used 

thanks
Luke

Yes, we have started to periodically remove dormant users. In most cases this is in no way a 'punitive' measure but became necessary because our database had grown to almost 25'000 users with more than half of them dormant or simply spam accounts.
Thank you.

Grotius wrote:

Snowgoeroe,

For my clarity.
You want pathpilot planner running in lcnc?

 

I think it might make the most sense to just port the >3 axis look ahead and blending over to the master LCNC branch.

I am not sure how their TP differs from ours otherwise, but I do know that theirs is pretty well tested and stable at this point.

Hello! I just re-signed up with the same email address and user name as previously. I was just wondering if users are removed periodically (I hadn't logged in for quite some time) or if there was some other reason my user was removed?

I just want to make sure I avoid whatever I did to make it happen so it doesn't happen again!

Thank you!
Evan

The Mesa hardware just doesn’t know about gcode. The computer interprets the gcode into step and direction timings and that is sent to the Mesa hardware. As for encoders, it does the counting and sends this information back to the computer. Any “closing of loops” is done by linuxcnc.

Whilst the Mesa hardware is quite complex (firmware wise) it requires a computer running Linuxcnc to instruct as to what to do.

Scott, thank you very much for pointing me in the right direction. I made changes to the configuration file "ec500-rt1052-DMA.txt" (JSON) according to your guidelines. I modified the parameters: "Step Length": 10, "Step Space": 5, but for now, I’m applying it only to one axis, X - JOINT_0, for testing purposes. I’m glad you helped me. Of course, in the *.ini file, I adjusted the SCALE parameter to match the settings from the HBS86H (microsteps) and to ensure movements are adapted to the lead of the ball screw. For now, everything is set up on the floor at home. In the future, I plan to install the Remora system on my new CNC machine, which I’ve been building for a long time (mainly because it’s very heavy, as it’s supposed to be, and requires a lot of work). I want it to be faster in its movements than my current one, which operates on a parallel port. If I have any questions, I’ll definitely ask you or others on the forum. It’s great that you’re all here and creating such amazing things. Take care for now.   Christopher - tu_koper.