Advanced Search

My axis.ini is as follows:
# EMC controller parameters for a simulated machine.

# General note: Comments can either be preceded with a # or ; - either is
# acceptable, although # is in keeping with most linux config files.

# General section

---

[EMC]

# Version of this INI file
VERSION = 1.1

# Name of machine, for use with display, etc.
MACHINE = LinuxCNC-HAL-SIM-AXIS

# Debug level, 0 means no messages. See src/emc/nml_int/emcglb.h for others
DEBUG = 0x7FFFFFFF
#DEBUG = 0

# Sections for display options

---

[DISPLAY]

# Name of display program, e.g., axis
DISPLAY = dummy

# Cycle time, in seconds, that display will sleep between polls
CYCLE_TIME = 0.100

# Path to help file
HELP_FILE = doc/help.txt

# Initial display setting for position, RELATIVE or MACHINE
POSITION_OFFSET = RELATIVE

# Initial display setting for position, COMMANDED or ACTUAL
POSITION_FEEDBACK = ACTUAL

# Highest value that will be allowed for feed override, 1.0 = 100%
MAX_FEED_OVERRIDE = 1.2
MAX_SPINDLE_OVERRIDE = 1.0

MAX_LINEAR_VELOCITY = 5
DEFAULT_LINEAR_VELOCITY = .25
DEFAULT_SPINDLE_SPEED = 200
# Prefix to be used
PROGRAM_PREFIX = ../../nc_files/

# Introductory graphic
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 5

#EDITOR = geany
TOOL_EDITOR = tooledit

INCREMENTS = 1 in, 0.1 in, 10 mil, 1 mil, 1mm, .1mm, 1/8000 in

[FILTER]
PROGRAM_EXTENSION = .png,.gif,.jpg Grayscale Depth Image
PROGRAM_EXTENSION = .py Python Script

png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python3

# Task controller section

---

[TASK]

# Name of task controller program, e.g., milltask
TASK = milltask

# Cycle time, in seconds, that task controller will sleep between polls
CYCLE_TIME = 0.001

# Part program interpreter section

---

[RS274NGC]

# File containing interpreter variables
PARAMETER_FILE = sim.var

# Motion control section

---

[EMCMOT]

EMCMOT = motmod

# Timeout for comm to emcmot, in seconds
COMM_TIMEOUT = 1.0

# BASE_PERIOD is unused in this configuration but specified in core_sim.hal
BASE_PERIOD = 0
# Servo task period, in nano-seconds
SERVO_PERIOD = 1000000

# section for main IO controller parameters

---

[EMCIO]

# Name of IO controller program, e.g., io
EMCIO = io

# cycle time, in seconds
CYCLE_TIME = 0.100

# tool table file
TOOL_TABLE = sim.tbl
TOOL_CHANGE_POSITION = 0 0 0
TOOL_CHANGE_QUILL_UP = 1

# Hardware Abstraction Layer section

---

[HAL]

# The run script first uses halcmd to execute any HALFILE
# files, and then to execute any individual HALCMD commands.
#

# list of hal config files to run through halcmd
# files are executed in the order in which they appear
HALFILE = core_sim.hal
HALFILE = sim_spindle_encoder.hal
#HALFILE = axis_manualtoolchange.hal
HALFILE = simulated_home.hal
HALFILE = check_xyz_constraints.hal
#HALFILE = cooling.hal

# list of halcmd commands to execute
# commands are executed in the order in which they appear
#HALCMD = save neta

# Single file that is executed after the GUI has started.  Only supported by
# AXIS at this time (only AXIS creates a HAL component of its own)
#POSTGUI_HALFILE = test_postgui.hal

HALUI = 

# Trajectory planner section

---

[TRAJ]
COORDINATES = X Y Z
LINEAR_UNITS = inch
ANGULAR_UNITS = degree
MAX_LINEAR_VELOCITY = 4
DEFAULT_LINEAR_ACCELERATION = 100
MAX_LINEAR_ACCELERATION = 100
POSITION_FILE = position.txt

[KINS]
KINEMATICS = trivkins
JOINTS = 3

# Axes sections

---

[AXIS_X]
MAX_VELOCITY = 4
MAX_ACCELERATION = 100.0
MIN_LIMIT = -10.0
MAX_LIMIT = 10.0

[AXIS_Y]
MAX_VELOCITY = 4
MAX_ACCELERATION = 100.0
MIN_LIMIT = -10.0
MAX_LIMIT = 10.0

[AXIS_Z]
MAX_VELOCITY = 4
MAX_ACCELERATION = 100.0
MIN_LIMIT = -8.0
MAX_LIMIT = 0.12

# Joints sections

---

[JOINT_0]
TYPE = LINEAR
HOME = 0.000
MAX_VELOCITY = 5
MAX_ACCELERATION = 50.0
BACKLASH = 0.000
INPUT_SCALE = 4000
OUTPUT_SCALE = 1.000
FERROR = 0.050
MIN_FERROR = 0.010
MIN_LIMIT = -10.0
MAX_LIMIT = 10.0
HOME_OFFSET = 0.0
HOME_SEARCH_VEL = 20.0
HOME_LATCH_VEL = 20.0
HOME_USE_INDEX = NO
HOME_IGNORE_LIMITS = NO
HOME_SEQUENCE = 1
HOME_IS_SHARED = 1

