Advanced Search

There has been a lot of improvements in Flex GUI the latest is HAL spin boxes. If you preset a value in the spin box when you start the configuration the HAL pin values are updated.

A couple of screen shots of probing





JT

Tommy, We use a 24k 5W resistor as suggested by PCW a long time ago.
You need to calibrate the adjustable voltage on the power supply to be 24 volts.
And you need to monitor the ohmic voltage when configuring it and ensure the ohmic threshold is above the off voltage when the torch is wet.
Initially, Steve had this set too low even though it worked for me.
I was going to ask Steve to try a threshold of 24.9 volts to see how reliable it is as an experiment. I have always seen a full 24 volts on contact.
There are so many advantages of using a THCAD for Ohmic sensing, it would be good if a few like minded people could experiment further.
 

Thank you, Tommy, happy to say that removing the base period and adjusting the FERROR values to 0.1-1.0 has yielded results. The machine has been running my very long test program for quite a few hours now with no issues yet. I will continue testing and gradually increasing the acceleration and velocity.

Hopefully this will be the end of this saga, I will report again after a day or three of thorough testing.

for sure debian SO have as usual some limitations and problem. Think it's worth doing some tests.... I'll do them as soon as I have some time. For now I'm busy understanding the "local" file structure of Debian 12....it seems to be very different from the previous ones....and it's giving me problems....

i did find a dip switch setting that made a difference. SW8 is a pulse filter on is 10ms off is 1.5ms mine were off. After i turned that on the set point signal smoothed out a lot.

one other thing i found was the control loop sets based on the peak current rotary switch. and even if you want to change those the drive will default back when the power is cycled. i did have mine set at 6 but 9 is a better choice based on what the manual is saying. 9 should tighten up the position error signal.

i think the drive knows the power supply voltage and sets your current based on supply voltage. @ 36V i get 4,8A, the drive has a max of 7A but mine only go to 6A with the 36V supply.

no idea if it is up to date:
github.com/itain/Tango-PCB-Kicad

I pushed some work to master to make this easier.
There is a sim demo: gmoccapy_qt_messages

The dialog HAL pins are:

ini_dialogs.VFD
ini_dialogs.VFD-waiting
ini_dialogs.bothtest
ini_dialogs.bothtest-waiting

ini_dialogs.VFD is a S32 and can be set to 0,1,2,3 for three different messages (0 to hide)
ini_dialogs.bothtest is a bit which will show the one dialog message.

Chris

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