Advanced Search

Thank you very much

It's the xy allowance 0.25mm , using a 6mm tool machining 6.05

Hello,
i just started with SolidCAM and try my first job -> attached photos..
All working toolpathes are blackish and one not working toolpath is blueish. Here i want a 6.05mm hole/4mm deep. Tool should be a 6mm end mill.
Tried many things but still don´t work.

Please help

..AND, I see now, Mesa page says 7i84 is obsolite, there is the 7i84U now..


AND differences are: 
1. Field outputs can be set to sourcing, sinking, or push pull modes on a per output basis.
2. Field outputs do not require flyback diodes for inductive loads regardless of load current.
3. 500 mA output current

So, nice!

Thanks! 


 

Thank you Tommylight,
looking at the 7i84 specs pdf, it seams the easiest solution.

Inputs and outputs works from 5V to 28V so it's ok (and yes you're right about the half/half voltage, as stated in the pdf).

There are two version of this board:

sourcing outputs: (7I84)
or sinking outputs: (7I84D)

I will use inputs only for now, but... I have to decide which one is better for any possible future expansion...

Any ideas? Better sourcing or a sinking outputs?

(Post Scriptum: probably Sourcing is better?)

Thanks

I also cover RT tuning in this video


What's not immediately clear that the servo thread and base thread are the only RT components used by Linuxcnc so that is why you only see one core in use.

LearningLinuxCNC wrote:

The load fail red led does come on and stay on when I boot up linuxcnc and get the error messages. also the green estop ok led is lit as well. Prior to starting linuxcnc the light is off.


 

OH, didn't read closely enough!  If you are saying the Load Fail LED only stays on after LinuxCNC starts?  I know of NO WAY LinuxCNC can turn this light on, except by maybe causing a fluctuation of the 12 V supply.
Please give a bit more detail.
Jon

LearningLinuxCNC wrote:

Jon,


The load fail red led does come on and stay on when I boot up linuxcnc and get the error messages. 

This is the killer problem!  The FPGA is not accepting the load of its program.  It is somewhat unlikely the EPROM has gone bad, but possible.  First, check that the +12V supply is operating properly, and does not have excessive ripple.  Without a valid program in the FPGA, nothing will ever work.  If the power supply is good, then it is possible the FPGA has been damaged, or one of the regulators on the board has gone bad or is overloaded.  You can check from the wide tab of U31 to one of the G terminals of P2.
That should read +3.3 V.  Then check the wide tab of U32, that should read +1.2V.  If either of these is out of range, something got popped.  You can also check for correct power up with the parallel port cable disconnected.  D4 (Load Fail) should blink once and then stay out.
Jon

You can also use a simple BOB on the expansion header, adding 5 more inputs (limited by BOB, not by Mesa).
And for RS422 see Mesa 7i84, it has 32 inputs and 16 outputs that work with 24V, but also work with 5V, i am pretty sure you can have half of IO with 5V and the other half with 12V or 24V or any combination of voltages as half and half. You might want to wait for confirmation of the half/half thing from PCW as i did something like that several years ago and i am a bit fuzzy.

Thanks PCW,
that's interesting... so maybe I better think about an expansion card to connect more inputs... I Know 7i96 has RS-422/RS485 and there are cards expansion with many I/Os...
I will think about. My limit switches works at 24V but I can think for a solution if this card works at a lower voltage...

A disadvantage of multiplexing is that the switch detection will be slower (by a factor of the servo thread period times the multiplex depth)

You could also use the parallel expansion port to add 17 more inputs (though 5V only and probable should have 220 Ohm or so
series resistors for protection)

Thanks Tommylight,
I know I can connect more limits/homing to the same input, but in case of a wiring problem/fault I will have a generic "Limit switch triggered error" and I would have to check all the switches wiring...

Instead if is it possible to multiplex limit and home switches inside LinuxCNC, by adding diodes connections between switches, it will reducing the all problem to 4 inputs only. This way, in the case of triggering I have the exact error like for example "Y Limit swtich triggered", so I can check only the Y wiring (in this example).

You do not need 12 switches for a simple machine, you need only 4 for a 4 axis machine, or for 3 axis with one of those having 2 motors/joints like gantry machines.
LinuxCNC can use the same switch for both limits and homing, it can also do all kinds of combinations to the point of using a single input for all limits and home on a 9 axis machine, granted none are tandem axis.
Here is some inspiration for DIY plasma cutting machines, certainly not the only one, but has more details about switches and reductions and overall building of such machines:
forum.linuxcnc.org/show-your-stuff/38547...-5m-cnc-plasma-build

