1. Forum
  3. Search

Advanced Search

Search Results (Searched for: )

  • snowgoer540
  • snowgoer540's Avatar
14 May 2025 22:34
Replied by snowgoer540 on topic Job not showing in position - 2.9.4 - v2.9-238.315

Job not showing in position - 2.9.4 - v2.9-238.315

Category: Plasmac

If you want to set X0Y0 via a user button (or MDI), you can use
G10 L20 P0 X0 Y0

I’m going to be honest, I don’t understand your workflow, or why setting up the laser offset and using the laser button won’t work for you.  

Either I’m doing a bad job of explaining or I need more info about your setup.  Perhaps a picture of your table would help?

Setting up the laser offset sets the relationship between the laser pointer and the torch, as this should never change.  Once that’s set, you will get a LASER button above the axis readouts.  You can then use
this button to set your offsets.  If you don’t want to use it to set a rotation and only X0 Y0 then you just click a few times until it says laser again.  It will then park the torch above where your laser pointer was, and set everything to 0.

What am I missing?  Help me help you :)
 
  • kubes
  • kubes
14 May 2025 22:19 - 14 May 2025 22:20
Digital Inputs (complex data) and generic type was created by kubes

Digital Inputs (complex data) and generic type

Category: EtherCAT

I am trying to use a cia402 generic driver what as digital input that is exposed 0x60FD:00 which is a bit for each input signal 16-31 (I only have 9 so bits 16-25). see: infosys.beckhoff.com/english.php?content...18798074891.html&id=

How do I assign the digital input states to hal pins using the generic type driver and the ethercat-conf.xml?  All the sample I find are using custom defined types.  The pins are exposed to the hal in halshow, but they do not follow their state and also are low, so my guess the config is wrong and not reading the inputs states correctly.

Thanks!!!!!!

here is my sniplet of the slave config:

    <slave idx="1" name="Y" type="generic" vid="00000a88" pid="0a880617" configPdos="true">
      <dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0" />
      <syncManager idx="2" dir="out">
        <pdo idx="1600">
          <pdoEntry idx="6040" subIdx="00" bitLen="16" halPin="controlword" halType="u32" />
          <pdoEntry idx="6060" subIdx="00" bitLen="8" halPin="opmode" halType="s32" />
          <pdoEntry idx="607A" subIdx="00" bitLen="32" halPin="target-position" halType="s32" />
          <pdoEntry idx="60FF" subIdx="00" bitLen="32" halPin="target-velocity" halType="s32" />
          <pdoEntry idx="60FD" subIdx="00" bitLen="1" halPin="pos-neg" halType="bit" />
          <pdoEntry idx="60FD" subIdx="01" bitLen="1" halPin="pos-pos" halType="bit" />
          <pdoEntry idx="60FD" subIdx="10" bitLen="1" halPin="din1" halType="bit" />
          <pdoEntry idx="60FD" subIdx="11" bitLen="1" halPin="din2" halType="bit" />
          <pdoEntry idx="60FD" subIdx="12" bitLen="1" halPin="din3" halType="bit" />
        </pdo>
      </syncManager>
      <syncManager idx="3" dir="in">
        <pdo idx="1a00">
          <pdoEntry idx="6041" subIdx="00" bitLen="16" halPin="statusword" halType="u32" />
          <pdoEntry idx="6061" subIdx="00" bitLen="8" halPin="opmode-display" halType="s32" />
          <pdoEntry idx="6064" subIdx="00" bitLen="32" halPin="actual-position" halType="s32" />
          <pdoEntry idx="60FF" subIdx="00" bitLen="32" halPin="actual-velocity" halType="s32" />
        </pdo>
      </syncManager>
    </slave>



 
  • Murphy
  • Murphy
14 May 2025 22:09
Replied by Murphy on topic Remora - ethernet NVEM / EC300 / EC500 cnc board

Remora - ethernet NVEM / EC300 / EC500 cnc board

Category: Computers and Hardware

Regarding my milling machine and setting up the EC500.
My denford mill is using 12v drivers 
​​that need to sink the 12v to ground to move the axis. 
​​​i tried a bc537 transistor to try and switch the 12v to ground. I originally had this working with a cheap bob. But it seems the ec500 outputs are to low to drive the gate. I'm measuring 3.8v on the ec500's outputs. 
I also tried a IRLZ44n mosfet but that's also the same I can't switch the gate. Both circuits had pull up and down resistors. If I connect 5v straight to the gate (330omh resistor) I can switch the gate and pulse the drive. So I'm thinking the outputs of the EC500 are just not strong enough. 
The IC in the ec500 is the am26ls31. If I connect the differential outputs to a am26ls32 will that restore a 5v stronger signal?
  • PCW
  • PCW's Avatar
14 May 2025 22:04 - 14 May 2025 22:16
Replied by PCW on topic mesa 7i73 4x8 keypad problems on KEY8 input

mesa 7i73 4x8 keypad problems on KEY8 input

Category: Driver Boards

Not sure what's going on, but if I read the memory image
with my programmer, all images (R14,R15,R16) start at 0
  • buergi
  • buergi
14 May 2025 21:48
Replied by buergi on topic mesa 7i73 4x8 keypad problems on KEY8 input

mesa 7i73 4x8 keypad problems on KEY8 input

Category: Driver Boards

Hi, "the friend" here. First of all, thanks Peter, for your support. I've no experience in flashing PICs so far so I'm not sure what the problem is. When I open the hex files in the MPLAB IDE (v8.92) the first 0xffff bytes are 0xff and then the contents of the hexfile starts at offset 0x1000.
When opening the hexfile in a text editor I can at least verify that it does not start at offset 0 but at an offset 0x2000. The first line, for example, reads

:182000004440A8003420EF0060042000E0ECB70020022000E1ECB7008C

From left to right 0x18=24 bytes, offset 0x2000, record type 0x00 = data, then 24 data bytes and one byte checksum.

I'm not sure where the difference between 0x1000 and 0x2000 comes from. But when I read the firmware back with the programmer and save it as a hex file it starts at 0x0000.

:020000040000FA
:10000000D9043700B40900003C0C0000500C00007B

So I assume that maybe in the first 0xfff bytes is something like a bootloader or similar.
The only way I could get the firmware to run was using the lines up to offset 0x2000 from the original firmware read from the board before flashing and combining them with the lines from the file you sent. So when I read the firmware back I get the file I attached (the one named ...readback.hex). The firmware flashed that way runs, is recognized as firmware 16 by LinuxCNC and e.g. the analog inputs work fine, only the matrix_kb doesn't work at all. In the previous firmware 14 only the buttons in column 0 did not work (most probably as they are sampled first).

Regarding the configuration section, I believe it is handled correctly by MPLAB, at least it is read the same way. However it differs in one byte

7I73S16H1.HEX
:0200000401F009
:100000000F000000FF000000070000008300000058
:10001000C50000004000000007000000C300000011
:00000001FF

read back with MPLAB
:0200000401F009
:100000000F00000000000000070000008300000057
:10001000C50000004000000007000000C300000011
:00000001FF

I also noticed that the firmware flashed via upload-eth (named ...before-flashing.hex in the attached zip file) differs in several places from the firmware flashed with the programmer, although, both are version 16, I'm not sure if this is intentional.

I'll try flashing the firmware 14 again tomorrow at check if the matrix_kb buttons, apart from column 0 are working again.
Displaying 16111 - 16115 out of 16115 results.
  1. Forum
  3. Search
Time to create page: 0.617 seconds
Powered by Kunena Forum