Advanced Search

Search Results (Searched for: )

  • Cant do this anymore bye all
  • Cant do this anymore bye all's Avatar
17 Jan 2025 07:58 - 17 Jan 2025 08:22
Replied by Cant do this anymore bye all on topic LinuxCNC on Intel Clear Linux

LinuxCNC on Intel Clear Linux

Category: Installing LinuxCNC

I think
—enable-non-distributable
switch when running configure may help.



Here's my opinion on latency.
For mesa cards epp\pci\pcie\ethernet\spi (rpi platform) or similar motion cards (seems to be a few more of these projects around now) where a base thread is not required it a little say loose, up to a certain point. I may be one of the few Luddites that still considers EPP an alternative .
It's when the Linuxcnc machine generates the step\dir signals and read encoders requiring a base thread that things get tight.
Even a i5-3470 machine from about 2012/2013 can perform fine when having to produce step\dir signals. (btw I found this machine on the side of the road, someone had put it out for "council" cleanup.)

@Tommy Slackware was my goto disrto for years, but I got a little tired of having to build missing libs and such to install a new piece of software. The last time I used Redhat was version 9, back in the days when you had to do some weird stuff to use wifi, some of which was using windows drivers, in some way or another, that's right ndiswrapper.
  • hmnijp
  • hmnijp
17 Jan 2025 07:56

Error message "Radius to end of arc differs....etc etc"

Category: General LinuxCNC Questions

What a coincidence! 
Just yesterday I was experimenting with this parameter and noticed that the value cannot be increased.
It's really only in the range of
#define CENTER_ARC_RADIUS_TOLERANCE_MM (2 * 0.01 * M_SQRT2)
#define MIN_CENTER_ARC_RADIUS_TOLERANCE_MM 0.001
rs274ngc_pre.cc
0.001 < tolerance < 0.0225


I wanted to disable the ARC_RADIUS_TOLERANCE constraint and see how interpolation works with a large difference between the start and end radius. This could be used to do spiral interpolation by extending the g-code to g2.1 / g3.1 - just copy interp_arc.cc, but there would be no radius difference check.

 
  • besriworld
  • besriworld
17 Jan 2025 07:50
Replied by besriworld on topic Rotating Axis Controlled by a Ballscrew

Rotating Axis Controlled by a Ballscrew

Category: Basic Configuration

Alright, I will list some disadvantages that I see. There are more moving parts and more expensive bearings. The ball screw needs to have a large diameter and be of a high grade. The biggest drawback of this drive system is that it will create not only axial loading on the screw but also radial loading. In other words, the play will depend significantly on the size of the screw.
If you decide to go another route I can give some ideas
  • Gautham
  • Gautham
17 Jan 2025 06:30
Replied by Gautham on topic Rotating Axis Controlled by a Ballscrew

Rotating Axis Controlled by a Ballscrew

Category: Basic Configuration

Hi,

Thank you all for your contribution. I apologise for not giving enough information here so let me correct that by sharing this video of the mechanism in motion.



Secondly, Timo you are absolutely correct about the pros and cons you listed. The cost is lower than a harmonic drive, the torque is greater due to the huge ratio. In this example over the range of travel, the average ratio of the stepper motor rotation to the b-axis is 85.2 and at a speed of 500RPM it takes 2.55s to do a full 90-degree sweep which is fine for me. If I need it to be faster I can change the ration by changes the ballscrew lead.

The thing I wanted to mention here is that the relationship between the ballscrew travel and the angle of the b-axis can be defined by a function rather than a mapping in order to get an exact and accurate relationship. It is similar to the relationship between the travel of a piston and the angle of the crankshaft, as explained in the video below.



Is there anyway I can insert this function into LinuxCNC?
  • xenon-alien
  • xenon-alien's Avatar
17 Jan 2025 06:21 - 17 Jan 2025 07:02
Replied by xenon-alien on topic Carousel with step motor

Carousel with step motor

Category: Advanced Configuration

@spumco
Thanks for the information and the files!
But now i have just 1 sensor - the index (sense-0).
There are no pocket sensor for sense-1.
Need i put one more sensor for pocket?
I thought 1 sensor enough for a stepper type control mode to home the "axis" and the position of each tool is known.
Before there was a KFLOP system with tool change in the config file
[code][code]#include "KMotionDef.h"
#define TMP 10 // which spare persist to use to transfer data
#include "C:\KMotion434j\C Programs\KflopToKMotionCNCFunctions.c"
 
//-----------------------------------------
//      LINEAR TOOL CHANGING
//-----------------------------------------
#define AXISX 0
#define AXISY 1
#define AXISZ 2
#define AXISB 4
 
