Advanced Search

This may be closer to what you want:

# Input and output configuration
net button-press <= hm2_7i95.0.inmux.00.input-05 # Connect input pin 5 to signal button-press
net relay-1-control => hm2_7i95.0.ssr.00.out-01 # Connect signal relay-1-control to relay output 1
net relay-2-control => hm2_7i95.0.ssr.00.out-03 # Connect signal relay-2-control to relay output 3

# Load and configure timedelay
loadrt timedelay count=1
addf timedelay.0 servo-thread

loadrt xor2
addf xor2.0  servo-thread

setp timedelay.0.on-delay 1.0 # 1-second delay
setp timedelay.0.off-delay 0.0 # No off delay

# Timedelay connections
net button-press => timedelay.0.in xor2.0.in0       # Link button-press to timedelay and logic
net relay-1-control <= timedelay.0.out  xor2.0.in1 # Link timedelay output to relay-1-control and logic
net relay-2-control <= xor2.0.out                           # Link xor out to relay-2-control
 

Many thanks for your reply. So how would I make one button activate the two outputs with the delay of one second? I want when the input 05 is pressed relay one opens for 1 second. Once the relay closes after the one second, then relay 2 opens and stays open untill I release the button
I'm so lost with this

Okay attaching the config did not work. Second try

After installation of the 5.4.279 rtai kernel + the matching Lcnc version  and a reboot, applying rt_setup and rebooting again,
starting a the axis demo for the first time often causes the system to hang or the run to abort with errors.
This happened with about 7 tries on two different systems (a 4 core Intel - isolcpu=3 and a 6 core AMD - isolcpu=2,3,5).
Info attached, as well as a run of the RTAI testsuite (odt file).
The second start of the axis demo gives an RTAI warning, but ignoring that the demo works perfectly to the end.

Running the latency test for the first time usually shows permanent 0's for both fast clock and servo.
Starting the second time it works, but the servo thread is always 999725 at start, but clearing that both values stay below 10000 with multiple gears and browsing.

Edit: Any suggestions what is wrong here?
Thanks.

Robert



 

Hello everyone

I am a little lost here. I am moving my machine interface to probe basic. Most things work already, however when I press M6G43 and other commands which call for the subroutine "m6_tool_call_tool_page.ngc", nothing happens. GO TO ZERO or GO TO G30 do work.

If I look at the terminal I get the following:

And thats it. The machine is stuck there. I have attached my full config. Any input is greatly appreciated.

Greetings
Sandro
 

agree! it has been glorious watching this new planner evolve! you are a rockstar! that path is super smooth looking!

oh, yes delete those, those are notes for the config conversion process only! i will add that to the docs!

you can keep the user_tabs as long as the user_tabs folder is in the config, it should insert the user tabs in the ui.

user_buttons folder should also be in the config folder. which version are you running again? stable or develop?

Hi,

I have recieved tormach's source. Not latest version.
In the tormach source, the tp.c file (planner) is nothing special. The planner can be used in lcnc within a few hours of work.
I can do that on request.

Btw think we don't need tormach's planner. As this planner out-perform's tormach's planner in every way :

Did you ever get past reprobe? There is no backoff move, then is G43 called and at least G53 Z0, which makes no sense to call G43, while toolseter trigered. First i would cleanup this file with all commented lines and debug,  or do indentation, to make the executed code visible.
When the machine stalled, did it write toollength before?
For testing i always start from terminal. If necessary just close the terminal, and start new.
 

Ethercat 64 bit float is supported.
float-double-ieee
However, the ethercat drive delivers the encoder data in a certain datatype, and you can not change that.
For floating point there is the Ethercat REAL (32-bit) and LREAL(64-bit) data-types.
You convert them into a hal float (which is actually a 64-bit float, or double, since some versions back)
using the keyword "float-ieee" for REAL and "float-double-ieee" for LREAL.
On the other hand, for integers it is likely that linuxcnc is restricting by its 32-bit integers.
There are no 64-bit integers in hal (as far a I know is best to day).