Advanced Search

itai wrote:

I am switching LinuxCNC from an old PC to RaspberryPI + Tango compatible board.
I see that riocore has support for HY_VFD and I want to use it. After resolving simple issues I can get a serial signal out of the Tang Nano, but no connectio to the VFD yet. I guess I will need a TTL to RS485 brekout board. Will this one do?

Last time that I made changes to the HY_VFD configuration it cost me a burnt spindle, so now I'm trying to learn more and if possible from other's experience. I will appreciare any help and suggestions.
Thanks!
-- Itai
 

Is your vesion of the Tango board a modified PCB? and is there Kicad or PCB repository.  Just so I can compare the difference with Olivers version.
Many thanks 

"But clearly i don't have the energy to do a good job of it any more."

Note to Sebastian:
There was absolutely no criticism intended. I am super grateful for what you do with buildbot and probably a lot of other stuff I'm not even aware of. Is there a way to distribute some of the workload to those with extra cpu cycles? Kinda like what the SETI program did.
Jim

Seems Seb has fixed it …

sourceforge.net/p/emc/mailman/message/58817616/

The error is from line #4 in the original gcode:

linuxcnc.org/docs/devel/html/gcode/g-code.html#gcode:g53

Hi at all,I installed LinuxCNC 2.8.4 on an old PC (Asrock M68PV-GS, Athlon II X2 250).
As the jitter values ​​are very bad with standard installation and I only use parallel ports, I changed the kernel

uname -a   >>   Linux CNC 4.19.195-rtai-amd64...

I previously used LinuxCNC 2.7 and defining the 2 paports in etc/modprobe.d/alsa-case.conf:

 alias parport_low level parport_pc
options parport_pc io=0xe480, 0xe880 irq=7,11,auto

 But that no longer works with version 2.8 and I get error messages about parallel ports when I start LinuxCNC.
For testing purposes, I added these lines to etc/modprbe.d/ath9k_htc.conf.

I ran the console command

sudo modprobe -a parport_pc

from the >documentation< , which immediately activated the ports and then allowed the machine to be tested successfully
and without errors.
When I restarted the PC, the settings disappeared again.

Can you please help me configure the ports permanently?

Thank you in advance, Yves.

New to Linuxcnc, got my Mesa 7i96 working and able to run Gcode on my DIY CNC without doing any cutting.  The Gode was generated from Fusion 360 with Origin on the TOP Left Corner of the Part.  When i used Mach3, all i do move the tool to the Origin on the part manually and Set G54 offset.  Then program runs.  Will this be the Same in LinuxCNC or it will automatically load some tool offsets from File.  When I tried a to run the program after setting the G54 on TOP-LEFT-CORNER of the part, it moves up in Z and ask me to load a tool.  When press enter it runs the program.

Thanks.

I should also clarify. The only one I use is master branch for bookworm, which no longer exists on either of those buildbot sites. My apt sources list points to deb buildbot2.highlab.com/debian/ bookworm master-uspace but there are no updates.
Jim

Good afternoon.

Using the example provided, I managed to get 1 motor to work... but in my case there are 4 axes. I have already changed the .hal and ethercat.xml and it doesn't work... I follow the example and it crashes again...
They start at 10ry, then I put the cable on and they go to 20ry.
then 1 88ry and the rest 20ry

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.