Advanced Search

I download the filewhen I try to use the pi image i get this errorwhat am I doing wrong?thanks      

So  I just did a Linux watch on the linuxcnc.var file for each change. 
Immediately after I loaded the NGC file the #5223 changed to the -364.743 value. I had previously set
the value to zero before I started linuxcnc.

This is the NGC file that I loaded is as follows:
%
G90 G94 G17 G91.1
G21
(G53 G0 Z0.)
(FACE1)
T36 M6
S12000 M3
G94 G4 P8.
G17 G90
G54
G64 P0.001 Q0.001
M8
G0 X188.156 Y-1.472
Z15.
G0 Z5.

G17
M5
G53 G0 Z0.
(Move Z all the way to the top)
M30
%

Hi PCW,

I was able to get 2.10 installed which I have posted about on the other post.  The output of periodm pins is as follows (just copied and pasted and I tried to clean up some):

    38  u32   I/O            0x00000001     hm2_7i96s.0.periodm.00.averages
    38  float OUT               59.1607       hm2_7i96s.0.periodm.00.duty_cycle
    38  float IN                      0               hm2_7i96s.0.periodm.00.duty_cycle_offset
    38  float IN                    100             hm2_7i96s.0.periodm.00.duty_cycle_scale
    38  float IN                      1               hm2_7i96s.0.periodm.00.filtertc_us
    38  float OUT              102354.1      hm2_7i96s.0.periodm.00.frequency
    38  bit   OUT                  TRUE        hm2_7i96s.0.periodm.00.input_status
    38  bit   I/O                 FALSE           hm2_7i96s.0.periodm.00.invert
    38  float IN                      1               hm2_7i96s.0.periodm.00.minimum_frequency
    38  float OUT                  9.77          hm2_7i96s.0.periodm.00.period_us
    38  bit   OUT                  TRUE        hm2_7i96s.0.periodm.00.valid
    38  float OUT                  5.78          hm2_7i96s.0.periodm.00.width_us

I think the pin I am looking for is 'hm2_7i96s.0.periodm.00.duty_cycle'.  This should let me read the duty cycle of the input PWM cycle into pin 29 (which is actually TB2 Pin 13,14 as the naming convention is not complex enough here...).  Do you agree with the assessment? 

Best,
-Dylan

Hi Aciera, 

Yes, that was a pretty silly mistake I made. I figured that out and closed it. I didn't want to post again until I was really stuck.  I was finally able to get 2.10 downloaded.  It was a little painful and I fed a lot of data from the other forum post into chatGPT and we had to update a key and make a file.  But it seems to be working. 

It did give me an error when I opened the GUI, I think this is related to gcode image that it loads up during startup as that is now missing? I am able to open the GUI after exiting the warning though.  Hopefully this warning does not cause issues. 

For now I am going to call this a success unless someones has a concern about said error. 

Thank you.

Best,
-Dylan

 

Based on this single probe attempt, what is causing the VAR _z to be -364.743 that I have highlighted in RED below?
All I did was turn on the machine and home it.

 --- QtVCP Screen Started on: Sat, Dec 28 2024 11:48:10 AM ---
 --- QtDragon_hd Version 1.5 on Linuxcnc 2.10.0~pre0 ---
 11:48:11 Machine OFF
 11:48:11 Hard limits tripped
 11:48:11 Tool 0: No Tool
 11:48:32 Machine ON
 11:48:57 Hard limits tripped
 11:48:57 Hard limits tripped
 11:49:04 Hard limits tripped
 11:49:04 Hard limits tripped
 11:49:09 Hard limits tripped
 11:49:09 Hard limits tripped
 11:51:28 Loaded tool 99
 11:51:28 Tool 99: 3D Probe
 11:51:37 Cannot switch pages while in AUTO mode
 11:51:43 Versa Probe: Start Cycle: Go to Tool Setter
 11:52:52 Versa Probe: Start Cycle: Probe Tool Setter Z Height
 11:53:21 HISTORY Tool Setter height Z[-132.446]
 11:57:20 Versa Probe: Start Cycle: Probe Z Height of material
 11:57:30 HISTORY Probe Material Top Z[-94.743]
 11:58:07 Loaded program file : /home/andy/uploads/Tool-change-TEST-2.ngc
 11:58:07 Loaded file /home/andy/uploads/Tool-change-TEST-2.ngc
 11:59:59 Saved: /home/andy/uploads/Tool-change-TEST-2.ngc
 11:59:59 Loaded file /home/andy/uploads/Tool-change-TEST-2.ngc
 12:00:34 Started program from line 1
 12:00:38  

