1. Forum
  3. Search

Advanced Search

Search Results (Searched for: )

  • sataran
  • sataran
Today 14:09 - Today 14:10
Replied by sataran on topic Bitfile or help – Mesa 6i25 + 7i74 (BiSS-C) + 8i20 + 7i70/7i87

Bitfile or help – Mesa 6i25 + 7i74 (BiSS-C) + 8i20 + 7i70/7i87

Category: Driver Boards

Hello again, I was sick for a week, so I didn't make much progress.
My boss want a change in our configuration, he want to replace the 7i70 by a 7i76 connected on the port p2 from the 5i25. I wanted to know if it need a change in the bitfile or if i can use something existent like the file "5i25_7i76_7i74biss3d" that you (PCW) provided here: forum.linuxcnc.org/24-hal-components/551...-biss-encoder#320220?
I tried to read and to understand what was in the vhd but i am not good enough for making it myself...

In order to experiment i already tried to used this existing bit file "5i25_7i76_7i74biss3d" in addition to an existing hal (the two are not from the same project) but i have an issue. When i tried to modify my hal in order to use the two serial port like this:
loadrt hm2_pci config="num_encoders=0 num_pwmgens=1 num_stepgens=5 sserial_port_0=0x0xxxxx sserial_port_1=0XXX"
with p3 => 7i74 = 0 => bissc 3 => 7i87
et p2 => 7i76.
In my understanding my hm2_pci config should be correct and be followed by : hm2_5i25.0.7i76.1.0.input,  hm2_5i25.0.7i74.0.0.something and hm2_5i25.0.7i74.0.3.otherThing? But i get an error: hm2/hm2_5i25.0: num_serials references 2 instances, but only 1 are available, not loading driver ...etc
I dont know if the issue came from the bit file or from the hal.

In the meantime, I will continue reading the hal manual.
Once again thank you for your help!
  • bkt
  • bkt's Avatar
Today 12:27
Kinko ECT coupler was created by bkt

Kinko ECT coupler

Category: EtherCAT

hello at all ... i try to load new coupler kinko etc .... with some in / out analogue in and out relays ... i try to use a custo xml based on pdos and sdos teminal reply .....
<masters>
  <master idx="0" appTimePeriod="1000000" refClockSyncCycles="1">
    <slave idx="0" type="generic" vid="0x00681168" pid="0x52503230" configPdos="true">

      <sdoConfig idx="0x1c12" subIdx="0"><sdoDataRaw data="00"/></sdoConfig>
      <sdoConfig idx="0x1c13" subIdx="0"><sdoDataRaw data="00"/></sdoConfig>
      <sdoConfig idx="0x1c12" subIdx="1"><sdoDataRaw data="0216"/></sdoConfig>
      <sdoConfig idx="0x1c12" subIdx="2"><sdoDataRaw data="0316"/></sdoConfig>
      <sdoConfig idx="0x1c12" subIdx="0"><sdoDataRaw data="02"/></sdoConfig>
      <sdoConfig idx="0x1c13" subIdx="1"><sdoDataRaw data="001a"/></sdoConfig>
      <sdoConfig idx="0x1c13" subIdx="2"><sdoDataRaw data="011a"/></sdoConfig>
      <sdoConfig idx="0x1c13" subIdx="0"><sdoDataRaw data="02"/></sdoConfig>

      <syncManager idx="2" dir="out">
        <pdo idx="0x1602">
          <pdoEntry idx="0x7020" subIdx="0x01" bitLen="8" halPin="out-byte-0" halType="u32"/>
          <pdoEntry idx="0x7020" subIdx="0x02" bitLen="8" halPin="out-byte-1" halType="u32"/>
        </pdo>
        <pdo idx="0x1603">
          <pdoEntry idx="0x7030" subIdx="0x01" bitLen="8" halPin="relay-byte-0" halType="u32"/>
        </pdo>
      </syncManager>

      <syncManager idx="3" dir="in">
        <pdo idx="0x1a00">
          <pdoEntry idx="0x6000" subIdx="0x01" bitLen="8" halPin="in-byte-0" halType="u32"/>
          <pdoEntry idx="0x6000" subIdx="0x02" bitLen="8" halPin="in-byte-1" halType="u32"/>
        </pdo>
        <pdo idx="0x1a01">
          <pdoEntry idx="0x6010" subIdx="0x01" bitLen="16" halPin="analog-0" halType="s32"/>
          <pdoEntry idx="0x6010" subIdx="0x02" bitLen="16" halPin="analog-1" halType="s32"/>
          <pdoEntry idx="0x6010" subIdx="0x03" bitLen="16" halPin="analog-2" halType="s32"/>
          <pdoEntry idx="0x6010" subIdx="0x04" bitLen="16" halPin="analog-3" halType="s32"/>
        </pdo>
      </syncManager>

    </slave>
  </master>
