Advanced Search

mine do not work too....

!BXYZ
!BYXZ

on a older version of Probe_basic or Linuxcnc (i dont know) it worked well...

that's cool

I am almost done. The Graphic in Overview, Hal and Axis works now.

rio.v and makefile OK.

One last issue: Warning: can not find toolchain installation in PATH: nextpnr (nextpnr-ice40)

Furthermore there is an error: loading joypad:: No module named 'fcntl'. No idea what I have to install here.

Just wanted to update, I spent many weeks verifying the wiring on the machine, and everything looked good from that standpoint. So I went back to the PID settings with a different approach, and have seemed to land on some stable settings that make the machine work correctly! The tool changer also needed some PID tuning and now seems to make all changes correctly.

Still have to set up the touch off probe and tool setter before I start making chips, but progress will be much slower with winter here

So wanted to thank everyone for offering help on this! When starting out you don't know what you don't know, and that made getting to this point difficult.

I’ve got an issue. I have a 7i95T board and Pico Systems brushless DC drivers that take PWM input. I assume I need a new firmware to convert all step/dir to PWM? Can anyone help me?  Additionally, I assume this won’t interfere with the 2 serial ports?
Charles

I'm most interested in using a non linuxcnc axis output to move a stepper motor for carousel motion, I'm fine with the rest of the macros being required and it being somewhat hybridized.

for the load tool not in carousel, I will be doing some extensive rewrites on the atc macros very soon which is what prompts my question, I would like to try and do both the "all macro" and "carousel comp/macro hybrid" edits in parallel while my mind will be saturated with the knowledge...lol I'm sure you can appreciate the benefit in that, its a good bit to keep track of and much easier when its all fresh in the brain.

The new data Base tool table feature is going to be a game changer for probe basic as it will add quite a bit of awesome functionality for those using atc's. the ability to have tool parameters stored and be accessible in the DB to be used in macros will make all the difference in what can be automated and simplified.

I am pretty excited to start work on it, just shoring up a few things in the shop before I can get to it. if you want to share what you have going on that would be a great start I'm sure!

Thanks Spumco!

Chris

Tool touch off is done.
gnipsel.com/linuxcnc/flexgui/tools.html#tool-touchoff

JT

Hi Salame,

I live in Holland near Gorinchem and Rotterdam.
It would be great to have a servo drive and motor and test it to be auto configurated.

it means that any servo drive will be auto configured?
At this stage, i can not confirm this.
When i retrieve the info from the ethercat bus, and pdo config is made for the drive.

Then i can test the servo drive to send commands.

It would not mean every drive would have the same pdo config, these would be different,
but we can automaticly sort data out and do suggestions for that data like:

If it comes out that a servo position command is always a 64 bit value. Then we can already map this to
a position command. It's just figuring out a few things.

If it turn's out there isn't any logical explanation in the servo pdo config. Then we can add a 
template for that particular servo drive vendor id.

@Fakename
The links are broken indeed, the source has moved to :
codeberg.org/skynet/realtime_app/src/bra...dor/ethercat_twincat

It is part of a bigger project that used opencascade.
 

thanks
for the gui you need to install some python packages.


@all
oss-cad-suite stuff runs also on windows now

 

so it is not so hard to run the other toolchains also

EDIT: gowin works also
 

I can run it under Windows now, but the graphical stuff does not work. 

In my case, it would be more convenient, as I only have Linux on the Raspberrry Pi 5.

Anyway, it is better that you use your time on the important stuff. The whole project is very impressive. Congratulation!!!

Thanks for the images. I'm encouraged to see some have the low data rate type A interface, so it appears the data requirements to the MESA card are not super demanding. USB data throughput has really evolved from the original 1.0 (12Mb/s) to 3.3 (20Gb/s) or 1600x faster. From what I have read 95% of the cheap so called "fast" 3.2 cables don't even have the conductors for the fast laneways so the port reverts back to the lower original slow laneway and the non technical people wonder why the device doesn't seems all that much faster?

I found an original IBM Thinkpad "OnePort" docking station on eBay for $10. In addition to the Ethernet port it has 2x USB 3.0 ports (5Gb/s) so the "OnePort" interface must be pretty capable, that "OnePort" docking station interface was replaced with a USB 3.x port the following year.

I'm still at the beginning of my LCNC experience, it means that any servo drive will be auto configured? If you want to make some test I can send you one, where are you located?

Thank you Collins.

Attached video shows the 3 interpreters tools moving around.

There is no motion component or whatever. The tool is just jumping to the consumed gcode position.

One of the problem's is when adding gcode segments to a infinite program, it has to check for duplicates,
and there must be a limit to the gcode preview. Otherwise we get a buffer overflow.

This run's quite stable, fixed some runtime bug's.

Was looking for info about raspberry, do you suggest to make a new buil on pi 4 because it's more stable? Or it's worth go with the 5?

you can use this Spartan6 module, but have to setup/modify 'riocore/boards/Spartan6/board.json' and change package and type for your needs.

programming will not work over w5500 you need to write the bitfile into the flash.

---

@all
WINDOWS-WARNING:
rio was not intended to run on windows, at the moment i can't give windows/mac support for it.
I just made the system a bit more platform independent.

i normally don't use windows at all, but i think if you customise the generated makefiles a bit, you could generate the bitfiles there too, but very experimental .