1. Forum
  3. Search

Advanced Search

Search Results (Searched for: )

  • rodw
  • rodw's Avatar
21 Apr 2025 09:48
Replied by rodw on topic First time to try build my xml for not listed ethercat in-out component

First time to try build my xml for not listed ethercat in-out component

Category: EtherCAT

Seems what I expected. 
What happens if you change bitlen to 32 and add ports 9 to 16?
You would need to get rid of the bitlen=8 line too.
  • bkt
  • bkt's Avatar
21 Apr 2025 09:12
Replied by bkt on topic First time to try build my xml for not listed ethercat in-out component

First time to try build my xml for not listed ethercat in-out component

Category: EtherCAT

these seems to work ... But I'm in remote so can not verify hardware result ....  halshow show all work correctly .... only never see op-state of lcsc ... but work on demo-sim-classicladder .... never check if on sim lcec go on op-state or not .....
<masters>
<master idx="0" appTimePeriod="8000000" refClockSyncCycles="1">  
    <slave idx="0" type="generic" vid="0x00000b3d" pid="0x29c9f7b1" name="D1">
      <!--S1-M20-->
      <syncManager idx="0" dir="in"/>
      <syncManager idx="1" dir="out"/>
      <syncManager idx="2" dir="out">
        <pdo idx="1600">
          <!--Output Data-->
          <pdoEntry idx="7000" subIdx="01" bitLen="16" halType="complex">
            <complexEntry bitLen="1" halPin="out-1" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-2" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-3" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-4" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-5" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-6" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-7" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-8" halType="bit"/>
            <complexEntry bitLen="8"/>
          </pdoEntry>
      </pdo>
      <pdo idx="1601">
          <!--Output Data-->
          <pdoEntry idx="7010" subIdx="01" bitLen="16" halType="complex">
            <complexEntry bitLen="1" halPin="out-9" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-10" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-11" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-12" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-13" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-14" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-15" halType="bit"/>
            <complexEntry bitLen="1" halPin="out-16" halType="bit"/>
            <complexEntry bitLen="8"/>
          </pdoEntry>
      </pdo>
      </syncManager>
      <syncManager idx="3" dir="in">
        <pdo idx="1a00">
          <!--Input Data-->
          <pdoEntry idx="6000" subIdx="01" bitLen="16" halType="complex">
            <complexEntry bitLen="1" halPin="in-1" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-2" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-3" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-4" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-5" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-6" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-7" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-8" halType="bit"/>
            <complexEntry bitLen="8"/>
          </pdoEntry>
      </pdo>
        <pdo idx="1a01">
          <!--Input Data-->
          <pdoEntry idx="6010" subIdx="01" bitLen="16" halType="complex">
            <complexEntry bitLen="1" halPin="in-9" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-10" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-11" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-12" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-13" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-14" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-15" halType="bit"/>
            <complexEntry bitLen="1" halPin="in-16" halType="bit"/>
            <complexEntry bitLen="8"/>
          </pdoEntry>
      </pdo>
      </syncManager>
    </slave>
  </master>
</masters>
  • bkt
  • bkt's Avatar
21 Apr 2025 08:24
Replied by bkt on topic First time to try build my xml for not listed ethercat in-out component

First time to try build my xml for not listed ethercat in-out component

Category: EtherCAT

i Try to use these config and seems to work ...
<masters>
<master idx="0" appTimePeriod="8000000" refClockSyncCycles="1">  
    <slave idx="0" type="generic" vid="0x00000b3d" pid="0x29c9f7b1" name="D1">
      <!--S1-M20-->
      <syncManager idx="0" dir="in"/>
      <syncManager idx="1" dir="out"/>
      <syncManager idx="2" dir="out">
        <pdo idx="1600">
          <!--Output Data-->
          <pdoEntry idx="7000" subIdx="01" bitLen="8" halPin="out1" halType="u32"/>
      </pdo>
      <pdo idx="1601">
          <!--Output Data-->
          <pdoEntry idx="7010" subIdx="01" bitLen="8" halPin="out2" halType="u32"/>
      </pdo>
      </syncManager>
      <syncManager idx="3" dir="in">
        <pdo idx="1a00">
          <!--Input Data-->
          <pdoEntry idx="6000" subIdx="01" bitLen="8" halPin="in1" halType="u32"/>
      </pdo>
        <pdo idx="1a01">
          <!--Input Data-->
          <pdoEntry idx="6010" subIdx="01" bitLen="8" halPin="in2" halType="u32"/>
      </pdo>
      </syncManager>
    </slave>
  </master>
