Advanced Search

Muchisimas Gracias, de todas maneras, comparto lo que tengo Placa Intel D865DKD, procesador Intel Celeron 2.53Hz )1 cpu lógico), 998MB RAM, kernel 3.4.9-rtai-686.pae. Test de latencia: Max Jitter servo 1ms us a 405us, con wifi apagado y BIOS con APM desactivado. ¿Con período de base de 100000 ( 100 us), en Stepconf, se queja de latencia?. Que hardware maneja usted?, Aún me gustaría saber lo de JT, quien me confirmó, que usaba ese Ubuntu hacías años, sin problemas. Muchas Gracias por haberme respondido y su paciencia. Me encantaría que ésta viejita de cpu, me anduviera bien....

I think I can configure it myself, but I decided to start this topic because, firstly, maybe someone has a ready-made solution, and secondly, it may be useful to someone else.

Well, I bought a Chinese rotary axis. It is of good quality and works properly, but the designer did not provide homing limit switches.
I decided to add them in such a way as to interfere with the original structure as little as possible.
I came up with an idea that if you cleverly place miniature inductive sensors, they can work with small pieces of metal attached to moving elements, while the sensors themselves will be attached to a stationary base.
I fiddled with it a bit and it worked.
The video shows a complete makeshift, the elements are attached with double-sided tape, and the Chinese TL-W3MC1 sensors work with plates from a canned food can. Of course, ultimately it needs to be done better.

As you can see, the B axis (tilt) is referenced first, then it is set at the appropriate angle relative to the sensors (in this case +90 deg from machine zero), and only then the A axis (rotary table) is referenced. No special combinations are needed here, just set the HOME, HOME_OFFSET and HOME_SEQUENCE parameters correctly in the ini file.

As I wrote above and as you can see in the video, it works properly, but there is a problem that needs to be solved.
Well, everything is fine when we base all axes at once.
If we try to reference only the A axis, it will probably fail, because the sensor and the mating metal will be in such positions that they will never come close to each other. Therefore, when homing only the A axis, should be first check whether the B axis is referenced and is in the appropriate position, and then decide whether to perform homing or display an appropriate message instead.
It seems to me that LinuxCNC has the appropriate pins and HAL components to do this, but I haven't thought about the details yet, because I only started this project today and, objectively speaking, I've already done a lot.

If someone would like to help me, that would be nice.

Yes indeed it was a wiring issue. As I was debugging today I discovered the power connector to the micro stepper was loose. When will I ever learn?!

Hi all,
i'm starting to finishmy first conversational wizzards, in first time this is for our aluminium work to make toolpaths for windows and doors profiles but it comes realy nice to other things to, to quickly make combinations and create the right toolpaths during day work to save and open in machine without the need of complex operations, software and exports.

Contains basic functions like orbit, pan and zoom in the perspective block, top view, and option to configure your header, tool change and footer of the gcode to turn more compatible with any requirements.

This will run in any browser and it will be in just one single file with no need instalations, as you will only need a browser wharever your os is.
So i'am open to useful tips to sse what you more experienced operators think will be nice to implement.
thank you in advance for your possible tips.

After update i am not able to run my flex ui


Edit:
It's just my testing in virtualbox, so no problem. Flex examples crash also

I'm sorry, I'm just a user like you. But that sort of thing is not unexpected when running the development branch (currently 2.10) and not the stable release version (2.9). The development branch is where changes are introduced and those changes are often undocumented or not fully documented. And things do occasionally get broken.

While I would not hesitate to use the Master branch to run a machine if a needed feature was only found there. I would want to thoroughly test it on that machine before releasing it to a production environment. And I would be extremely hesitant to update the version of said working machine without further rigorous testing. Personally I will stick to the general release branches whenever possible for machinery others might use. Master is for testing.

That seems to be working. I just finished successfully downloading the source code over my very slow internet. Soon I have a meeting with a client, so I will have to explore further later.

Download problem found and fixed

Thanks to everyone who reported that the Debian packages could not be downloaded from www.cnc.gmbh/download even when logged in. The cause is found and fixed, please try again.

