Advanced Search

if you can change things on the sindle (rpm, direction, etc) without turning the spindle on.....and your arduino works perfectly. Then when you turn the spindle on nothing works or works poorly, you likely have an emi issue not a software one.

lookup emi protection for more details but in general. shielded wires grounded on one end only. avoid running wires parallel, when they need to cross cross at 90 degrees, ferrite chokes, use different power supplies. make sure no ground loops (computers are often grounded), etc

In general that's why arduinos are rare in the industrial world. not because they cant work, but because hardening them against emi is much harder and more time consuming than a board designed to work in those enviroments. e.g. mesa, plc's, etc 

jimmyrig wrote:

On another note what's the process for editing the UI? seems like the files are under the /lib folder. load them up in qt, edit and restart? I'm sure its more involved than that but not sure where to begin.
looking at adding an axis for the rotary (A) and bar feed (U) and need corresponding home buttons and read outs.

The A axis dro and buttons will appear if it is a valid axis in the config, currently XYZABC axes are catered for.


For customising the UI, it is best to do it with a USER_COMMAND_FILE in python if possible as this will not get overwritten by any future updates. If the update issue doesn't bother you then the UI is a Qt Designer file and the handler file is a python file.

linuxcnc.org/docs/devel/html/plasma/qtpl...#_custom_python_code

was also thinking of playing around with blue line thickness that shows torch travel between cuts. Sometimes they can be hard to find if needing to restart.

The preview uses the QtVCP GCodeGraphics widget, I think you can change the colours but not the thickness. You may need to dig deeper for that.
linuxcnc.org/docs/devel/html/gui/qtvcp-w...idgets:gcodegraphics

Could it, yes! Does it now? not sure....prob not

linuxcnc being open source gives so many opportunities for advancement and tuning that cannot be done with closed sourced machines.

Your idea is a great one, no reason its not possible, someone just needs to code it. With AI now adays it couldnt be a better time.

id start with a simple python script to record the values every 10th of a second or so (outside of linuxcnc) then tell linuxcnc to stop if those compared values are different (+ some perfentage). once it is working the integration to linux cnc wont be too bad.

Hello PCW,
thanks for your help. I will try another PCI slot soon.

will give that a shot and report back. updated the issue as well.

Was wiring things up today and bricked my 7i96 when uploading firmware. Luckly i had a 7i96s on backup which i would have needed anyways for the BOB. Sending it back to Mesa, they will flash it for free (+shipping). Thanks Mesa!


On another note what's the process for editing the UI? seems like the files are under the /lib folder. load them up in qt, edit and restart? I'm sure its more involved than that but not sure where to begin.
looking at adding an axis for the rotary (A) and bar feed (U) and need corresponding home buttons and read outs.

was also thinking of playing around with blue line thickness that shows torch travel between cuts. Sometimes they can be hard to find if needing to restart.

I think I understand the original problem, fixed it and removed the restriction.
It can be reinstated with an INI switch if wanted.

Pushed to master.

I've got a machining center I'm thinking of retrofitting with linuxcnc and I'm trying to understand the value from a production and automation standpoint.  Looking at the feedback we get from the drives with ethercat has me wondering, would it be possible to record the spindle load for a production job? Could linuxcnc compare the recorded values through the duration of the job and error out if the real time job sees an out of tolerance load? This could be a real time way to monitor broken tools or maybe even worn out tools before they break. 
Maybe this could be done with the axis servos as well. 

What other ideas are there for linuxcnc to help with production automation?

Using user defined parameters:

Result: running as user: mill,
runtime: 7200 seconds,
parameters: --nobase, --base 100000,
prefix for outfiles 1716355190
nglx: 5,

LinuxCNC pc tests, version 20200930, started 22.05.2024 01:21:08
********************************************************************************
Hardware info is logged here: 1716355190.hw.
Latency data is logged here: 1716355190.lat.

General info:
Dell Inc., Vostro 270
Bios version A08, dated 11/23/2012
Chipset: Intel Corporation 7 Series/C216
Harddisk is rotational
The amount of swap currently used is 0
================================================================================
CPU related data:
model name : Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz
cpu cores : 4
stepping : 9
cache size : 6144 KB
================================================================================
RAM related data:
Maximum Capacity: 8 GB
Size: 8 GB
Size: 8 GB
================================================================================
GPU related data:
product: Oland GL [FirePro W2100]
product: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
configuration: depth=32 driver=radeon latency=0 resolution=1920,1080
configuration: driver=i915 latency=0
================================================================================
Parallel port related data:
number of parallel ports is 0
================================================================================
Os and desktop related data:
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"