</masters>

no w try to divide byte to bit .... hope it work

 
  • bkt
  • bkt's Avatar
21 Apr 2025 08:10
Replied by bkt on topic First time to try build my xml for not listed ethercat in-out component

First time to try build my xml for not listed ethercat in-out component

Category: EtherCAT

Please post the output of lcec_configgen.


is these ..... as you can see little bit too long ...

File Attachment:

File Name: S1-M20.xml
File Size:389 KB
  • unknown
  • unknown
21 Apr 2025 08:07
Replied by unknown on topic Proxxon CU4

Proxxon CU4

Category: General LinuxCNC Questions

USB isn't an option.

Parallel port maybe, but you would have to get Proxxon to confirm.
  • Didi
  • Didi
21 Apr 2025 07:42
Proxxon CU4 was created by Didi

Proxxon CU4

Category: General LinuxCNC Questions

Hi,

I'm a newbie on this forum.
Is LinuxCNC compatible with the Proxxon CU4 interface (via parallel port or otherwise)?
  • dctrytsman
  • dctrytsman
21 Apr 2025 06:47
Lathe with C axis was created by dctrytsman

Lathe with C axis

Category: General LinuxCNC Questions

I decided to make a separate post for this. I have a Mazak Qt20 that is retrofitted with Linuxcnc. Currently I have a x and z axis.I want to mount a live spindle to the turret and use the spindle as the C axis. This spindle drive is a A06b-6044-h011 AC servo drive, I'm not sure what motor it uses, there is no tag on it. The motor drives a gearbox that drives the spindle and the spindle is connected to an encoder that is driven with a toothed belt. The encoder is a Tamagawa RFH1024-22-1m.
How should I connect the components ? Do I need to connect the encoder to the drive, as it currently is, or should I connect it directly to the Mesa card? Is there any other I/O pins that I should connect to or from the drive, other than enable, gnd, -V, 0V? How do I set this up in my INI and Hal configurations? 

I will attach a wiring diagram of the drive. 
  • spumco
  • spumco
21 Apr 2025 04:29
Replied by spumco on topic After homing X and Y, can I auto move to a non 0,0 location?

After homing X and Y, can I auto move to a non 0,0 location?

Category: General LinuxCNC Questions

Switches shared on one input isn't the issue.

I'm trying to determine where the switches are in relation to the table movement so we can make sure that everything moves the correct direction during homing, and if need be move back to a position you want after homing is complete.
  • ffffrf
  • ffffrf
21 Apr 2025 04:13 - 21 Apr 2025 04:20
XZC live tool sherline lathe Post processor: Not reorienting after a step-down was created by ffffrf

XZC live tool sherline lathe Post processor: Not reorienting after a step-down

Category: Fusion 360

This is a long shot but I have been working on a live tool system for my sherline lathe. I am using a tryally QCTP and created a mount for a 33mm 60krpm spindle that I manually control. I modified a hass millturn lathe to output XZC moves only, and modified to use startcode that work with linuxcnc. However, I am noticing an interesting behavior that I am wondering if it is even fixable - it must be, no?The problem: Let';s say I have the endmill parallel to the Z axis, meaning it is in line with the axis of the part (the C axis), and I create a tool path that mills out a wobbly shape out of bar stock, but I need to do it in multiple stepdowns. The post and linuxcnc work as expected for the first stepdown, however, when moving to the next stepdown, it does not reorient itself back to C0, instead it simply continues to mill out the shape exactly where it left off. This means that the second stepped down wobbly shape is some random angle ROTATED from the top (first stepdown) portion. This obviously is not feasible for making parts...However, I am struggling to figure out a solution. One possibility is to try to introduce logic into the post processor that can try and detect when Z distance changes some value and somehow force a reset back to C0 to restart the second stepdown exactly where it needs to, but this seems complex especially if I am going to be varying stepdowns depending on what material I use, what endmill I use, etc.Has anyone thought something like this through? I will upload my Gcode for you all to see. The first stepdown is Z=-6, and the second stepdown starts at Z-10.  

