Advanced Search

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

The boards have different ip addresses, on a separate switch without wi-fi and without internet. There are only three elements in the network: the host and two boards, all have different static ip addresses. I noticed that the LAN is completely blocked when linux cnc is running with one board, even ping does not work.
An error occurs on this line from hal:
loadrt hm2_eth board_ip="192.168.0.121, 192.168.0.122" config="num_encoders=6 num_pwmgens=1 num_stepgens=5, num_encoders=2 num_pwmgens=2 num_stepgens=10 sserial_port_0=0xxxxxxx"

From log:
hm2_eth: 192.168.0.121: INFO: Hardware address (MAC): 06:2e:1b:12:00:38
hm2_eth: ERROR: can't connect: Network is unreachable

The first board connects, the network is blocked, and the second board cannot connect.

I just realize I didn’t quote the original question so of course my question didn’t make sense. It is about this realtime error. I installed ethtools and the error disappeared. After upgrading from LinuxCNC 2.8 to 2.9.3 the error came back.

 

 

Sorry, yes, you are right.
Though it is mainly intended for MPGs so that the machine doesn't shake to bits responding to each MPG pulse individually

What was limiting the accel previously? I am not sure what has changed to affect this. Is the behaviour the same for both joint and axis jogging (ie, before and after homing)