Advanced Search

Does anybody have a working set of configuration files for a Lichuan LC10E system with homing in the drive? I have been trying unsuccessfully for several days to get either RodW's or Marco's homing configs to run. I *know* that neither of these can successfully do in-drive homing without modification because neither ever sets the 0x6098 homing mode register, or the homing velocity and acceleration registers. They also never put the drive into operating mode 6 (homing). I added the extra registers in the xml file and eventually got the drive to go into mode 6, but the motor would not turn. Also, I found that jogging with these modified config files would result in a runaway motor after a small motion. I haven't figured out what in the comp file is causing that.

So if some one out there has blazed this trail before me, I would love to see your xml, comp, hal, and ini files. I've attached my current snapshot, which still does not do homing, and has this mysterious runaway jogging problem.

Thanks,
-- Ralph

The "unknown gtag" error means that your mesaflash is not up to date enough
to know about the periodm. This has no real significance.

To list all mesa hardware pins/parameters, with LinuxCNC running, in a terminal, type:

halcmd show all hm2

you can re-direct this to a file with:

halcmd show all hm2 > all-mesa.txt

if you just want periodm pins:

halcmd show all | grep periodm

Hi Ikavan,

looking into the .tlc files is certainly not the way to go.
You can look at the halcmd source. Halcmd is a program that can make a list of components, pins, params etc.

To build halcmd you can look at repositories on github.  github.com/grotius-cnc/linuxcnc/tree/master/cmake
Then from there you can create a qt app.
 

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.