[JOINT_1]
TYPE = LINEAR
HOME = 0.000
MAX_VELOCITY = 5
MAX_ACCELERATION = 50.0
BACKLASH = 0.000
INPUT_SCALE = 4000
OUTPUT_SCALE = 1.000
FERROR = 0.050
MIN_FERROR = 0.010
MIN_LIMIT = -10.0
MAX_LIMIT = 10.0
HOME_OFFSET = 0.0
HOME_SEARCH_VEL = 20.0
HOME_LATCH_VEL = 20.0
HOME_USE_INDEX = NO
HOME_IGNORE_LIMITS = NO
HOME_SEQUENCE = 1

[JOINT_2]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 5
MAX_ACCELERATION = 50.0
BACKLASH = 0.000
INPUT_SCALE = 4000
OUTPUT_SCALE = 1.000
MIN_LIMIT = -8.0

# Normally the Z max should be 0.000!
# The only reason it's greater than 0 here is so that the splash screen
# gcode will run.
MAX_LIMIT = 0.12

FERROR = 0.050
MIN_FERROR = 0.010
HOME_OFFSET = 1.0
HOME_SEARCH_VEL = 20.0
HOME_LATCH_VEL = 20.0
HOME_USE_INDEX = NO
HOME_IGNORE_LIMITS = NO
HOME_SEQUENCE = 0
HOME_IS_SHARED = 1
 

Here is my config for OMRON R88D-KN04H-ECT. With this config I can change driver mode - velocity or position.
Change vid="0x00000083" pid="0x00000007" to you value.
Default driver in velocity mode <sdoDataRaw data="09"/>, in position mode mast be <sdoDataRaw data="08"/>

Cant do this anymore bye all wrote:

Just got info from 2 suppliers that there are 16GB RPi 5 for sale. No mention of any other hardware updates.

8 gb should be heaps. I havenever used more than 4 gb

Stand by. Trying to make a new pi5 image with all of our learnings
 

The GUI is independent of the kinematics the custom panel on the right side is not strictly required for the functionality.

Oh, it's you again. You do certainly have a talent of making people NOT want to help you.
forum.linuxcnc.org/38-general-linuxcnc-q...89-which-ui?start=30

Just got info from 2 suppliers that there are 16GB RPi 5 for sale. No mention of any other hardware updates.

PCW wrote:

What I would do is get a basic working configuration with pncconf.
This means setting the machine limits, scaling, directions, timings,
velocities, and accelerations. Once this is working I would then worry
about tuning for best performance and  special features like drive fault
operation.

That is, don't get the sandpaper out when you are still in the chainsaw stage.
 

I don't know how to respond to this, other than to say that's exactly what I'm doing.

My advice to you is to improve your documentation, because that is the real issue here. I'm trying not to bother you on the phone or email you directly, but I need to know how this software works, in order to use it. It just isn't set up for a newbie to walk in and paint by numbers, and it should be, for a simple 3-axis benchtop router with Clearpath servos. This should not be a science project.

I have made parts that have been in Space. If you're looking for a test-case for someone willing to follow directions, I'm your guy. I just need the directions!

Thanks for your answer. Can Gmoccapy screen be used for this kinematics?

I'm sorry you find the documentation and help provided inadequate. I'm sure those volunteering their time here to help others like you could easily find more rewarding activities.

--update--

i changed the base period and servo period
base perio is 22000
servo period is 90000
and the scale is 50(1 rotation is 10mm | 10 mm equal 500 pulses it is good)
and i take max 2500rpm for jog speed(25000mm/min)  
when i decrease the base period for example 20000 i take maximum 3000rpm but sometimes program give following error so that 22000 is good

and also when i open the axis program
"Unexpected realtime delay on task 0 with period 22000
This Message will only display once per session
Run the Latency Test and resolve before counting"
What should i do?

Aciera wrote:

@fully_defined
Deleted the twin thread. Having multiple threads about the same topic will invariably cause confusion.
If you want to make the results of the discussion more visible you can edit the first post.

Thanks
 

I wish you hadn't. Some thoughts:

1) You would save yourself a lot of time and energy by creating a default configuration that works for a common machine type, like a router, and then explaining what special considerations should be made to account for unique machine types, rather than the blank canvas it is now.
2) Update the documentation! It's basically useless for unseasoned users, in its current state.
3) You should strongly discourage your half-dozen most prolific forum posters from only partially answering questions, which is more confusing and time-consuming for the person asking the question(s).

I have extremely common, made in USA axis motors and a brand new Mesa Board. This should be a slam dunk, five-minute exercise, plugging in a few values and following explicit instructions, but instead I am several threads deep and I know less now than when I started. Tormach mills have Mesa boards, and run PathPilot, which is just LinuxCNC, so what I'm doing should have already been well-documented.

I made the second thread as a place to store the correct answer in its own little place on the forum, for future reference. Otherwise, I, and whomever else might need the information, would have to wade through several hundred entries of me arguing with people for weeks to get a simple answers to simple questions.

hello PCW
Actually i download ini and hal file from byte2bot com because i bought parallel port rpi hat card from there

the latency test writing

Servo thread(1ms) max interval : 1003960ns | max jitter 3960 ns | last interval ~ 1 000 000 ns

Base thread (25 us) max interval : 30111ns | max jitter 5686 ns | last interval 25000ns

Should I change the base period and servo period values?

Thanks