</masters>

seems to work ... but for obtain the real value of pdos need to use these one ...
<masters>
  <master idx="0" appTimePeriod="1000000" refClockSyncCycles="1">
    <slave idx="0" type="generic" vid="0x00681168" pid="0x52503230" configPdos="true">

      <sdoConfig idx="0x1c12" subIdx="0"><sdoDataRaw data="00"/></sdoConfig>
      <sdoConfig idx="0x1c13" subIdx="0"><sdoDataRaw data="00"/></sdoConfig>
      <sdoConfig idx="0x1c12" subIdx="1"><sdoDataRaw data="0216"/></sdoConfig>
      <sdoConfig idx="0x1c12" subIdx="2"><sdoDataRaw data="0316"/></sdoConfig>
      <sdoConfig idx="0x1c12" subIdx="0"><sdoDataRaw data="02"/></sdoConfig>
      <sdoConfig idx="0x1c13" subIdx="1"><sdoDataRaw data="001a"/></sdoConfig>
      <sdoConfig idx="0x1c13" subIdx="2"><sdoDataRaw data="011a"/></sdoConfig>
      <sdoConfig idx="0x1c13" subIdx="0"><sdoDataRaw data="02"/></sdoConfig>

      <syncManager idx="2" dir="out">
        <pdo idx="0x1602">
          <pdoEntry idx="0x7020" subIdx="0x01" bitLen="8" halPin="out-byte-0" halType="u32"/>
          <pdoEntry idx="0x7020" subIdx="0x02" bitLen="8" halPin="out-byte-1" halType="u32"/>
        </pdo>
        <pdo idx="0x1603">
          <pdoEntry idx="0x7030" subIdx="0x01" bitLen="8" halPin="relay-byte-0" halType="u32"/>
        </pdo>
      </syncManager>

      <syncManager idx="3" dir="in">
        <pdo idx="0x1a00">
          <pdoEntry idx="0x6000" subIdx="0x01" bitLen="8" halPin="in-byte-0" halType="u32"/>
          <pdoEntry idx="0x6000" subIdx="0x02" bitLen="8" halPin="in-byte-1" halType="u32"/>
        </pdo>
        <pdo idx="0x1a01">
          <pdoEntry idx="0x6010" subIdx="0x01" bitLen="16" halPin="analog-0" halType="s32"/>
          <pdoEntry idx="0x6010" subIdx="0x02" bitLen="16" halPin="analog-1" halType="s32"/>
          <pdoEntry idx="0x6010" subIdx="0x03" bitLen="16" halPin="analog-2" halType="s32"/>
          <pdoEntry idx="0x6010" subIdx="0x04" bitLen="16" halPin="analog-3" halType="s32"/>
        </pdo>
      </syncManager>

    </slave>
  </master>
</masters>

problem become create everytime a new .hal file based on new module added .... for obtain bit correctly need to use bitslice component .... that is no so fast .... there is a giude for create a new lcec-kinko-c e lcec-kinko.h library so no need to use bitsile or other component for reading and writing bit?? ... thanks to any help .... (p.s. analogue reading is good) .... for better explaine me I add some pdos reading ....
adm1@db13:~$ sudo ethercat reg_read -p 0 -t uint8 3

0x00 0

adm1@db13:~$ sudo ethercat reg_read -p 0 -t uint8 4

0x08 8

adm1@db13:~$ sudo ethercat reg_read -p 0 -t uint8 3

[sudo] password for adm1:

0x00 0

adm1@db13:~$ sudo ethercat reg_read -p 0 -t uint8 2

0x03 3

adm1@db13:~$ sudo ethercat reg_read -p 0 -t uint8 1

0x00 0

adm1@db13:~$ sudo ethercat reg_read -p 0 -t uint8 0

0x11 17

adm1@db13:~$ sudo ethercat reg_read -p 0 -t uint8 4

0x08 8

adm1@db13:~$ sudo ethercat reg_read -p 0 -t uint8 3

0x00 0

adm1@db13:~$ sudo ethercat reg_read -p 0 -t uint8 2

