Advanced Search

Hi,
I upgraded my machine from linuxcnc 2.8 to 2.9 and now I have a problem with probe_screen (from verser), because of my small monitor. Everything worked for 2.8, where I used probe icons for a 1024x768 screen. But the actual icons of the version for 2.9 do not include these, which leads to a gmoccapy gui that is larger as my monitor.
So my question is how to solve this:
Is there a way to reduce the whole probescreen with some commands?
Or does a reduction in icon size solve this? If so, to which size should they be reduced? I am not sure if I can use the old ones, have not tested yet, maybe that would be a third option, but it looks as if the one or other icon has been added.

Ooooh, wow! That worked like a charm Thank you so much!

Hi all,

This question is coming from me trying to better understand motmod. What about motmod makes so that this comp needs to create and manage its threads instead of having the "threads" module handle setting up threads and then loading motmod after?

So far I understand that threads need to be loaded in a particular order (fastest to slowest) and that motmod also ensures that the base and servo thread are integer multiples of each other. Besides this what other things does the motion planner need to guarantee about its threads to work properly?

I installed a fusion 360 post processor, with probing macros

put the path in linuxcnc, set up the probe and tried to load the circle hole probe. i get bad char '/' near line 27

the macro loads up in linuxcnc and the probe g-code doesn't contain any /, tried a different macro and get the same error

not sure how to trouble shoot this 

Hello.
7i48 has 6 channels by muxing has this any limitation compared to 7i37 ?
Where can i buy both cards and thcad2 from europe in good prices ?

Seems to work on axis (2.10):

 

zz912 wrote:

How did you try it?

I would expect it to list all the tools from the program. Do you have more T in the program? T5, T4, T100 ....

Just uncomment the print statement in gmoccapy.py:4011 of my dev branch: github.com/hansu/linuxcnc/tree/gmoccapy-3-5-0

Yes I used a program with some different T commands...

Moin
Ich habe vor einiger Zeit mittels einer Relaisschaltung den Spindelstart per Linuxcnc umgesetzt. Vorher musste ich immer von Hand starten und stoppen.

Nun habe ich allerdings das Phänomen, dass bei laufender Spindel die Maus nicht mehr funktioniert. Die Tastatur funktioniert tadellos und auch die Laser der Maus ist an. Aber der Cursor bewegt sich nicht.

Es hat definitiv mit dem aktivierten Relais zu tun, aber was kann es sein und wie kann ich das beheben?

Ich nutze eine Mesa 7i76

Gruß 

Yes I saw !
Thanks a lot.
Kind regards
Philippe

How did you try it?

I would expect it to list all the tools from the program. Do you have more T in the program? T5, T4, T100 ....

You can exclude the tool change gcode from the preview interpreter by checking 'task':

zz912 wrote:

List of tools can be helpful before run the program:

I just tried it and the toollist was always empty. No idea in which cases there are tools listed or if it's a bug.

Yes, all access is blocked to the interface that LInuxCNC uses
when LinuxCNC is running.

I would use 10.10.10.10 and 10.10.10.11 addresses for the 7I92 cards
to avoid possible overlap with local NAT address ranges.

Once this is done and you have set a static host IP of say 10.10.10.100
you can test the network setup by pinging 10.10.10.10 and 10.10.10.11

Then LinuxCNC setup must match.

Previously both, the MPG jogs and the keyboard jogs were limited by multiplexing lower acceleration values to ini.*.max_acceleration parameters during these jogs. Here is the commit message:

xhc-hb04.tcl use *.jog-accel-fraction pins
instead of mulitplexing reduced accels to ini.*.max_acceleration. Notes: 1) the prior multiplexing to ini.*.max_acceleration pins required a helper script (scripts/xhc-hb04-accels) since the ini pins are not available until task started. 2) the fractional accel settings apply only to wheel jogging (not other forms of jogging using nml commands)

The xhc-hb04-accels script is marked as obsolete and not used since 2.8~pre. The new suggested solution, to use *.jog-accel-fraction pins does not cover the keyboard jogs. Only MPG jogs.

Link to xhc-hb04-accels script from v2.7.15

Perhaps a unified test platform for the "sysgen" aspect would help.

Tom