//---------Absolute position of tool holders
#define HOLDER_B_1 18.28
#define HOLDER_B_2 48.28
#define HOLDER_B_3 78.28
#define HOLDER_B_4 108.28
#define HOLDER_B_5 138.28
#define HOLDER_B_6 168.28
#define HOLDER_B_7 198.28
#define HOLDER_B_8 228.28
#define HOLDER_B_9 258.28
#define HOLDER_B_10 288.28
#define HOLDER_B_11 318.28
#define HOLDER_B_12 348.28

#define HOLDER_Y -151
#define HOLDER_Z -147.68
 
// absolute position of the tool height setting plate
#define SOFT_LIMIT_X_SHIFT_POS 700
#define SOFT_LIMIT_Y_SHIFT_POS -151 
 
// absolute position to move to that is permanently unobstructed, and safe to move down in Z
#define TOOL_CHANGE_SAFE_POS_X  753 
#define TOOL_CHANGE_SAFE_POS_Y -151
#define TOOL_CHANGE_POS_X 819.34  
#define TOOL_CHANGE_POS_Y -151 
#define AXIS_SAFE_DISTANCE_X 600  // distance in mm to approach tool holder
#define Z_1 -1
//---------
 
//--------- Spindle IO bits
#define CLAW_EJECT 52       // IO bit to eject tool from spindle (KONNECT OUTPUT 10)
#define SPINDLE_CLEAN 51    // IO bit to blow air out of spindle taper (KONNECT OUTPUT 11)
#define CLAW_LOOSE 1041     // IO bit to sense whether the claw has ejected (KONNECT INPUT 24)
#define TOOL_SENSE 1040 
#define CHENGER_OPENED 1042
#define CHENGER_CLOSED 1043
#define OPEN_CHENGER 58
#define CLOSE_CHENGER 59
    // IO bit to sense whether the a tool is in the spindle (KONNECT INPUT 24)
//---------
 
#define TOOL_VAR 9          // Tool changer desired new tool Var
 
// Tool changer Last tool loaded is saved globally in this Var
#define LAST_TOOL_VAR 8     //  -1=Spindle empty, 0=unknown, 1-12 Tool Slot loaded into Spindle
#define TOOL_DISK_FILE "C:\\KMotion434j\\C Programs\\User\\temp\\ToolChangerData.txt"
 
 
#define CLAMP_TIME 2.0      // seconds to wait for the clamp/unclamp
#define CHANGER_OPENING_TIME 2.0  // seconds to wait for the OPEN/CLOSE CHANGER
#define TOOL_HEIGHT_BIT 1055    //bit to read tool height plate (KONNECT INPUT 31)
 
#define SAFE_HEIGHT_Z 10 
#define SAFE_HEIGHT_Z1 100  // relative distance in mm to move to clear the top of the tool taper
#define TOOL_RETRACT_SPEED_Z 45.0    //speed in mm/second to move spindle up after tool has been ejected
 
#define SlowSpeed 150.0 //mm/sec
#define SlowSpeedB 80 //deg/sec 
#define Time_to_open 2 
float S=0;
[/code]
[/code]
[code][code]I hope the home-offset will be fine in my case

P.S.: My native language is not English and I'm a building engineer. So, the coding part a little difficult for me to understand. Never used those concepts such as velocity mode or position mode and how they differ, or other stuff.
But if there is an example, or description with images, schemes, it much more easier for me. (simple text reading is difficult to understand for me)
[/code][/code]
  • rebelx
  • rebelx
17 Jan 2025 05:54
Replied by rebelx on topic LinuxCNC on Intel Clear Linux

LinuxCNC on Intel Clear Linux

Category: Installing LinuxCNC

One of the developers at Clear Linux team stated the following on Github yesterday:

I did attempt to package this. The biggest issue is that the LinuxCNC team itself thinks one of the produced binaries has a license conflict between GPL2.0 and GPL3.0 when building a binary for redistribution. Since that's what we're trying to do, we're kind of stuck until/unless they fix it or decide that it's not a conflict.


Does anybody know anything about this? I have requested more details about the specific binary.
  • tommylight
  • tommylight's Avatar
17 Jan 2025 02:38

Path display glitching - QTPlasmaC - v1.235.265 QtVCP LinuxCNC v2.9.0

Category: Plasmac

Somehow this slipped through ...
usually driver/graphic/OpenGL issue as OGL is used by gremlin.
What Linux?
Run it from the terminal, does it show OGL errors?
  • Thayloreing
  • Thayloreing
17 Jan 2025 02:07
help to compensate for changes in the rack was created by Thayloreing

help to compensate for changes in the rack

Category: Advanced Configuration