0x03 3

adm1@db13:~$ sudo ethercat reg_read -p 0 -t uint8 1

0x00 0

adm1@db13:~$ sudo ethercat reg_read -p 0 -t uint8 0

0x11 17

regards
  • tincho80
  • tincho80's Avatar
Today 12:10
Replied by tincho80 on topic Machine from LinuxCNC 2.8.4 to LinuxCNC 2.9.8 not working anymore

Machine from LinuxCNC 2.8.4 to LinuxCNC 2.9.8 not working anymore

Category: Forum Questions

APPLIED SOLUTION:
folders "macros" and folder "python" must be located within the machine folder, although in MyMachine.ini absolute paths to "home/user/linuxcnc/configs/macros and .../python are referenced! That must have changed some where along the way from 2.8.4 to 2.9.8 - I dont know...

MyMachine.ini must contain the following lines in addition, coming from version LinuxCNC 2.8.4 under DISPLAY:
[DISPLAY]
...
CYCLE_TIME = 100
...
DEFAULT_SPINDLE_SPEED   = 500
DEFAULT_SPINDLE_0_SPEED = 500
MIN_SPINDLE_0_SPEED     = 0
MAX_SPINDLE_0_SPEED     = 3000
MAX_SPINDLE_0_OVERRIDE  = 1.2
MIN_SPINDLE_0_OVERRIDE  = 0.5

File vc-postgui.hal must have uncommented lines, which are unused, like following:
net     axis_0_max_vel     vc-p4s.ini.0.max.vel => ini.0.max_velocity
net     axis_1_max_vel    vc-p4s.ini.1.max.vel => ini.1.max_velocity
net     axis_2_max_vel     vc-p4s.ini.2.max.vel => ini.2.max_velocity
#net     axis_3_max_vel    vc-p4s.ini.3.max.vel => ini.3.max_velocity
#net     axis_4_max_vel    vc-p4s.ini.4.max.vel => ini.4.max_velocity
#net     axis_5_max_vel     vc-p4s.ini.5.max.vel => ini.5.max_velocity

now it works!
NO syntax change necessary! just raw and stupid line by line debugging...
many thanks anyway!!!

 
  • tincho80
  • tincho80's Avatar
Today 10:28
Replied by tincho80 on topic Machine from LinuxCNC 2.8.4 to LinuxCNC 2.9.8 not working anymore

Machine from LinuxCNC 2.8.4 to LinuxCNC 2.9.8 not working anymore

Category: Forum Questions

Thank you very much for your quick reply Rod and Tommy!
unfortunately the error message seams to be misleading here. username, machine name, computer name, paths all is the same and double checked.
so I bet it must be an issue with the syntax change. I remember at some point I got the message: "did you mean print (...)"
how do I change the syntax from python2.7 to python3? could you give me a starting point? hint? tool? using AI?
  • billykid
  • billykid's Avatar
Today 09:35 - Today 09:43
7i80db16 7i85s 7i37 firmware was created by billykid

7i80db16 7i85s 7i37 firmware

Category: Driver Boards

Good morning, I would like to replace the DC motors on my CNC. I have three Sanmotion RS2 drivers with 400-watt motors that work. I need firmware for the 7i80db 16 + 7i85s + 7i37. The 7i37 is 50-pole but I can adapt it without any problems.
  • SrLange61
  • SrLange61's Avatar
Today 09:28
Replied by SrLange61 on topic Latency, error finishing read, and IRQ affinity

Latency, error finishing read, and IRQ affinity

Category: General LinuxCNC Questions

I’ve just updated to a Ali 7i92 with a Gecko540 on a old i3 pc, Plenty of ddr3 here. Running rt_setup allows the steppers to run smooth. Without it the motors appeared to be missing some steps. I had some problems running the script to find its a download error, dos2unix fixed the file to run as above. 
Thanks 
srl
  • meister
  • meister
Today 09:04
Replied by meister on topic Mesa 7i96 step ausgangsignal =5V , Schrittmotortriber eingang 12V was nun?

Mesa 7i96 step ausgangsignal =5V , Schrittmotortriber eingang 12V was nun?

Category: Deutsch

du brauchst doch sowieso ein breakout board , die ziehen in der regel einfach den pin auf masse, daher kannst du die spannung selber festlegen.
  • cdamm11
  • cdamm11
Today 08:55
Replied by cdamm11 on topic 6i25 and 7i77 config

