Advanced Search

kzali wrote:

where is the github repository for baord
 

The RIO 5ax board is by no means ready and yet to be tested. I believe the PCB fab are currently laying out the silkscreen on it today, and so quite far from being a for-public release. Check back in a week or two, we should have significant progress made then. 

In a meantime (if in a rush) the Tang Nano 9k from Sipeed is as close as it gets to the Rio 5ax. Will require a W5500 module to go with it and some sort of 3V3-5V/5V~3V3 translation. 

1.6 is the current ethercat version.

oh well, one more thing 

if someone is from germany and has a Mesa 7C81 or 7I90HD lying around that he can lend for 1-2 weeks,
then I would try to port RIO to it

there is none

---

EDIT:
Just my general opinion on this:
I think it's fine if someone doesn't want to give out all the sources, he has already posted the schematics of many relevant parts.
I'm glad that someone with knowledge is constructing a board for RIO. 

If you want, you can also build your own board and just show the pictures here, I am also happy to help with such projects. The main thing is that everyone has fun and it helps the project to grow (community/bug-fixes/...)

Hello,
I have AC servo motor which has harmonic gearbox with ratio is 80:1
How can I setup LCNC to work correctly with the gearbox ratio ?.
Thank you.

Are they making some updates on ethercat right now? Because when I try to install it it says that it cant fetch some files, I checked and the files that he is searching are version 1.5.2. but the files on repository are version 1.6.1. these files are changed 15 days ago so I was wondering do you now how long will it take for them to fix that?

i meant this board

i Lcvette,

Yes, will check the mm to inches.

To test the scurve motion planner in linuxcnc i added a new repository , based on lcnc stable version 2.9.3.
Inside the repository we have the cmake framework to build one the current motion planner  "tpmod" and 
two a motion planner called "tpmod_scurve".
Conclusion: very compact code enviroment to test scurve motion planner.

Now to make the new motion planner work in linuxcnc, we have to add some logic because the new planner works a little
different then the current motion planner.

Main differences :
1. New motion planner loads gcode itself. Old motion planner, recieves gcode in chunks over the servo cycle.
2. New motion planner calculates "look ahead" before gcode execution, Old motion planner does this at runtime.

Possible difficulties:
1. New motion planner loads gcode itself, this can take a few seconds for big files. This could result in creating a multi-threading process.
2. The clothoid & spline fillets are not shown by lcnc gremlin on forehand. Validation and debugging is more difficult.

Next week i will add the code to make this work.

where is the github repository for baord

Hallo Danke für die Antworten.
Habe die HAL und INI Datei Kopiert hoffe es sind die Richtigen. Habe auch das Video angeschaut ist leider auf Englisch konnte daher nur wenig versehen. Gibt es einen Chresh Kurs damit man die Befehle verstehen kann? So mal schauen ob ich die File auch mitschicken kann.
Die Mesa Karte ist die 7i96s. Die x-Achse hat 2 Motoren.

too late

but W5500 pins are missing , so you can do this part

In fact don't change anything right now. Once I have the board and set PINs for permanent set-ups I'll upload my json(s) over and hopefully you can help me to have this included in Riocore. Let's wait!

ps. I'm really leaning toward binning those colorlight cards and going RIO/Gowin for all 3 (2ax lathe, 4ax mill, 3ax laser). No joke!

you will surely find what you need in this link

linuxcnc.org/docs/html/drivers/hal_pi_gpio.html

That's too kind strikes again! Thanks, Oliver. Can I further abuse your generosity and ask for the amendments below? (C7 part, 50meg XO, UDP). Otherwise final, I think. Convenience at its finest, too cool this GUI 

The short answer is, yes, you can change axis limits through HAL connections as well as through GCODE but there are a few things you need to be aware of.

- Axis limits are exposed as hal pins only after the GUI has started up. So any hal connections would need to be made in the POSTGUI_HALFILE
linuxcnc.org/docs/html/gcode/overview.html#gcode:ini-hal-params
As stated in the documentation #<_ini[section]key> parameters are read_only so if you want to change the value from Gcode you have to use a custom Mcode that uses a script language (eg tcl or bash) to execute a 'halcmd'

- Changes to ini parameters during GCODE execution will only become effective AFTER a quebuster command (eg M66 E0 L0)

My usual solution to change ini parameters from GCode is this:

1. save this bash script as 'M123' to a folder named 'mcodes' in your machine config folder and mark as executable:

To make sure that the changes are actually used we call the above script from a GCODE subroutine.

2. Save the following code as 'm123_wrapper.ngc' and save to a folder in your [RS274NGC]
SUBROUTINE_PATH

To make linuxcnc aware of these mcodes add these lines to the [RS274NGC] section of your ini file
Note 'argspec=PQ' will enforce that the 'M423' command is followed by a 'P' word containing the code for which axis [X(1),Y(2)] and which limit [min (1), max(2)] should be changed and a 'Q' word containing the limit value.
example usage:will set 'ini.x.max_limit' to '401'


The parameter handling can be changed to your specific requirements in the 'case' part of the bash script above.