Advanced Search

Search by Keyword Keywords:

Search Options

Find Posts from

Sort Results by

Search at a specific date

Jump to Result Number

Search in Categories Also search in sub-categories

Search Results (Searched for: )

tommylight

16 Apr 2025 09:02

Replied by tommylight on topic Custom interface board questions

Custom interface board questions

Category: General LinuxCNC Questions

ajar171 wrote:
Now to my questions:
- encoder scaling: where is it applied with a Mesa board? In the FPGA (did not find anything in the VHDL) or the hostmot2 driver or in LinuxCNC main software?
- motor acceleration and max speed: the same question

In LinuxCNC, in the ini file.

Grotius

16 Apr 2025 08:02

Replied by Grotius on topic LinuxCNC S-Curve Accelerations

LinuxCNC S-Curve Accelerations

Category: General LinuxCNC Questions

Hi,

Before starting to change kernels etc. I thought maybe first do the latency-histogram test.
I did this on 2 different pc's.

From what i read here : max us > 100 = is bad.
Is this value both the same for base- & servo-thread?
Or maybe i am reading the histogram not correct.

ajar171
ajar171

16 Apr 2025 07:55 - 16 Apr 2025 08:41

Custom interface board questions was created by ajar171

Custom interface board questions

Category: General LinuxCNC Questions

Hi everyone!

Long time lurker here

Being fed up with the random avaiability of Mesa hardware in the EU, I decided to start designing an open source interface board. The schematics and PCB designs are almost finished, the firmware works so far, that I have communication between a development board and LinuxCNC and can control digital and analog inputs and outputs, read encoder inputs, etc.. So far so good...

Now to my questions:
- encoder scaling: where is it applied with a Mesa board? In the FPGA (did not find anything in the VHDL) or the hostmot2 driver or in LinuxCNC main software?
- motor acceleration and max speed: the same question

Thanks in advance!

Aciera

16 Apr 2025 06:16 - 16 Apr 2025 06:30

Replied by Aciera on topic Remap M6 in python

Remap M6 in python

Category: General LinuxCNC Questions

The task check to avoid execution on load can also be put into the ngc remap like this:

o<g123remapwrapper>sub
o100 if [#<_task> EQ 1]
M66 L0 E0           ;force sync, stop read ahead    
(call your python remap here)
M66 L0 E0
o100 endif
o<g123remapwrapper>endsub
m2

Also, as you have already found out, the 'print()' statements are actually executed during read ahead. If you want messages from the command queue you could use something like this:

    self.execute('(msg,your debug message here)')

unknown
unknown

16 Apr 2025 05:54

Replied by unknown on topic 7i92 firmware issue

7i92 firmware issue

Category: Driver Boards

Of course, having a "senior moment".

Aciera

16 Apr 2025 05:36 - 16 Apr 2025 06:49

Replied by Aciera on topic Remap M6 in python

Remap M6 in python

Category: General LinuxCNC Questions

Python remaps are tricky to get right. I'm no expert but I have done a lot of trial and error during my work on Tilted Work Plane codes which uses a fairly complex python remap (although no M64, M65 usage).
github.com/LinuxCNC/linuxcnc/blob/master...ting/python/remap.py

On this background I would like to point out a few general things:

You might want to put something like this at the beginning of your remap so it does not execute on load:

if self.task == 0: # ignore the preview interpreter
    yield INTERP_EXECUTE_FINISH
    return INTERP_OK

Also note this restriction for the 'yield' feature:

linuxcnc.org/docs/html/remap/remap.html

which means that code like this is not allowed:

            if router_down:
                print("Raising Router (P14)")
                self.execute("M64 P14")
                yield INTERP_EXECUTE_FINISH
                time.sleep(2)
                self.execute("M65 P14")
                yield INTERP_EXECUTE_FINISH

instead you could use:

            if router_down:
                print("Raising Router (P14)")
                self.execute("M64 P14")
                self.execute("G04 P2")
                self.execute("M65 P14")

Premature execution of the python remap by the read ahead may also be a problem. While 'yield INTERP_EXECUTE_FINISH' at the beginning would prevent that it would also bar the use of 'self.execute()' after it (as pointed out above). My usual workaround is to call the python remap through an ngc wrapper like this:

o<m6wrapper>sub
M66 L0 E0                                                   ;force sync, stop read ahead    
(call your python remap here)
M66 L0 E0
o<m6wrapper>endsub
m2

electrosteam
electrosteam

16 Apr 2025 04:50

Gmoccapy Modal Display was created by electrosteam

Gmoccapy Modal Display

Category: Gmoccapy

Starting to use G54 and G55 to enable two job locations - new to me.
Test run a short program with G55 in the header.

In Axis, the Modal Display changes to G55 when a program is run, then back to G54 on completion.

In Gmoccapy, the Modal Display stays at G54, even though the DRO Display shows G55 while the program runs.

In each case, the DRO Display correctly shows the G55 Offsets and coordinates during the run time.

I think this must be a bug.
If so I can live with it.

notJamesLee
notJamesLee

16 Apr 2025 04:40

Replied by notJamesLee on topic Determining Angular Scale - Help w/ Microsteps

Determining Angular Scale - Help w/ Microsteps

Category: Configuration Tools

youre 100% right, not sure where i got 533 from.

I set it to 600 and its still over shooting. Probably about 1.125 rotations again.

I am having trouble believing its the driver because with the 1600 it works perfectly and repeatable (not sure that's a word).

Maybe i need a sanity check on the layout of the belt system (simple diagram) attached. I dont think the tensioner (idler gear) makes any difference in the belt ratio calc (shout out uni for that one)

lrak

16 Apr 2025 04:18

Replied by lrak on topic LinuxCNC 2.9.4 Released

LinuxCNC 2.9.4 Released

Category: Installing LinuxCNC

2.9.4 is released - but not in forum.linuxcnc.org/29-forum-announcements?

Looking via Debian - it appears this is only in sid=unstable - so not yet stable or testing - so your install instructions won't work for anyone running anything other than unstable.

That being said, I currently have 2.9.0~pre1+git20230208.f1270d6ed7-1+deb12u1 under bookworm.
And have had some random resets.. Is there a list of what is fixed in 2.9.4 ?

So to install in bookworm you would have to install half of testing as dependencies.

I'm not complaining - like seeing the progress, but hope this might help others that run stable=bookworm.

I put trixie on a laptop for non linuxcnc - runs well, but lots of libs are getting updated at a high pace as the freeze has been approaching . trixie is supposed to release sometime in the second half of the year - when it is ready.

[color=#000000]The following packages have unmet dependencies: [/color]
linuxcnc-uspace : Depends: python3 (>= 3.13~) but 3.11.2-1+b1 is to be installed
                  Depends: libc6 (>= 2.38) but 2.36-9+deb12u10 is to be installed
                  Depends: libglib2.0-0t64 (>= 2.12.0) but it is not going to be installed
                  Depends: libgtk-3-0t64 (>= 3.11.5) but it is not going to be installed
                  Depends: libgtk2.0-0t64 (>= 2.8.0) but it is not going to be installed
                  Depends: libpython3.13 (>= 3.13.0~rc3) but it is not going to be installed
                  Depends: libstdc++6 (>= 13.1) but 12.2.0-14 is to be installed
                  Depends: libtirpc3t64 (>= 1.0.2) but it is not going to be installed
                  Depends: libgtksourceview-4-dev but it is not going to be installed
[color=#ff5454]E: [/color][color=#000000]Unable to correct problems, you have held broken packages.[/color]

Hope this is helpful.

electrosteam
electrosteam

16 Apr 2025 04:17

Gmoccapy Touch-Off Offsets was created by electrosteam

Gmoccapy Touch-Off Offsets

Category: Gmoccapy

3-axis mill with RPi 4B and LC 2.9.3 from Download page, and Gmoccapy 3.4.6 - runs a job fine.

Offset Values:
In Axis, Touch-Off populates with a value generally within 0.001 mm of the value entered
Minor corrections are often successful, but sometimes ignored.

In Gmoccapy, Touch-off x=0, y=0, z=0, G54 populates with a value, like z=0.511.
- Touch-off often leaves small errors on the DRO, like 0.008 mm.
- I seem to run in circles trying to get the Offsets Page to agree with the DRO display, the G54 values, and the current position.

Suggestions ?

electrosteam
electrosteam

16 Apr 2025 04:02

Replied by electrosteam on topic Gmoccapy Stop Mid-Run

Gmoccapy Stop Mid-Run

Category: Gmoccapy

Got some time to review mill operation.
Delving into G54 and G55 Offsets.

I think my problem was an attempt to travel beyond the Z- soft limit.

So, one of my current educational tasks is to try and get something like an error code displayed on a soft limit excursion.
As suggested, like HalScope or HalShow.