Advanced Search

I will Check again.
and let you know. Is there a terminal command to see witch version is installed?

Best regards,
Ben

Indeed if you set acceleration to 200, the scurve max acceleration will be 400 at inflection point.
Exceeding your max acc off 240.

I get the same error even if all accelerations are set to 100 in the ini file

Hi! This is a lathe with Lichuan Ethercat and mesa 7i96s servodrivers for controlling the spindle with a mesa digital potentiometer mesa processes three encoders, one spindle and two linear for each axis, and it seems to work fine. I was even able to thread the G76 cycle.
I use absolute encoders how do I set up the machine so that the position of the machine is automatically read from the drivers when the machine is turned on?

I don't understand if I have to add something about the hal file, I found this:
linuxcnc.org/docs/stable/html/man/man9/stepgen.9.html
stepgen.1.dirsetup
stepgen.1.dirhold
stepgen.1.steplen
stepgen.1.stepspace

I also found this but I don't know where to put the parameters, I know that this gui is only for the parallel port or am I wrong?

Found out why it delays when switching on.
The stepper driver (HBS57) is disabled by a 3.5V signal to the ENA+/- ports.
When you enable the driver by pulling the voltage signal (directly or via the pulse gen PCB), apparently it takes a bit of time for the driver to react.
This also happens when using a different 5V powersupply.

It does react instantly when you re-apply the 3.5V to the ENA+- ports, instantly stopping the motion.

If I can invert the ENA (Enabled) signal in the driver software, I can switch the opposite by relay to apply a voltage to enable the driver instead of disabling it. But I could get an issue stopping the driver in time if I do that.

I have to figure out how to connect to the driver, never done that before.
 

Chaka!
Today I tested the new i7 Tiny PC Lenovo m910q with previously shown pings and latency, and the machine seems to work fine. Ok, I just made an air milling over 10 minutes, but the whole code went through without motor-position errors. I tried full G0 with 7,5m/min and normal milling feeds with 3,5m/min, no errors anymore.
BTW- WLAN connection was active during the process, without activity, but former constellations had bad influence on ping and latency.
I hope, this is my final post regarding latency and pings. I learned a lot about settings.

Big Thank you to all of you for sharing your knowledge and for helpful comments!
Happy greetings, Hanno

I see that I've updated the information related to the AX5800 card. Now I have some questions:
I see that I created some enable pins. I assume they are to enable the output of each of the step generators. In the XML file for LINUXCNC, these pins appear as BIT, but I don't know how to configure them correctly in the EEPROM generator file. Bit variables don't appear there. In that same file it appears
<pdoEntry idx="6001" subIdx="01" bitLen="32" halPin="Frequency" halType="float-ieee"/>
</pdo>
<pdo idx="1a01">
<pdoEntry idx="6001" subIdx="01" bitLen="8" halPin="DI1" halType="u32"/>
<pdoEntry idx="6001" subIdx="02" bitLen="8" halPin="DI2" halType="u32"/>
<pdoEntry idx="6001" subIdx="03" bitLen="8" halPin="DI3" halType="u32"/>
<pdoEntry idx="6001" subIdx="04" bitLen="8" halPin="DI4" halType="u32"/>

It's not clear to me what function those DI pins have and how they are programmed in the EEPROM generator.

So basically if you select piercing only
1-Make  piercing. 
2- Ask the operator to clean dross.
3 - Ask the operators to change consumables (if the case).
4 - Start cutting with 0 piercing delay.

I use a separate material config for piercing and switch to normal when cutting.
Going a bit further, one could have automatic shift to a piercing-only material config when doing piercing only.
And shift back afterwards.

I'm not good at typical programming languages. I'm best at G-code.

Here, G4 has to be because after reaching the pocket, the READY pin is active so the toolchange procedure runs without moving the engine

Yes, I know that ATC is not a priority, but I'm asking in advance (I'll eventually write ATC on CL .. I think that thanks to the knowledge I've gained from trying to start CAROUSEL, I'll manage, and if not, I'll treat it as an axis and use g-code)

This machine is a challenge because:
I've never used a tool magazine
I've never done anything on servos
I didn't have a Mesa card either
and here it will be all

GUI AXIS

acceleration = floor(max_acc/2)

tommylight wrote:

STEPLEN = 150000
STEPSPACE = 150000
to
STEPLEN = 5000
STEPSPACE = 5000
or
STEPLEN = 10000
STEPSPACE = 10000
As you have it it is way to long so it limits the max velocity a lot and can cause joint errors, depending on the scale and velocity set in the ini file.

 

[AXIS_Y]
MAX_VELOCITY = 175
MAX_ACCELERATION = 2000.0
MIN_LIMIT = -5.0
MAX_LIMIT = 300.0

[JOINT_1]
TYPE = LINEAR
HOME = 0.0
MIN_LIMIT = -5.0
MAX_LIMIT = 300.0
#MAX_VELOCITY = 175
MAX_VELOCITY = 175
MAX_ACCELERATION = 2000.0
STEPGEN_MAXACCEL = 2200.0
SCALE = 160.0
FERROR = 1.0
MIN_FERROR = 0.5
HOME_OFFSET = 0.0
HOME_SEARCH_VEL = 0
HOME_LATCH_VEL = 0
HOME_SEQUENCE = 0
[STEPGEN]
#150000
DIRSETUP = 150000
DIRHOLD = 150000
STEPLEN = 5000
STEPSPACE = 5000

and

[AXIS_Y]
MAX_VELOCITY = 175
MAX_ACCELERATION = 2000.0
MIN_LIMIT = -5.0
MAX_LIMIT = 300.0

[JOINT_1]
TYPE = LINEAR
HOME = 0.0
MIN_LIMIT = -5.0
MAX_LIMIT = 300.0
#MAX_VELOCITY = 175
MAX_VELOCITY = 175
MAX_ACCELERATION = 2000.0
STEPGEN_MAXACCEL = 2200.0
SCALE = 160.0
FERROR = 1.0
MIN_FERROR = 0.5
HOME_OFFSET = 0.0
HOME_SEARCH_VEL = 0
HOME_LATCH_VEL = 0
HOME_SEQUENCE = 0
#[STEPGEN] <

---

need this???
#150000
DIRSETUP = 150000
DIRHOLD = 150000
STEPLEN = 5000
STEPSPACE = 5000

same of the conf with:
#DIRSETUP = 150000
#DIRHOLD = 150000
#STEPLEN = 5000
#STEPSPACE = 5000

If I add a homing switch to the Z axis, will this problem be more easily solved?

Indeed if you set acceleration to 200, the scurve max acceleration will be 400 at inflection point.
Exceeding your max acc off 240.

I will try this, note that this is a difference from LinuxCNCs standard TP where the
acceleration bound in the ini file is obeyed at all points.
(unless you have backlash compensation enabled)

STEPLEN = 150000
STEPSPACE = 150000
to
STEPLEN = 5000
STEPSPACE = 5000
or
STEPLEN = 10000
STEPSPACE = 10000
As you have it it is way to long so it limits the max velocity a lot and can cause joint errors, depending on the scale and velocity set in the ini file.