Advanced Search

Search Results (Searched for: )

  • tommylight
  • tommylight's Avatar
16 Apr 2025 09:10
Replied by tommylight on topic LinuxCNC S-Curve Accelerations

LinuxCNC S-Curve Accelerations

Category: General LinuxCNC Questions

Always use --show at the end of latency histogram, it will show the number of excursions that are not inside the visible area of the histogram, but they can be seen as multicolored columns on both sides of the histogram.
Also, use --nobase if there is no need for the base period, it adds more timing strains to CPU that will mess with the servo period latency results.
For both periods
latency-histogram --show
For servo period only
latency-histogram --nobase --sbinsize 1000 --show
  • tommylight
  • tommylight's Avatar
16 Apr 2025 09:02
Replied by tommylight on topic Custom interface board questions

Custom interface board questions

Category: General LinuxCNC Questions

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
  • Grotius's Avatar
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
  • Aciera's Avatar
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
  • Aciera's Avatar
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.


 
Displaying 17176 - 17183 out of 17183 results.
Time to create page: 0.689 seconds
Powered by Kunena Forum