Advanced Search

hello!

I went through this too! I'm finishing a document with files... very neatly so there are no doubts... when I finish I'll post it here

if you are on the latest version you can have a look at how the probing parameters are stored, its kind of ugly and cumbersome but currently is the only way we could figure to do it from within the ui. we are essentially sending the widget entry parameters to a subroutine (which is a built in feature and simple by using the widget container name: #<widget_name> = #1 as shown there for example. however this does not work for M6 Remap calls for some reason, so we have had to add an extra step which is to send the widget parameters to a subroutine where we can then write them to the var file. its cumbersome and not pretty but it does work relaiably. the parameters are stored int he ui and are loaded from the settings file based on the yaml file definitions.

it works fine but in the future we would like to find a more elegant solution. remap kind of plays by its own rules which has been found to be difficult to work around.

hope this helps!

Chris

In order to tackle the cooling of the servo motor and head of the machine I ordered two 80mm Ncotua branded fans.

 

I installed the fans in the top cover so they blow across the head of the machine including the toothed belt and then onto the spindle servo motor.

 

 

 

 

 

I wired the two 12v fans in series and power them with 24v from one of the outputs of the Mesa 7i84 expansion card in the control cabinet.

In order to have the operation of the fans automatically controlled I added a line of HAL code to my LinuxCNC configuration which slaves them to the spindle-enable signal.



Next up is the replacement of the spindle bearings which have been making bad noises for quite some time...

 

In order to test the new spindle motor I decided to mill a new polycarbonate shelf for my parallel blocks.

I milled the polycarbonate at 2500 rpm with very little noise however another issue crept up which I had overlooked, heat!

The old induction motor had a big fan on the back which not only cooled the motor but also indirectly cooled the head of the machine. Without any airflow the new spindle servo got pretty hot after running for an hour straight. The head of the machine was also uncomfortably hot.

In order to be able to finish milling the polycarbonate I ghetto rigged a small USB powered fan on top of the machine which did the trick.

Here is how the polycarbonate shelf came out. 





 

 

so I got stuck, still can't get any movement , and yes i tried everything , someone please explain what are the basics to get an operational system...
from absolute zero ... in what order to do stuff ... i am sure i did something wrong and just got stuck so i will restart from zero but ... please please please someone can tell me the order to do stuff ... i just erased everything from the harddisk and have option to start from zero ... 

Is the direction above reversed? It should be
net x-output => cia402.2.velocity-cmd

That is how I would do it but those directional symbols are for readability only and are ignored when the file is parsed.

the sim should work without any modification to the config files, if so then everything is installed correctly, just compare your config files for your machine config to the sim config files. there are a few sections in the ini file that are required for probe basic and they stand out easily enough and then there are some additional files in the sim config that you won't find in the axis config folder that will need to be copied over. its not too bad and its good to become familiar with these files as they are there for user integrations and customizations in probe basic.

In regards to Ohmic triggering, did anyone try to add a resistor in parallel to THCAD input?
That should raise the current required to trigger, and might improve usability a lot.
A 220 ohm 5W should be a nice value to try, it raises the reuqired current to roughly 120mA, instead of uA. Should be more than enough to eliminate water induced triggering.
470 ohm will be under 50mA, if that proves to be problematic on dirty and rusted sheets, although i doubt it.

There isn't really anything you can do.
I guess you'll just have to wait for your PR to catch the attention of somebody with the required github privileges.

I guess I should clarify I’m referring to the master builds (and docs) on distros > Buster.

Bari wrote:

onelaboratories.us/rtai_lcnc/    5.4.258 matching RTAI kernel and LCNC debs
onelaboratories.us/abc/  5.4.279 matching RTAI kernel and LCNC debs


To install on Debian 12 with linuxcnc-uspace already installed use : sudo apt purge linuxcnc*  and wait for apt to completely remove every trace of LCNC.

 

 

Trying to follow the instructions, but linuxcnc does not get removed and I get the following message when I issue  sudo apt purge linuxcnc*  

Package 'linuxcnc' is not installed, so not removed


Thanks

Philip

Try the one from Todd first, then the Highlab one.
Normally there is no need for it as our official build uses the regular one, while the Debian BookWorm from the Debian site uses the Highlab ones.
For all Debian BookWorm versions and Linux Mint Debian Edition 6 and Ubuntu 24, the Higlab one is used, so to get the latest build would require changing repositories as RodW mentioned on several posts, probably can be found on one of the pinned topics on the "installing LinuxCNC" section of the forum.
No need for any of this if using the official ISO.

I do not think you need a base period for EtherCAT, so if that is the case it would be good to remove it.
Ferror values for meteic machines are usually 0.1 and 1, maybe someone with working machine can chime in on what those values should be as those can cause joint errors.
Amplifier fault is caused most probably from interference, if those pins are used in hal and attached to drives, but can also be from drive falting, so check the lights on the drive when it happens to be sure.

But no distro for bookworm. Now what? Build from source I guess.
Jim

Todd is right, that is the buildbot that builds the official Debian packages, and is always behind from the normal boluildbot Todd linked.
No idea why, but there were differences between those two builds for BookWorm.