Advanced Search

Most of the hobby machine-builder (*myselfincluded) hardly put effort in selecting the correct wiring for the job!! /lazy. And a lot of us can't differentiate between power-vs-signal wire, mΩ/m a.k.a. voltage drop, let alone using the correct gauge-vs-freq if they do. Shielding and wiring arrangement requirements comes last, imho.

Great vid regardless. Watched it all, relaxing! I like the guy and will bookmark his website/store.

Sorry..I meant the Mesa configuration tool...pncconfig works...the problem is that I nee new firmware for more axis through 7i96s and thought I needed Mesa Configuration tool to do this...is that wrong?...

Thanks

Thanks - I have it working using pyvcp, I connected the pin to both the LED and joystick in the postgui file.

Not clear what you mean when you say the configuration
tool does not work.  What happens if you launch pncconf
from a terminal window by typing:

pncconf

 (return)
 

DPFlex wrote:

Hello Todd,
I understand that you make example of "incremental encoder" with quadrature.
My encoder is 17 bit absolute multi-turn type, so the counts for one turn is huge value 131072.
I calculate: 131072*80/360 = 29127.111111. Is it still correct to apply ?.

I put ENCODER_SCALE = 29127.111111 to INI file, but nothing happen.
I understand need to revise HAL file to use ENCODER_SCALE, but it seem encoder component is only suitable to incremental encoder type.
linuxcnc.org/docs/devel/html/man/man9/encoder.9.html

Please advise Thank you.
 

This is a little bit of late reply, the encoder component documentation you referenced is a software encoder counting component applicable for reading an encoder via gpio such as through a parallel port. This would not be applicable to your situation with Ether CAT. But it sounds like you are on the right track now.
(I have no experience with Ether CAT.)

For positioning, I normally use a grid widget to give the rough position to an item within the main window. Then within its box, you can tell it to center, or be to the top,bottom, left or right.

When you try to connect glade halpin to a signal, you must do it in a hal file that is loaded after the gui is started (aka the post-gui-hal file.) If you try to use the pin name in one of your regular hal files that are loaded before the gui is functioning, you will get a hal pin not found error and Linuxcnc will close without opening.

Hi...seem to be stuck here...I can not get configuration tool to work..installed from usb debian 12 bookwork...could not get mirror so continued without..from there downloaded configuration tool..could not get to install...not sure why this is not easy but whatever......I am very new to linux...how can I update the firmware and use discover option..by other means..or do I need to resolve installation issues first?

Thanks,

Rick

Kernel 5.4 is not that new, there have been some issues with Ryzen CPUs. So if Tommylight's solution doesn't work you could try this rt kernel 6.10

drive.google.com/drive/folders/1L28lG0zD...2XQJx?usp=drive_link

No, you should just leave the Kins setting as Trivkins. As Rod was trying to say, the Trivkins machine model was modified to handle slaved joint gantries in version 2.8, as well as handle arbitrary joint to axis assignments. There is no need to to try to use another kins model.

Now a history lesson. (Stop reading if you don't care.) Previous to v2.8 the Trivkins machine model was truly simple. Just assigning each joint 0-8 to each axis x,y,z,a,b,c,u,v,w respectively. Such that if you needed a config that used axis X,Y,Z, and W. you had to set up and configure dummy joints and axis for the unused A,B,C,U,V axis. You could hide the unused axis in the user interface configuration so they were not seen, but they were still there under the skin. There was also no means for attaching multiple joints to an axis or to square a gantry. That necessitated the gantry kins config, it was a bit of a kludge and caused some minor confusion of joints and axis within Linuxcnc most noticeable with some user interfaces. With the merger of the Joints/Axis development branch into 2.8 (while 2.8 was in development as Master) the last version Gangrykins eventually became/was developed into the current version of Trivkins. Previous to Joints/Axis, the defining/separation of a joint and an axis, was not always clear or separated in the Linuxcnc code. This wasn't a big deal for trivial machines or even much of a problem for a gantry, but it could complicate setting up and running non trivial machines where the movement of a joint did not identically match the movement of an axis. Hence the push to clearly separate in the Linuxcnc codebase the difference between a joint and an axis.

Thank you, thats what I was looking
will start from here and update if succeded/failed )