Edit: I added the base Haas post processor that I am using. I almost wonder - shouldnt the post processor have some way of handling this itself? I cant imagine I am the only one trying to do such a cutting move? 
  • RushA
  • RushA
21 Apr 2025 00:55
Replied by RushA on topic A simple question: How to use EXPORT_SYMBOL()

A simple question: How to use EXPORT_SYMBOL()

Category: General LinuxCNC Questions

hi, thanks!
yes, it's C. I did include A.h in B.c, but it doesn't work.
  • pgf
  • pgf
21 Apr 2025 00:53
Replied by pgf on topic After homing X and Y, can I auto move to a non 0,0 location?

After homing X and Y, can I auto move to a non 0,0 location?

Category: General LinuxCNC Questions

@spumco may be onto something? My limit switches are shared: both switches on one circuit. Maybe that's the problem?

@rodw -- My impression and hope was that if I homed to the upper right, I could somehow let the mill know that that point was 12,12 , and that therefore both axes would, yes, count in the negative direction, but not actually ever be negative. They would still go from 0 to 12, but it wouldn't be the 0,0 corner that homing was finding.
Does that make sense?
  • machinedude
  • machinedude's Avatar
21 Apr 2025 00:00
Replied by machinedude on topic Black Friday Deal got me :)

Black Friday Deal got me :)

Category: Plasma & Laser

another update
  • rodw
  • rodw's Avatar
20 Apr 2025 22:04
Replied by rodw on topic Are the program's extents available to the g-code?

Are the program's extents available to the g-code?

Category: General LinuxCNC Questions

 Given that the length of the bit is variable, there is no single actual lower hardware limit. It depends on how far the bit protrudes from the collet. Given that, what's the use of the limit? When would it do me any good?

Adding an upper Z limit switch is usually pretty easy and makes it easy to use Linuxcnc as intended. eg Work in G54 offsets.
Normally, you would jog down so the tool touches the workpiece and set your g54 offset. 
Using work coordinates eg G54 was my biggest learning.
  • rodw
  • rodw's Avatar
20 Apr 2025 21:49
Replied by rodw on topic After homing X and Y, can I auto move to a non 0,0 location?

After homing X and Y, can I auto move to a non 0,0 location?

Category: General LinuxCNC Questions

You have to remember you are dealing with cartesian coordinates.
You can home to any corner you wish. Homing to the lower left of the worktable means all x,y coordinates are in the positive quadrant.
Homing to another corner will mean at least one axis will count in the negative direction. Think of the graphs you drew at school

I did have a machine where the home switch was at max Y but I added a home offset to make the home position at min Y
Thinking about it after using it, I realized I could have homed it at the home switch position so the Y axis would count in the negative direction beecause once you zero G54 offsets at lower left on your workpiece, everything would count in a positive direction anyway.
  • rodw
  • rodw's Avatar
20 Apr 2025 21:36
Replied by rodw on topic Should I switch from AXIS to QtDragon?

Should I switch from AXIS to QtDragon?

Category: Qtvcp

I have plenty, you are welcomed to use them, but i can not guarantee the quality! They do chew on everything in the shop though, seem pretty healthy by the looks and the speed they move through the shop. 

I had one but I bought a better mousetrap and the offending rodent was dispatched in under an hour!
Anybody want a used but battle proven mousetrap I no longer have a use for?
Displaying 121 - 135 out of 26686 results.
  1. Forum
  3. Search
Time to create page: 0.300 seconds
Powered by Kunena Forum