6i25 and 7i77 config

Category: Driver Boards

Just to end this topic: i bought a new PC and LCNC booted up. So the issue was proberly that i used a too new PC with buggy/Incompabtible PCI-E.
  • harindugamlath
  • harindugamlath
Today 08:15
Replied by harindugamlath on topic Servo Driven tool changer - How to set up

Servo Driven tool changer - How to set up

Category: Advanced Configuration

my idea is to run two extra joints for this. but don't really know where to start.
  • kello711
  • kello711's Avatar
Yesterday 04:55
XHC-WHB04B-4 config difference was created by kello711

XHC-WHB04B-4 config difference

Category: Advanced Configuration

Is there a difference between the configuration of the XHC-WHB04B-4 and the XHC-WHB04B-6. I understand there may be more buttons on the -6 but I'm more concerned about the core functionality of the MPG wheel, axis selection switch, and the step scale switch. I got it working in Axis sim but not sure I have it working perfectly. I started out with the example config from the documentation page. I did notice that hitting the "W-HOME" button invoked a Macro 4 popup in Axis, which seemed odd.
  • soehlrich
  • soehlrich
Yesterday 04:26
Replied by soehlrich on topic Qtdragon_hd Zero button not zeroing

Qtdragon_hd Zero button not zeroing

Category: General LinuxCNC Questions

  • soehlrich
  • soehlrich
Yesterday 04:24
Replied by soehlrich on topic Qtdragon_hd Zero button not zeroing

Qtdragon_hd Zero button not zeroing

Category: General LinuxCNC Questions

Initialling I was thinking this was simply rounding error, but I think it is something else. The fact that I cant set the Zero properly tells me there is some underlying problem with my configs of some thing the way calulations are being done different with openloop steppers.

Some further info. Always getting following error on Z axis (Joint 2). I have upgrade the PC now and have done all the tuning with the Os and interrupts.

I have been a week now, working every day to try and get this going after upgrading from from I think was 2.4, which seemed to work flawlessly for a good number of years.

I have also tried going back to 2.8.0, but still get the errors and the Zero button not working correctly.

When running a short program with the Z going up and down to cros the top of clamps the program will never run through, it always stops with a joint following error.

The other error i am getting is if I set the Deaband to 0, which it was the steppers are always vibrating.

Wondering if there are other hal file setting that have chnage since the earlier version.

This is driving me insane.

Picture of screen hot in next message showing that the position cmd and the fb are the same.

All help would be greatly appreciated.
  • amanker
  • amanker
Yesterday 04:19
Replied by amanker on topic Remora - Rpi Software Stepping Using External Microcontroller via SPI

Remora - Rpi Software Stepping Using External Microcontroller via SPI

Category: Computers and Hardware

Sorry, I was confused in spi. I assumed that both board use same single spi without seeing it's board pin maps. But after seeing SKR3 pin map I found that it's using separate spi for config and comms. But in Octopus it's same for config and comms. Thanks for pointing out.
  • Edereets
  • Edereets
Yesterday 03:34
Replied by Edereets on topic Startup Question

Startup Question

Category: General LinuxCNC Questions

Simple question that I cannot seem to locate the answer: block blast
No matter what offset I was using when I shutdown LinuxCNC I want my DROs to read 0 after I restart and then home. I can do this with the Touch-Off button in Axis but how do I set my INI/HAL file to clear offsets when LinuxCNC restarts?

Of is there a mdi input that would have the same outcome?

Thanks,
HH
You can zero offsets on startup by adding a small macro with:G10 L2 P1 X0 Y0 Z0  ; zero G54
 

You can zero offsets on startup by adding a small macro with:
G10 L2 P1 X0 Y0 Z0  ; zero G54

Call it after homing, or set it in your
.ini
under
OPEN_FILE_ON_STARTUP
to run automatically.
  • tommylight
  • tommylight's Avatar
Yesterday 03:00
Replied by tommylight on topic Machine from LinuxCNC 2.8.4 to LinuxCNC 2.9.8 not working anymore

Machine from LinuxCNC 2.8.4 to LinuxCNC 2.9.8 not working anymore

Category: Forum Questions

Rod seems on the right track, there are several missing files that might be there but will not be found as it seems the user name and subsequently the file path was different.
Old user name was
cncmrue
Displaying 1 - 15 out of 19939 results.
  1. Forum
  3. Search
Time to create page: 0.378 seconds
Powered by Kunena Forum