What happened: the shop server read the whole package (about 30 MB) and pushed it to the browser in one piece. The web server behind the shop allows only two seconds per send operation, so on a normal internet connection the transfer was cut off before the first chunk was through. The browser then received an empty file, or nothing at all. The login itself was never the problem.


If it still does not work for you, please post the file name, your browser and roughly the time of the attempt so I can check the server log.

Todd wrote:

I seem to recall reading a recent message somewhere that talked about replacing all 32 bit hal code with 64 bit versions in Master. This might be your problem. I suspect that the new command your code needs to use might be "hal_pin_new_uint" instead of "hal_pin_u32_newf"
 

You're absolutely right, that's exactly the point.
I created an issue on github linuxcnc-ethercat and received information that the problem was not only known to the authors, but had been solved long ago. You just need to download the deb package from the getset branch instead of main, or set a different source in the apt settings (I haven't checked it yet, but I believe it works).
But how is an average user who is not a LinuxCNC developer supposed to know about this?
He'll just do exactly what I did - update what he has installed, find out it doesn't work and start swearing...

Small update: I made a free online version of the OD turning cycle, so you can try it without installing anything.

turngcode.com/en/generator/?utm_source=l...m_campaign=generator

Enter stock and finished diameter, length and cutting data - it shows the passes in a 2D view (same simulator as in the program) and gives you a ready .ngc for LinuxCNC (G7 or G8, G54-G59). The calculation runs on the server and is the same as in the program, line for line. No sign-up, no email.

25-second video: www.youtube.com/shorts/wDvjlCfCUAQ

The other 11 cycles are still only in the program. If you try the online one, I'd like to hear what is missing or wrong - especially from those who turn on LinuxCNC every day.

Hi everyone,

We're looking for testers for a new LinuxCNC interface to Dynomotion's KFLOP (USB) and Kogna (Ethernet) motion controllers.

LinuxCNC's G-code interpreter and user interfaces (AXIS, gmoccapy) drive our third-order, jerk-limited trajectory planner (TP3), with velocity, acceleration and jerk limits per axis or per actuator. Motion execution and servo control run on the controller, so the PC needs no realtime kernel. It installs as its own LinuxCNC build in your home folder, beside any LinuxCNC you already have: LinuxCNC 2.10 built from source with four small patches, its realtime motion module replaced by a userspace one that talks to the controller. Initialization and machine functions are C programs on the controller, and a simulation mode runs without hardware.

Demo, LinuxCNC in Debian inside VirtualBox on a Windows PC:


(Please set quality to 1080p for better viewing)


Getting started: the QuickStart covers the VM, the install, the controller firmware and the first runs; on a Debian 13 PC the same install script should do it without the VM. The source is TomKerekes/KMotionX on GitHub , and FEATURES.md lists what works and what does not yet.

This is under development, and we would like to hear how it does on different machines and configurations. Please post in this thread, successes as well as problems: which controller, what you were doing, any error messages and the relevant configuration files, and install.log for installation problems.

Thanks for helping us test it!

Tom Kerekes
Dynomotion, Inc.

I seem to recall reading a recent message somewhere that talked about replacing all 32 bit hal code with 64 bit versions in Master. This might be your problem. I suspect that the new command your code needs to use might be "hal_pin_new_uint" instead of "hal_pin_u32_newf"

Hi automata, hi NWE,

thanks a lot for trying it out and for reporting this and sorry for the trouble. You're right: the download section and the manual link on cnc.gmbh are currently broken. The site was just migrated to a new system and the file links didn't make it over correctly.

I'm fixing it right now and will post here as soon as the .deb packages, the source code and the manual are downloadable. Your registration stays valid, so no need to sign up again.

Thanks for your patience and looking forward to your feedback once you have it running!

Daniel

I see an email half way down the front page yurtaev.com/ with instructions to contact that email for purchasing cards.

ajanfahri wrote:

The source code isn't publicly available, so I'm afraid I can't share it.

 

What association does your software development have with open source LinuxCNC forum? Free advertising?