1. Forum
  3. Search

Advanced Search

Search Results (Searched for: )

  • PhilipME
  • PhilipME's Avatar
06 Aug 2024 15:29 - 06 Aug 2024 15:36
Replied by PhilipME on topic G53, and G54

G53, and G54

Category: General LinuxCNC Questions

I dont have homing (I bought the limit switches but did not install them yet )

So every start I have to zero x,y,z and that will be my G53 every time.

What I am doing now is G53 G0 x0 y0 then I shut the machine

next start I will set x, y to zero again to set g53 again. For some reason G54 is saved. But it is useless if G53 is lost.

Thanks

Philip


Edit : 

apology

I just realized that my question has no meaning.

I have to install the limit swiches, be able to home, then G54 will work because it is saved.

 
  • OGMaker
  • OGMaker
06 Aug 2024 15:24
Replied by OGMaker on topic [ Vfdmod ] An easy VFD control over MODBUS RTU

[ Vfdmod ] An easy VFD control over MODBUS RTU

Category: HAL

 

File Attachment:

File Name: vfdmod-0.3...md64.zip
File Size:33 KB

It looks lilke aekhv has pulled the project :-( There are are forks of it, but forking doesn't capture the wiki or the project or the releases. I'll attach the debian 3.2 release in case you still want to use it..
  • TheRoslyak
  • TheRoslyak's Avatar
06 Aug 2024 15:21 - 06 Aug 2024 15:22
Replied by TheRoslyak on topic Monitoring SDO value

Monitoring SDO value

Category: EtherCAT

Since no advice was forthcoming, I decided to develop my own component that can monitor and change SDO parameters.
Essentially, this will be a similar component to the one currently working with EtherCAT LinuxCNC but specifically for manipulating SDO data. Unlike the existing driver, it will work with YAML, which is much more convenient than XML.
An approximate example of such a file will be attached. If there are any suggestions, I would be happy to hear them.
I think I will start this week and finish in about a week. Later on, it will be possible to integrate the old functionality for working with PDO.
Although the current one works well, it has its drawbacks.

PS Admins, please add yaml and yml formats to the editor.
  • juliankoenig87
  • juliankoenig87
06 Aug 2024 15:13
Replied by juliankoenig87 on topic Probe panel for Axis GUI

Probe panel for Axis GUI

Category: AXIS

Yeah inches...

Ok. There are two minor things to change. I am currently not at home but can answer later in more detail.

One is the fast forward in between a pocket. Here I use 5 mm to the estimated contact to use faster speed while probing. 5 inches just leads to the fact that there ist no faster movement.

The second one you find yourself. I have some (yes I know quick n dirty programmed) safety functions. In inches the values are way smaller so that the macro thinks that the probe is not calibrated.

Can you show your tool table please.

Julian
  • OGMaker
  • OGMaker
06 Aug 2024 15:11
Replied by OGMaker on topic [ Vfdmod ] An easy VFD control over MODBUS RTU

[ Vfdmod ] An easy VFD control over MODBUS RTU

Category: HAL

If you having trouble finding it, see github.com/thestealth131205/vfdmod

I'm not sure if the project has been hijacked, or the original owner changed his login without realizing the impact on his links. The good part is that the bits are all still there. I'll be making a fork to have a backup in case it goes away...
  • PCW
  • PCW's Avatar
06 Aug 2024 15:01
Replied by PCW on topic 3 Achs Fräse mit MESA 7C80 und Raspi 4

3 Achs Fräse mit MESA 7C80 und Raspi 4

Category: Deutsch

The spindle output is _not_ a PWM output but rather
an isolated analog output used to replace the potentiometer
of a VFD.

If you need a 5V PWM signal, you would need firmware
that includes a pwmgen with an output on a 5V pin

7c801p_5abobd.bit

Is one, this replaces STEP5 with a PWM output

 
  • Lpkkk
  • Lpkkk
06 Aug 2024 14:57
Replied by Lpkkk on topic Positioning issue on remora with nvem

Positioning issue on remora with nvem

Category: Basic Configuration

I've tried different deadband settings by adding to my hal :

setp remora.joint.0.pgain [JOINT_0]P_GAIN
setp remora.joint.0.ff1gain [JOINT_0]FF1_GAIN
setp remora.joint.0.deadband [JOINT_0]DEADBAND

And to my ini in joint 0 section :

P_GAIN = 1
FF1_GAIN = 1
DEADBAND = 0.001

I've tried different values like 1, 0.5, 1.1, all of them didn't change anything.
  • TucsonSean
  • TucsonSean
06 Aug 2024 14:56 - 06 Aug 2024 15:22
Replied by TucsonSean on topic Probe panel for Axis GUI

Probe panel for Axis GUI

Category: AXIS

Ok, two more questions:

First, what is the procedure for using this with a machine set to inches for the units?  I have converted the mm values to inches in the ini files but are there other values that need to be adjusted in other files?

Second, the calibration completes and enters the data into the tool table (I checked the file and there are now X, Y, I and J values added to Tool 99). When I try to do any other probing operatoin, i get the following error: No calibration data found in tool table. Please do a calibration. aborting
I re-ran calibration and now it is working. 

So, my first question still stands.

-Sean
  • TucsonSean
  • TucsonSean
06 Aug 2024 14:44
Replied by TucsonSean on topic Probe panel for Axis GUI

Probe panel for Axis GUI

Category: AXIS

I tried using 2.7 and I kept getting dbounce error and LinuxCNC would not load. I upgraded to 2.8.4 and I did not get the dbounce error any longer.
  • PCW
  • PCW's Avatar
06 Aug 2024 14:41 - 06 Aug 2024 14:42
Replied by PCW on topic Latency Test OK, dennoch Fehlermeldung

Latency Test OK, dennoch Fehlermeldung

Category: Deutsch

So you are saying that changing eno1 coalesce settings affects the other interface?
That's extremely weird

Is it possible both interfaces are sharing an interrupt?

(lshw should show this)
  • Aciera
  • Aciera's Avatar
06 Aug 2024 14:35
Replied by Aciera on topic G53, and G54

G53, and G54

Category: General LinuxCNC Questions

G53 is your machine reference point that is set during homing.
G54 .. g59 should be saved when you exit linuxcnc. At least that is what happens on my installations.
  • PCW
  • PCW's Avatar
06 Aug 2024 14:34
Replied by PCW on topic Hardware advise mesa boards for control-loop with motor-encoder and linear scale

Hardware advise mesa boards for control-loop with motor-encoder and linear scale

Category: Driver Boards

Note that whatever control hardware is used, tuning will be problematic
unless you can remove almost all backlash from the mechanical system.
 
  • Aciera
  • Aciera's Avatar
06 Aug 2024 14:29 - 06 Aug 2024 14:32
Replied by Aciera on topic Need Help in XYZAC configuration.

Need Help in XYZAC configuration.

Category: Advanced Configuration

If things work with the 3d probe but not with other tools then there is likely a problem with your tool table.

What tool z offset have you set your 3 probe to?

May be you can show us your tool table?

[edit]
Also I notice that you use external offsets for the z axis, are those deactivated when you test things?
  • PhilipME
  • PhilipME's Avatar
06 Aug 2024 14:22
G53, and G54 was created by PhilipME

G53, and G54

Category: General LinuxCNC Questions

Is there is a way to save G53, and G54 after turning the machine off?

Thanks
  • amanker
  • amanker
06 Aug 2024 14:17
Need Help in XYZAC configuration. was created by amanker

Need Help in XYZAC configuration.

Category: Advanced Configuration

I have setup 5 axis (XYZAC configuration).
Using QtDragon_HD GUI.
I have measured all offsets using 3D Probe.
And added all offsets in ini file.

When I switch to RTCP mode, Its working nice when I am using that 3D probe. All TCP movements are properly aligned.

But As soon as I change probe to other tool bit of different length. Toolpoint dont follow properly. (I think It needs same length).
I am using manual tool change. Tried measuring tool offsets, Changing tool table. Using G43 to update current tool offset. Nothing worked.

Can anyone guide me proper procedure for this. So that when I change tool, TCP dont misbehaves.
Please outline procedure with sample codes.

Here are settings for kinamatics which are working.
HALCMD = setp xyzac-trt-kins.x-rot-point -85.775
HALCMD = setp xyzac-trt-kins.y-rot-point -110.570
HALCMD = setp xyzac-trt-kins.z-rot-point -16.942
HALCMD = setp xyzac-trt-kins.y-offset 0
HALCMD = setp xyzac-trt-kins.z-offset -38.7445

This is my POSTGUI.HAL
    # load components
########################################################################

loadrt logic names=logic-and personality=0x102
addf logic-and servo-thread

# load a summing component for adding spindle lift and Z compensation
loadrt scaled_s32_sums
addf scaled-s32-sums.0 servo-thread

loadusr -Wn z_level_compensation z_level_compensation
# method parameter must be one of nearest(2), linear(1), cubic (0)
setp z_level_compensation.fade-height 0.0
setp z_level_compensation.method 1

# connect signals
########################################################################

net spindle-speed-limited  =>  spindle.0.speed-out-rps => spindle.0.speed-in

# the unlink pin commands are only used, because they are connected 
# in core_sim.hal and we use this file to simulate
unlinkp iocontrol.0.tool-change
unlinkp iocontrol.0.tool-changed
unlinkp iocontrol.0.tool-prep-number

net tool-change      hal_manualtoolchange.change   <=  iocontrol.0.tool-change 
net tool-changed     hal_manualtoolchange.changed  <=  iocontrol.0.tool-changed
net tool-prep-number hal_manualtoolchange.number   <=  iocontrol.0.tool-prep-number

net eoffset-clear    axis.z.eoffset-clear
net eoffset-counts   axis.z.eoffset-counts
setp axis.z.eoffset-scale .001
net eoffset-total          axis.z.eoffset
net eoffset-total          qtdragon.eoffset-value
setp axis.z.eoffset-enable True

## external offsets for spindle pause function
##################################################
net eoffset-clear     qtdragon.eoffset-clear
net eoffset-spindle-count   <= qtdragon.eoffset-spindle-count    
net spindle-pause     qtdragon.spindle-inhibit spindle.0.inhibit
net probe-input qtdragon.led-probe

## Z level compensation
####################################################
net eoffset-clr2            z_level_compensation.clear      => logic-and.in-01
net xpos-cmd                z_level_compensation.x-pos      <= joint.0.motor-pos-cmd
net ypos-cmd                z_level_compensation.y-pos      <= joint.1.pos-cmd
net zpos-cmd                z_level_compensation.z-pos      <= joint.2.pos-cmd
net z_compensation_on       z_level_compensation.enable-in  <= qtdragon.comp-on
net eoffset-zlevel-count    z_level_compensation.counts     => qtdragon.eoffset-zlevel-count

net eoffset-spindle-count   scaled-s32-sums.0.in0
net eoffset-zlevel-count    scaled-s32-sums.0.in1
setp scaled-s32-sums.0.scale0 1000
net eoffset-counts          scaled-s32-sums.0.out-s

    #loadrt scale names=spindle_amp_scale
    #addf scale.1 servo-thread
    #setp scale.1.gain 9.6 # PWM per RPM, calculated over full scale. Example: 0-100 PWM, 12000 rpm: (100/12000)  = 0.008333
    #net spindle-amp-in spindle.0.speed-out => scale.1.in
    net spindle-amp-scaled scale.1.out => qtdragon.spindle-amps
    setp qtdragon.spindle-volts 48

What I am missing? 
Displaying 21526 - 21540 out of 26067 results.
  1. Forum
  3. Search
Time to create page: 0.455 seconds
Powered by Kunena Forum