I'm having problems with my houter, the rack I used doesn't have very good cymetry, in some points it measures smaller than it should and in other places it gets bigger, things 2 mm apart, mark all the points where this happens, I wanted to know if Is there any way to change the scale in real time of the machine, or something similar, like when it is in a coordinate where, let's say, the average is getting larger, you can compensate this downwards, to reach the exact measurements at which it should be, no. I wish I had to buy a rack new, would there be any way to compensate for these points on the rack?
  • smc.collins
  • smc.collins
17 Jan 2025 01:17
Replied by smc.collins on topic M6 Remap Lathe (Remap T & ignore M6)

M6 Remap Lathe (Remap T & ignore M6)

Category: General LinuxCNC Questions

operating the turret is different from using carousel. Carousel will help to detect and operate the motor to select the position of the turret, but the remainder of the logic will have to exist outside of the carousel component.
  • rodw
  • rodw's Avatar
17 Jan 2025 01:16
Replied by rodw on topic First Start Up - E Stops

First Start Up - E Stops

Category: General LinuxCNC Questions

this line in your ini file sets the axis to joint assignment starting at joint 0COORDINATES = XYZA
Changing the order here will reassign axes to different joints
Unfortunately pncconf labels stuff in your hal file by axis letters which I find really annoying.
I have been known to rename labels in the hal file to use joint numbers so it can reassign joint order by changing the ini file line I mentioned
  • phillc54
  • phillc54's Avatar
17 Jan 2025 00:48

Error message "Radius to end of arc differs....etc etc"

Category: General LinuxCNC Questions

It seems that the docs differ slightly with the code in regards to CENTER_ARC_RADIUS_TOLERANCE_MM.

The docs  state that the default is 0.00127 yet the code  sets the default to 0.02828. 

It seems that the default value is also the maximum allowed and the minimum allowed is 0.001.
 
  • rodw
  • rodw's Avatar
17 Jan 2025 00:42
Replied by rodw on topic Hypertherm XPR woes

Hypertherm XPR woes

Category: EtherCAT

The hypertherm docs show quite a number of 3000:xx SDO's
Try this
www.hypertherm.com/Download?fileId=HYP182148&zip=False
  • Tntmold
  • Tntmold
16 Jan 2025 22:48

Ethercat build from source - full instructions

Category: EtherCAT

This thread almost worked for me, I have a mismatch between ioctl() version magis is differing: /dev/EtherCAT0: 37, ethercat tool: 33. What is the best way to correct this?
  • Yaroslav
  • Yaroslav
16 Jan 2025 21:38
Replied by Yaroslav on topic M6 Remap Lathe (Remap T & ignore M6)

M6 Remap Lathe (Remap T & ignore M6)

Category: General LinuxCNC Questions

The complexity of the algorithm and the number of tools does not matter. I made 2 tools to easily simulate the situation.
Now I made it on a ladder, improved it so that it works in two directions and works clearly and does not skip tools.
On the carousel component it would be easier.
  • spumco
  • spumco
16 Jan 2025 21:08
Replied by spumco on topic Carousel with step motor

Carousel with step motor

Category: Advanced Configuration

There is documentation for carousel.comp which explains what all the pins are as well as encoder schemes.  I'll admit that without some context or experience not everything is obvious.

In your case, I suggest using encoder mode INDEX.  As long as your proximity sensors & flags provide a tight, repeatable location that should be fine.

Note that the home and pocket signals must be at the pocket center, not between the pockets (as mentioned in your first post).  There can be some offset between the home and pockets, manageable with pin carousel.N.home-offset... but I'd suggest aligning everything as close a possible mechanically.

I've attached my ATC-specific HAL and INI files.  The INDEX encoder scheme does not require carousel.N.scale or stepgen.N.position-scale - those are just for COUNTS mode - but I haven't removed them yet from my config.  You won't need them.

The basic arrangement looks like this:
  • Stepper drive commanded via Mesa stepgen
  • Stepgen in velocity mode
  • Carousel.comp
    • carousel.N.motor-vel connected to stepgen.N.velocity-cmd
    • enable pin connected to a motion.digital-out pin (triggered via g-code subroutine)
    • destination pocket connected to motion.analog-out pin (also set via g-code subroutine)
      • this requires an intermediate conversion from float to s32 (analog-out is float, carousel.N.pocket-number is s32)
    • homed & ready pins connected to motion.digital-in pins (for safety checks during g-code)
    • sense-0 & sense-1 connected to home & per-pocket sensors
    • fwd-dc and rev-dc control rotational speed (along with stepgen.N.maxvel & maxaccel)
    • align-dc & decel-time control the fine-alignment speed

Please let me know if you need some help deciphering the files I sent - there may be a couple signals connected in other HAL files not included here.
Displaying 19681 - 19695 out of 21714 results.
Time to create page: 0.442 seconds
Powered by Kunena Forum