Advanced Search

Which type of servo drive do you use?

Martin87 wrote:

I also have an automatic tool change that already works, but I'm prompted to do so every time I change a tool and have to confirm the tool with the OK button.
I don't know how to delete it from the system. It should run automatically without the OK button.
Do you perhaps have experience with this?
Kind regards

I also have an automatic tool change that already works, but I'm prompted to do so every time I change a tool and have to confirm the tool with the OK button.
I don't know how to delete it from the system. It should run automatically without the OK button.
Do you perhaps have experience with this?
Kind regards

pippin88 wrote:

Suggestion / request:
Overrides
When starting a program running (cycle start): user is prompted that an override (rapid, feed, or spindle) and asked whether they want to continue with override, or want to reset to 100%

HansU wrote:

I could imagine make an optional warn dialog with a settable limit. For all overrides? Feed, rapid and spindle?

Yes, something like attached.



Warning pop up if any override is on.

Switching from `pigpiod` to WiringPi resolved the issue—SPI communication is now working as expected.
Thank you very much for the detailed explanation.

I followed your instructions and used the following `gpio` commands to generate the clock:

gpio mode 7 clock
gpio clock 7 5000000

While I couldn’t measure the actual frequency, the FPGA responded properly after applying this change, so it seems that the commands produced an 18 MHz clock as you suggested.
My `board.json` already contained the following settings:

"clock": {
"osc": "18000000",
"speed": "29812000",
"pin": "35"
}

After this setup, the `rio-test` tool returned valid results, and LinuxCNC no longer shows the `"HXHP"` error.

It appears that the 5 MHz clock generated by `pigpiod` was not suitable for the ICE40, and this prevented the FPGA from functioning correctly.

Thanks again—this completely solved the problem.

I reinstalled the ethernet drivers and got it down to 12ms so got it working for now, all tho at slow speeds. I order a faster mini computer so I hope that gets fixed, I installed a 7i76u daughter card, I flashed the bin file and nothing again the CR3 led is yellow and CR6 led is red. I installed the 7i92 with 7i76 bin file.

yeah its a pin phil added in the plasmac usercommand file
github.com/LinuxCNC/linuxcnc/blob/master...c2/plasmac2.py#L5689

Thanks for the warning. What or where is the issue with raster galvo laser support? I'm still learning about linuxcnc and the mesa hardware and understanding how to implement the relevant capabilities.

This project involves only vector laser cutting or sweeping some areas with the galvos, not raster etching of images or text etc. In the future though of course it would be good to have both vector and raster capabilities.

Dear LinuxCNC User,

I have bare minimum code of .ini and .hal file that perfectly working for single axis linear stage. Now, I want to add two switches one for emergency stop and another for feed override. I am planning to use pin 0 for emergency stop and pin 1 for feed override of Mesa 7i95 board.

Kindly provide the necessary pieces of code that need to be added in .hal and .ini file. explain the logic of the connection because I am not an expert of editing the .hal file.

The wiring I am planning for these switches are following..

either 0 or 5 volt to pin 1 using external DC power supply (I don't have switch currently but will buy it soon)

Continuous Analog voltage from 0-5 volt at pin 2 using another DC Power supply

GND, 0 volt at pin 3, because it is common ground for pin 0 and pin 1.

I am using linuxcnc 2.9.2


Thanks.

Thanks Tommy. The attached files will support the 7i97t.  I created a config successfully but I don't have a card to test with so maybe the OP or someone can give it a try and let me know if it works.  I can send in a pull request if it's good.   This will only work with 2.10 master.

After updating to latest master just copy the attached private_data.py file to /usr/lib/python3/dist-packages/pncconf/ and the pncconf.py to /usr/bin/pncconf

I would suggest making a backup copies of the original files first just in case.