Hi all,
I have a diy Plasma with Linuxcnc (it has some mechanical problems and never got it to reliably work... due to modification of the original project due to not having the planned space in my previous location... I will solve...), 

BUT I also had some wiring problems triggering limit switches...

AND, having all limit switches connected to one (or less than the total number) input in my 7i96,
I had to check every limit switch to find which wire was broken or had a loose connection (so triggering).

NOW, Hopefully in a few days, I'm going to be in another project (this NEEDS to work! ) adding Linuxcnc to a proper (not diy) milling machine by a Mesa 7i96S.

SO I WAS THINKING:

The Mesa 7i96S does not have enough inputs for 8 limits + 4 homing switches... SO

what if I make a diode schema to connect 8 limit switches (4 axis) + 4 homing switches to 4 7i96S inputs only and I multiplex these switches inside LinuxCNC?

I know there is a module called mux16 (or something similar, I have to check..), maybe I can connect it's output to the limit/home switches...

Has anyone tried that? Does it work?

This way if one limit or home switch get triggered when the machine is not there, I could already know the one to fix because the GUI would tell me which switch would be in error state...

Thanks for any reply,
Alberto.



 

I need good latency for software stepping.  I am using a parallel port and a HobbyCNC PRO Stepper board.  
I needed to update my LinuxCNC computer as it was still using Debian 9 on a really old computer.  I had ok latency on that old computer. 
But during the move to Debian 12 I decided to use a somewhat newer PC as well, the "new" one having an AMD A-8 processor.
During initial tests, Debian 12 worked well on this old AMD-A8 machine, but the latency was horrid.
I found this article as well:  dantalion.nl/2024/09/29/linuxcnc-latency...arameter-tuning.html  and after tuning mine I now have excellent latency for my needs. (Big thanks to "dantalion" if they ever see this post, I could not find any way to contact them to thank them in their blog.)
Before tuning: 200,000+ microsecond base threads
After tuning :6,000 and below. 
I ended up only setting 1 of the 4 processors for the real time tasks, vs 1/2 of them.  As when I was watching the cores using HTOP while running latency tests, one core appeared to be doing nothing.  And the non-realtime cores were getting hit pretty hard by other tasks when making the system work.  So I figured I would just let one core handle the real-time, and let the other three cores take care of other stuff.  Not sure if this will cause me a problem at some point, but so far it all seems to be working well, when actually running LinuxCNC and performing some real world initial tests.
Below is what I ended up doing, I am posting steps and my settings below for others that may be new to Linux and struggling with how/where to make the edits.  I have not found anything that walks through all the steps.  If you are using this, just be sure you read the above mentioned article and change the lines that impact the cores.
I don't fully understand all of the settings, but applying all of them noted in the blog post seemed to work for me.
What I did was:Edit Boot Parameters:
- open the terminal
- edit the grub file using nano:  sudo nano /etc/default/grub
- edit one line in grub (put a # in front of the existing GRUB_CMDLINE_LINUX_DEFAULT="quiet" line to comment it out, then make a new line below it.) My new line is: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash skew_tick=1 nosmt=force kthread_cpus=0-1 irqaffinity=0-1 rcu_nocb_poll rcu_nocbs=2-3 nohz=on nohz_full=2-3 isolcpus=2-3 intel_pstate=disable amd_pstate=disable idle=poll cpufreq.off=1 cpuidle.off=1 intel_idle.max_cstate=1 amd_idle.max_cstate=1 nowatchdog nosoftlockup"
- save the file and close out of nano
- update grub: sudo update-grubEdit sysctl parameters:Make a new file for the custom config and add contents to it: sudo nano /etc/sysctl.d/99-custom.conf
- added the following lines: 
kernel.timer_migration=0
kernel.sched_rt_runtime_us=-1
- save file and close out of nano
- I think rebooted computer.

---

Also I experimented with another machine that had an AMD A10 core, but that would result in 2 of the cores showing as inactive in htop,  I think it has something to do with this chip being really 2 chips with dual cores, vs the AMD A8 is a single chip with 4 cores.  I'm sure there is a way to address that, but since the A8 chipped worked out, I never pursued anymore.