Lathe path preview looking strange

More
3 years 4 months ago - 3 years 4 months ago #273463 by alex_sar
Hi all,
that is probably not a gmoccapy but gremlin problem, but I did not find better place to post it.

I've built a lathe cnc based on 2.9 dev branch (RIP build), it works fine except one problem. No matter what I do and what do I do in the gcode, the preview always show a dashed line to some point out of working area. I've never saw it on milling linuxcnc configs.

As I can see the point offset somehow correspond to G54 offsets.

Is it a known problem and is there a way to fix it? 

my ini file:
Code:
 [EMC] MACHINE                 = izh VERSION                 = 1.1 [DISPLAY] DISPLAY                 = gmoccapy #DISPLAY                        = axis CYCLE_TIME              = 0.1 LATHE                   = 1 HELP_FILE               = doc/help.txt POSITION_OFFSET         = RELATIVE POSITION_FEEDBACK       = ACTUAL MAX_FEED_OVERRIDE       = 2.0 MAX_SPINDLE_OVERRIDE    = 2.0 MAX_LINEAR_VELOCITY     = 250 MAX_LINEAR_VELOCITY     = 1 DEFAULT_LINEAR_VELOCITY = 50 DEFAULT_SPINDLE_SPEED   = 100 PROGRAM_PREFIX          = ~/linuxcnc/nc_files INTRO_GRAPHIC           = linuxcnc.gif INTRO_TIME              = 1 INCREMENTS              = 1mm, 0.1mm, 0.01mm, 0.001mm #PYVCP                  = nyx-6.xml [APPLICATIONS] DELAY                   = 1 [TASK] TASK                    = milltask CYCLE_TIME              = 0.01 [RS274NGC] PARAMETER_FILE          = izh.var RS274NGC_STARTUP_CODE   = G18 G7 G21 G40 G43H0 G54 G64P0.005 G80 G90 G94 G97 M5 M9 [EMCMOT] EMCMOT                  = motmod SERVO_PERIOD            = 222242 COMM_TIMEOUT            = 1.0 COMM_WAIT               = 0.010 [HAL] HALUI                   = halui HALFILE                 = nyx.hal HALFILE                 = vfs15.hal HALFILE                 = LIB:xhc-hb04.tcl [NYX] ;PARAMS                 = j4.par PARAMS                  = empty.par AXES                    = 8 VEL_SCALE               = 100 SP_VEL_SCALE            = 100 TRQ_SCALE               = 10 [EMCIO] EMCIO                   = iov2 CYCLE_TIME              = 0.1 TOOL_TABLE              = tool.tbl [TRAJ] COORDINATES             = X Z #NO_FORCE_HOMING        = 1 LINEAR_UNITS            = mm ANGULAR_UNITS           = degree #POSITION_FILE          = izh.pos MAX_LINEAR_VELOCITY     = 80 MIN_LINEAR_VELOCITY     = 0.00001 DEFAULT_LINEAR_VELOCITY = 20 [KINS] KINEMATICS = trivkins coordinates=XZ JOINTS = 2 [AXIS_X] MAX_VELOCITY            = 80 MAX_ACCELERATION        = 680 MIN_LIMIT               = -160 MAX_LIMIT               = 0 [AXIS_Z] MAX_VELOCITY            = 80 MAX_ACCELERATION        = 680.0 MIN_LIMIT               = 84 MAX_LIMIT               = 570 [AXIS_Y] MAX_VELOCITY            = 80 MAX_ACCELERATION        = 680.0 [AXIS_A] MAX_VELOCITY            = 80 MAX_ACCELERATION        = 680.0 [JOINT_0] TYPE                    = LINEAR HOME                    = 0 MAX_VELOCITY            = 80 MAX_ACCELERATION        = 680 BACKLASH                = 0.000 SCALE                   = 10.0 MIN_LIMIT               = -160 MAX_LIMIT               = 0 FERROR                  = 2 MIN_FERROR              = 0.5 HOME_SEQUENCE           = 0 HOME_ABSOLUTE_ENCODER   = 2 HOME_OFFSET             = -81919.00 [JOINT_1] TYPE                    = LINEAR HOME                    = 0 MAX_VELOCITY            = 80 MAX_ACCELERATION        = 680 BACKLASH                = 0.000 SCALE                   = -5.0 MIN_LIMIT               = 84 MAX_LIMIT               = 570 FERROR                  = 2 MIN_FERROR              = 0.5 HOME_SEQUENCE           = 0 HOME_ABSOLUTE_ENCODER   = 2 HOME_OFFSET             = 1133.50
 
Last edit: 3 years 4 months ago by alex_sar.

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #273470 by tommylight

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #273477 by alex_sar
Thanks for response!

Do you mean G92 offsets? That is a new setup and I definitely did not use any offsets besides G54.

But I will check to make sure all possible offsets are zero.

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #273489 by scotth
The HOME_OFFSET values look large. It may be because of the absolute encoders, just a guess.

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago - 3 years 4 months ago #273490 by alex_sar
Yes, I'am using MR-J4-B with absolute encoders, and offset values are correct. I think it should not break anything in UI, and if it breaks it is better to get it fixed.
Last edit: 3 years 4 months ago by alex_sar.

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #273491 by scotth
I don't run gmoccapy, but can you shrink the display enough to see the other end of the dotted box. I believe that is the defined work envelope displayed.

Please Log in or Create an account to join the conversation.

Moderators: newbynobi, HansU
Time to create page: 0.437 seconds
Powered by Kunena Forum