Advanced Search

smv wrote:

Right now gcode++ extends g-code by introducing for loops, while/do-while loops, as well as imports (currently working on test cases for the same for the latest LinuxCNC release).

You know that LinuxCNC G-code already has do/while loops? 

linuxcnc.org/docs/stable/html/gcode/o-code.html
 

I am successful and fully transition from my old Parallel Port PC to an I7 Laptop with Riocore! Finally I am able to browse something without waiting forever Thanks Olli! This is great stuff.

I have my
- whb04b-06 Hand wheel operating
- Classic Ladder with RS 485 Modbus working (over an dedicated RS485 USB Dongle)
- Auto squaring Y Axis
- Touch plate/Probe input

It was not terrible, but I feel like I have modified a lot of ini and hal files which were created automatically to make this work. Is there a way that you could add a checkbox or so to ricocore gui to not overwrite the existing config files?

I don't know what the best workflow would be. I think if I want to add another function to the FPGA i I will just do it in a separate folder and flash the FPGA, then add the changed manually to my machine folder ?!?

Look at the files in the sample directory. They should be already part of your installation, but you can also see them here:
github.com/LinuxCNC/linuxcnc/tree/master/nc_files
Look at the lathe_g7* files.

Can't believe I missed it.

Cheers

github.com/multigcs/riocore/tree/dev/riocore/boards/Mesa7c81

OK, there only dif in mine clone was the SPI & FPGA clk pins. Seemed to be very picky regarding that.

Any code in the repo yet ?

Hello.
I have the same question.
After probing i have the Z coordinate value.
I measuring 2 points to align the B axis.
I'm doing it 2 times.
The 2nd measuring if gives a result with equal 2 decimals don't rotate the B axis.
Is there a code for the g-code to get a result in parameter, like in the debug
%.xf = x (0-9) number of decimals?

Good the hear, thanks for update.
The firmware needed an overhaul to get all info in and out anyways.

I found the limit in the software but it wasn't just to increase 16 PDOs to say 32 PDOs.
For the time being I consider 16 PDOs in and 16 PDOs out to be the max the number of PDOs the Ax58100 can handle.
It can be more, but my tests doesn't show that and I find no info in the pretty useless datasheet of the Ax58100.