Should the info below not match with your machine,
kindly post the output of pstree here, including a brief
desciption of your desktop environment, window manager and
display manager. Tia
forum.linuxcnc.org/18-computer/39370-scr...-of-computer-latency

Desktop environment : lightdm
Windowmanager : Xfwm4
Displaymanager : lightdm
================================================================================
Kernel related data:
Kernel 6.1.0-18-rt-amd64
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
Cpu idle driver: intel_idle
================================================================================
Kernel modules data:
Check if pcspkr is loaded: ./lcnc-hw: line 576: [: too many arguments
Yes, may cause bigger latency.
can be eliminated using:
sudo echo "install pcspkr /bin/true" >/etc/modprobe.d/pcspkr.conf
Check if snd modules are loaded: Yes, may cause bigger latency.
can probably be disabled in bios, alternatively, you can run
"./block-snd-modules"
which has just now been created for your convenience.
================================================================================
Keyboard & Mouse related data:
Number of mice: 1
Mouse 0 : Telink Wireless Receiver Mouse
Mice attached to USB:
./lcnc-hw: line 631: lsusb: command not found
Keyboards attached to USB:
./lcnc-hw: line 633: lsusb: command not found
================================================================================
LinuxCNC related data:
LinuxCNC version is: 2.9.2
================================================================================
Preparing for latency test:
Started glxgears No. 1, 2, 3, 4, 5
......ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
....
Started firefox with 'vimeo.com/150574260', WID
================================================================================
STartime = Wed May 22 01:21:22 AM EDT 2024
Command for latency test is:
su mill -c "latency-histogram --nobase --base 100000 --sbinsize 1000 --nox 2>&1 | tee -a 1716355190.lat &"

Latency testing loop started Wed May 22 01:21:22 AM EDT 2024,
should end after Wed May 22 03:21:22 AM EDT 2024
Core 0: +49.0°C (high = +85.0°C, crit = +105.0°C)
Core 1: +48.0°C (high = +85.0°C, crit = +105.0°C)
Core 2: +46.0°C (high = +85.0°C, crit = +105.0°C)
Core 3: +46.0°C (high = +85.0°C, crit = +105.0°C)
done command, retval = 0
.Note: Using POSIX realtime
0 s servo min: -4.400 us max: 5.400 us sdev: 1.600 us
. 1 s servo min: -4.400 us max: 7.100 us sdev: 1.600 us
2 s servo min: -5.500 us max: 7.600 us sdev: 1.600 us
. 2 s servo min: -7.700 us max: 10.100 us sdev: 1.700 us
. 3 s servo min: -7.700 us max: 10.100 us sdev: 1.700 us
4 s servo min: -7.700 us max: 10.100 us sdev: 1.600 us
. 4 s servo min: -7.700 us max: 10.100 us sdev: 1.600 us
5 s servo min: -7.700 us max: 10.100 us sdev: 1.700 us
There are no windows in the stack
Invalid window '%1'
Usage: windowactivate [options] [window=%1]
--sync - only exit once the window is active (is visible + active)
If no window is given, %1 is used. See WINDOW STACK in xdotool(1)
Remaining 0d 1h:59m:55s, press ^C to abort...
6 s servo min: -15.200 us max: 13.200 us sdev: 1.700 us
6 s servo min: -15.200 us max: 13.200 us sdev: 1.700 us
7 s servo min: -15.200 us max: 13.200 us sdev: 1.700 us
7 s servo min: -15.200 us max: 13.200 us sdev: 1.700 us
8 s servo min: -15.200 us max: 13.200 us sdev: 1.700 us
9 s servo min: -23.900 us max: 24.300 us sdev: 1.800 us
9 s servo min: -23.900 us max: 24.300 us sdev: 1.800 us
Core 0: +57.0°C (high = +85.0°C, crit = +105.0°C)
Core 1: +57.0°C (high = +85.0°C, crit = +105.0°C)
Core 2: +54.0°C (high = +85.0°C, crit = +105.0°C)
Core 3: +53.0°C (high = +85.0°C, crit = +105.0°C)
Remaining 0d 1h:59m:50s, press ^C to abort...
10 s servo min: -23.900 us max: 24.300 us sdev: 1.800 us
11 s servo min: -23.900 us max: 24.300 us sdev: 1.800 us
11 s servo min: -23.900 us max: 24.300 us sdev: 1.800 us
12 s servo min: -23.900 us max: 24.300 us sdev: 1.800 us
13 s servo min: -23.900 us max: 24.300 us sdev: 1.700 us
13 s servo min: -23.900 us max: 24.300 us sdev: 1.700 us
14 s servo min: -23.900 us max: 24.300 us sdev: 1.700 us
15 s servo min: -23.900 us max: 24.300 us sdev: 1.700 us
Core 0: +59.0°C (high = +85.0°C, crit = +105.0°C)
Core 1: +58.0°C (high = +85.0°C, crit = +105.0°C)
Core 2: +56.0°C (high = +85.0°C, crit = +105.0°C)
Core 3: +54.0°C (high = +85.0°C, crit = +105.0°C)
Remaining 0d 1h:59m:45s, press ^C to abort...
15 s servo min: -49.500 us max: 35.900 us sdev: 1.700 us
16 s servo min: -49.500 us max: 35.900 us sdev: 1.700 us
17 s servo min: -49.500 us max: 35.900 us sdev: 1.700 us
17 s servo min: -49.500 us max: 35.900 us sdev: 1.700 us
18 s servo min: -49.500 us max: 35.900 us sdev: 1.700 us
19 s servo min: -49.500 us max: 35.900 us sdev: 1.700 us
19 s servo min: -49.500 us max: 35.900 us sdev: 1.700 us
20 s servo min: -49.500 us max: 35.900 us sdev: 1.700 us
Core 0: +61.0°C (high = +85.0°C, crit = +105.0°C)
Core 1: +59.0°C (high = +85.0°C, crit = +105.0°C)
Core 2: +55.0°C (high = +85.0°C, crit = +105.0°C)
Core 3: +56.0°C (high = +85.0°C, crit = +105.0°C)
Remaining 0d 1h:59m:40s, press ^C to abort...

Hi,according to the attachment file .I guess it's called DM3E-556 ?

Here is a modified designer .ui file for qtdragon_hd
put this file in your <configuration folder>/qtvcp/screens/qtdragon_hd/
Name it qtdragon_hd.ui
rename/move/delete the file to go back.

The leds names are led_usr_1 to 4
The labels are label_led_1 to 4
The (check) button names are btn_usr_1 to 6
The pin names will be similar ie qtdragon.led_usr_1

Obviously most of the text is not helpful.
You could use an editor/designer/stylesheets to change the text of the labels.
Hopefully that will get you started.

Chris

If you have another hdd load 2.8.2 and see if that helps. I've got computers that run perfect on Debian 10 but have major latency issue on 12.

Thank you for the explanation, much appreciated, still:

Teknic_Servo wrote:

ClearPath-SDSK servos were designed to be a cost-effective upgrade from stepper systems, and as such were also designed to have torque-speed curves that look like a stepper.

Why?
It does not make sense to cripple a perfectly good servo system like that, it just does not, not design wise, not financially and not usability wise.
Maybe you have your reasons, and the one above might just be one of them, so again thank you for taking the time to explain it.

@Hi Rod,
Yes we can add gcode. We leave the gcode structure intact as is. But add extra info to it.

Will add a Head & Tail to each gcode segment. This are half segments that are tangent to each other.
The Head will get info about it's next gcode segment. Some may be filtered out by the cavalier algo.
This then will solve missing gcode lines when users decide to use G64P100

The cavalier algo is made fertig for 3d operations.
Testing 2 lines in a 3d position :

    cavline l0;
    l0.p0={0,0,0};
    l0.p1={50,50,50};
    l0.bulge=0;

    cavline l1;
    l1.p0={50,50,50};
    l1.p1={100,0,0};
    l1.bulge=0;

Then we create a plane from the given line points. We translate & rotate the line content to topview xy zero.
Then we do the cavaliercontour algo.
Then we translate & rotate the results back to original plane. This far better then any other fillet algo.

 

Hi, I have a Shibaura machine and i want to retrofit but i wonder if the servo drives are analog, pwm or serial. I want to reuse the drives because they seems to work fine.
The machine controller is tosnuc 777-2.​​​​​​

Machine model VMC-55E
Servo drive models are:
AC14I-F
AC28F-D
AJ-28E
I can't find any info of them, pinout or something.Attached some pics of the drives. 

Thank you

​​

I just received 4 of these drives. I hope they work...