Sami wrote:

"""
Remove the lathe power plug, try again.
"""
We have started linuxcnc without lathe hw plugged in and it start until error of
missing I/O-information about door etc. When lathe hw is connected to 6i25 pc reboot
at line addf hm2_5i25.0.read servo-thread.

 

That points to a bad wiring issue with outputs or inputs, or power issues, or different potential between Mesa/lathe electronic/drives/spindle drive.
Remove all the input and output plugs from the Mesa 7i77, power on everything and start LinuxCNC.
If that works, power off the machine, plug one of the connectors, turn on the machine, test connectors one by one.
When you find a connector that causes issues, start removing wires from it and test.
Do not remove wires or plugs while the machine is on.

I used this:

#vacuum cleaner delay
addf vacuumOr2 servo-thread

addf toolchangeXor2 servo-thread

loadrt timedelay names=timeDelayVacuum
addf timeDelayVacuum servo-thread

setp timeDelayVacuum.on-delay  0 
setp timeDelayVacuum.off-delay 4


net spindle-on spindle.0.on => vfd.spindle-on


net spindle-on vacuumOr2.in0
net coolant-flood  vacuumOr2.in1
net vacuum vacuumOr2.out 
#net vacuum timeDelayVacuum.in

#net in-toolchange iocontrol.0.tool-change #in toolchange

net vacuum        toolchangeXor2.in0
net in-toolchange toolchangeXor2.in1
net toolchanging  toolchangeXor2.out
net toolchanging  timeDelayVacuum.in

net delay_sig timeDelayVacuum.out  [HMOT](CARD0).ssr.00.out-05

But watching in Halshow the iocontrol.0.tool-change never changes. Will try your suggestion tomorrow, I did come across that motion-type but for some reason I didn´t want to use it.
Thanks!

""""""
-Check if the ram memory is detected correct in the bios.
-Replace ram memory, check cpu temperature (old thermal paste?)
-Another/Newer kernel
-maybe it's just a defect in the mb or cpu
""""""
Ram is detected ok in the bios and we had three different mb where reboot issue
is present, when zen 3 Ryzen prosessor is installed (Ryzen 5 5600G or Ryzen 7 5700X).

We have been also tested with latest release of linuxcnc (2.9.2 and 2.9.3) with
rt-kernel and realtime kernel (5.4.258).


"""
Remove the lathe power plug, try again.
"""
We have started linuxcnc without lathe hw plugged in and it start until error of
missing I/O-information about door etc. When lathe hw is connected to 6i25 pc reboot
at line addf hm2_5i25.0.read servo-thread.

When we comment that line out, we can start linuxcnc, but all is not working ok
(we can see I/O information etc, but could not start machining).


"""
My understanding is that your computer reboots only when you run Linuxcnc?
You could install the latest Linuxcnc and test your lathe  with your current setup files (ini, hal, ui …)
"""
We have tested latest versions and still have reboot issue with zen 3 prosessor. Latest versions
works ok with older pc hw and we can machining with setup from old pc (ini, hal etc.).

We also tested old hdd (old linuxcnc and ubuntu) with new pc hw (zen 3) and have this same reboot
issue with it. Old hdd with old linuxcnc&ubuntu works ok when Ryzen 5 1600 or older cpu is in use.

Otherwise all tested pc works ok and those tested pc's have been used several months in other use
without issues.
 

Forgot:
to access the values in Gcode (eg the value 9.2 above) you can use:
Important notice:
I strongly recommend to use a quebuster command like 'M66 E0 L0' right before reading a hal pin in Gcode otherwise the readahead may read the pin much before code execution gets to that line.

my1987toyota wrote:

Something to note if a cable is to be continuously flexed a braided shield is better suited for things like drag chain
cable carriers at least in the long run and industrial settings where the machine maybe operating 24/7 365 for
years on end.
 

Even better, get drag chain rated cable. Thats what I have used for the last couple of projects and its not very expensive. The 4 core stuff I use has a plastic sheath around the wires, then the braided shield and then an outer plastic sheath, It was called ÖLFLEX CLASSIC 400 CP and like everything of quality in Australia, I had to wait for it to arrive from Germany