---

Program Begin PROBE

---

 12:00:38  Current Coord System: 540.000000
 12:00:39  G43 Tool Offset:  0.000000
 12:00:39  Current Selected Tool: 36.000000
 12:00:39  Current Selected Pocket: 36.000000
 12:00:39  Current Tool Loaded: 99.000000
 12:00:39  Current Tool Index:  99.000000
 12:00:39  Orig Tool Z position local_start_z: 364.743000
 12:01:59 Tool 36: Sharpro SPWS2LXD3.22 Down cut 1/8" Shan
 12:02:33 Run timer stopped at 00:01:59
 12:02:33 Tool 36: Sharpro SPWS2LXD3.22 Down cut 1/8" Shan
 12:02:33  

---

FINAL PROBE BACKOFF

---

 12:02:34  Z value detected 5063: 217.447440
 12:02:34  Setting tool 36.000000 Z to 255.144440
 12:02:34  

---

FINAL PROBE

---

 12:02:34  Current Tool Z Offset 5403: 255.144440
 12:02:34  Probe Height: -132.4400
 12:02:34  Block Height: -94.7430
 12:02:34  Probe Result: 217.4474
 12:02:34  5063        : 217.4474
 12:02:34  Tool          : 36.000000
 12:02:34  5400          : 36.000000
 12:02:35  Return to original tool-tip position using new z-offset: 45.666690 , 95.252380 , 364.743000
 12:02:35 Linear move on line 271 would exceed Z's positive limit
 12:02:35 Linear move on line 271 would exceed joint 3's positive limit
 12:02:35 invalid params in linear command
 12:02:35 Abort Parameter is [3]
 12:06:48 Machine OFF
 

Sorry I forgot that information, I'm using the axis interface

Grotius wrote:

@RDA,

Here you see a xyz + a move. Using a blend radius in the corner.

 

I propose 4 variants of one trajectory for testing, which will show the problem of smoothing more than 3 axes
- g2 circle
- polyline circle
- g2 circle + AB axis
- poliline circle + AB axis

In the current version of TP you can clearly see the difference between the speed on the polyline, (which is as fast as the G2 circle), and how much slower the speed will be when the AB axes are connected. Ideally they should all run at the same speed.
 
 

Are there any issues using a intel nuc to run Linux Cnc?

the type of gui should not interfere with the kinematics.

make sure you close the synaptic package manager window before you try to update from the terminal.

stdglue.py
about line 317
 _combat = {
emccannon.CANON_PLANE_XY :
There are entrys for zr
According the manual,  deijkpqr are free for use as argspec
In my remap, i got the error on the second set of coordinates, named parameter #<d> not found.
I extended the entry for emccannon.CANON_PLANE_XY   by  "d","e","i","j","k","p","q","r"
Any reason that is not default? or shouldnt i have done that?
At least it is working now, in the sim

Update: I am getting a similar error every direction I try to do this from.  The error is similar to 'Could not get lock on /var/lib.dpkg/lock-frontend. It is help by process 1736 (synaptic)'

Does anyone have any idea what is goin on with this? lol

It would help to know what GUI you're using. You can reload with the hal interface.

JT

Hi all,

I changed a bit my workflow due to the usage of a new GUI (Basic Probe), my new workflow require my machine to have a precise and consistent Z axis zero point.

ATM, I only have a small Omron tactile switch has it was just used as approx. boundaries.

What could I use to achieve a better axis homing ? IR Sensor ? Special tactile switch ? 

Any recommandation that doesn't cost an arm and is easy to setup is welcome

Thank you.

Is there a pin to link an external button to reload the gcode that is already loaded? I did a probe but whenever I do the probe I have to reload the gcode for the viewer to go to the right coordinate, I looked for a pin to link an external button but I couldn't find it, does anyone know if it exists?