Advanced Search

On you actionbutton (in Designer):
Select property 'indicator_status_option'
Select property 'is_homed_status'

Then set your stylesheet, though usually one would set a specific button:

I live in north ... here continuos rain these year not usual ... some disaster happens .... not a lucky year for whether here. These summer until 1.5 month ago 42°C than in 5 days we go to 18°C ... and now it rain every days with stop of 1 or 2 days than rain again.
Happy places Holland. Your plains are very beatiful. Never visit Kosovo .... before I had the boys I thought of going to visit Tommilight on  motorbike....now the motorbike has dust and it's been almost 10 years. ... life is strange .... beautiful and strange ....

When opcua compile correctly using cmakelist ... I add that features on my project, for now seems I use double version od opcua62541.h heather ... maybe ... installation process on qt is not well understand from my side. So I have multiple copy of plugin and heather in many parts.

 

spindle speed 2000-2500 rpm

meister wrote:

Hi,
very cool !!!!

for my board without oscillator, i need to run:
```
gpio mode 7 clock
gpio clock 7 5000000
```
to provide a clock signal for the FPGA


for flashing i use this script:
```
riocore/configs/IceShield/spiflash.sh
```
all as root.

LinuxCNC runs as user,
i think i use the normal LinuxCNC RPI image (bookworm)

if you use the default config with:
```
{
"type": "blink",
"pins": {
"led": {
"pin": "LED:G"
}
},
"frequency": 1.0
},
```
on of the LED's have to blink with 1Hz after flashing

to test the connection, you can also use the rio-test tool:
```
bin/rio-test riocore/configs/IceShield/config.json
```
 

It works! Thank you, the GPCKL0 gpio config was just what I needed. Linuxcnc talks to it just fine now. Also, it seems I forgot to route pin 7 to 35 on the FPGA

I'll adjust the board to route that line, dump a production outputs file and instructions for people to order it, and push it up to github along with the config once I confirm the motors and switches do what I need them to do for a standard 3 axis mill setup.

 

To add a liyttle more detail:

-> qtversaprobe.enable

reflects the state of the 'measure tool' button on the versa probe screen.
This is a manual selection button (to ignore auto probing)
It doesn't do anything unless the remap code utilizes it such as:

-> qtversaprobe.probe-loaded

true when the tool number equals the preference files entry:
ps_probe_tool = 1

It doesn't do anything unless connected to other logic such as spindle.0.inhibit.
If you have multiple signals to connect to spindle.0.inhibit, then you must use an OR logic component.
 

No homing expert, but if the search and latch velocities are in the same direction
it seem like you would always end up on the switch after homing if the home final
velocity was 0 (and it seem to be set to 0 on all joints) It also seems like to avoid
this you also need home defined.
 

Hey, I've had this issue on and off for a while and I am still trying to figure out the reason my system does this every so often:
My Y axis has 2 steppers and 2 limit switches. Y(1) being on the left, Y2 the right. When the limit switch for Y2 triggers the motor backs off the switch and (supposedly) waits for the other axis to finish finding its home.
Y(1) hits the switch, but instead of backing off it pauses for a fraction of a second then continues to push into the switch.
I hit the Estop at that point as the stepper starts skipping when it gets near the end of its travel.

Video of the switch issue


Things I've checked:
Restarting the system entirely doesn't seem to have any effect.
Wiring is all good, I can see the corresponding lights on the mesa board lighting when the switch is pressed
The switches is fine, I switched the 2 axis switches and got the same behavior
Signals are coming through according to the HAL meter with Y and Y2 home both showing true when pressed
The home offset is set for 5.00 mm for both sides, meaning the gantry should move in the negative direction (away from the switches) when correcting (and it does when it occasionally works)

Any help or suggestions would be very welcome.

 



On a side note: I'd love to know what the homing subroutine looks like, but I can't find anything online for it. Is it possible to remap it like the M6 tool change in the INI?  

Badass man, submit a pull request