Advanced Search

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

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

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.

From the "machine" menu, choose "homing" then the axis you want to home.

tommylight wrote:

Yes i have, but not a default config, it is for NV something or another.
Do you get the dropped connection?
Do you get joint errors?
 

No the connection is stable( joint error only 3 video Youtube+stresstest+rustdesk remote desktop) but i have bad stepper movement.
Try to put:
[JOINT_1]
DIRSETUP   = 150000
DIRHOLD    = 150000
STEPLEN    = 150000
STEPSPACE  = 150000

 and

[STEPGEN]
#150000
DIRSETUP   = 150000
DIRHOLD    = 150000
STEPLEN    = 150000
STEPSPACE  = 150000

and
[STEPGEN]
#150000
STEPGEN_DIRSETUP   = 150000
STEPGEN_DIRHOLD    = 150000
STEPGEN_STEPLEN    = 150000
STEPGEN_STEPSPACE  = 150000

and 

[STEPGEN]
#150000
STEPGEN_1_DIRSETUP   = 150000
STEPGEN_1_DIRHOLD    = 150000
STEPGEN_1_STEPLEN    = 150000
STEPGEN_1_STEPSPACE  = 150000

my driver is a  TB6560 (only for testing not final hardware)
all conf not change the movement



the work is linuxcnc classic engrave test

Nice clean up.

Problem 1: gelöst

Wie hast du das Problem gelöst?
Ich habe den gleichen Fehler.

Eugenius.

Yes, set the same home sequence for both in the ini file.

please post your ini file.

I think it has to do with the 10 bucks stepgen PCB, it also happened before I removed the physical pushbuttons and soldered wires to it.

It's not a big issue, but would be nice if it responds faster.

I have to double check the stepper driver dip switch settings.
If no luck i think it might be possible to put a relay on the EN+/- wire, between the PCB and the stepper driver and just leave the PCB ON constantly, only changing direction by switching the DIR and activating the stepper driver via the Enabled signal.
That could solve it, will test later on. It would send out pulse signal constantly, but can't think of a reason why that would be an issue.