1. Forum
  3. Search

Advanced Search

Search Results (Searched for: )

  • juliankoenig87
  • juliankoenig87
19 Jan 2026 20:02
Replied by juliankoenig87 on topic Mesa 7i96 step ausgangsignal =5V , Schrittmotortriber eingang 12V was nun?

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

Category: Deutsch

Achso. Das Ganze per ULN2803. Und wenn man eh dabei ist nen paar Inputs über TLP292 Optokoppler...
  • juliankoenig87
  • juliankoenig87
19 Jan 2026 19:57 - 19 Jan 2026 20:00
Replied by juliankoenig87 on topic Mesa 7i96 step ausgangsignal =5V , Schrittmotortriber eingang 12V was nun?

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

Category: Deutsch

Moin,

hab das selbe Thema bei meinen Berger Lahr Endstufen. Die benötigen auch 12V. Hab mir für die 7i96(s) dafür eine Adapterplatine gemacht. Mit einem Darlington Array. Für die üblichen 100 bis 200kHz Takt jedenfalls schnell genug. Dazu weil noch Platz war 2 Relais und bissle Kleinkram. Modbus und 0-10V.

Steckt man auf den expansion port. Bin nur noch nicht dazu gekommen das Bitfile zu schreiben. Wenn du Bedarf hast gibt Bescheid. Allerdings hab ich das auf ner 7i96. Falls du zb. eine 7i96s nutzen willst müsste man nochmal ran dann was das Bitfile angeht.

Wie immer auch dort beim ersten Mal kleine Fehler (siehe schiefe Pins) ;-)

Grüße
Julian
  • PCW
  • PCW's Avatar
19 Jan 2026 19:41
Replied by PCW on topic Trying to move from UCCNC to Linuxcnc and using 7i96s but having trouble

Trying to move from UCCNC to Linuxcnc and using 7i96s but having trouble

Category: StepConf Wizard

Can you post your current hal/ini files?

There are basic steps to verify encoder operation

1. Run halshow

2. Select the watch tab and then the 7I96S  encoder position pin and verify that it
increments by 1 for each forward turn of the spindle

If not you need to check the scaling, encoder connections etc

 
  • Studi
  • Studi's Avatar
19 Jan 2026 19:19 - 19 Jan 2026 19:34
Replied by Studi on topic Mesa 7i96 step ausgangsignal =5V , Schrittmotortriber eingang 12V was nun?

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

Category: Deutsch

Meister schrieb:
Du brauchst sowie dochso ein Breakout-Board, die in der Regel einfach den Pin auf Masse ziehen, daher kannst du die Spannung selbst festlegen.

Kannst Du mir das erklären? 

Das Mesa-Bord ist der Takt- und Richtungsgeber, dessen Ausgänge sind TTL Pegel = 5V.  ( Ich denk, die gibt die Spannung vor, oder?)
Die Motorenkarte erfordert aber mindestens einen Pegel von 8-12V. (Die Spannung der Mesa liegt weit unter dem Pegel der von den Eingängen gefordert wird.)
 
  • Mark Kraus
  • Mark Kraus
19 Jan 2026 19:01
Replied by Mark Kraus on topic Trying to move from UCCNC to Linuxcnc and using 7i96s but having trouble

Trying to move from UCCNC to Linuxcnc and using 7i96s but having trouble

Category: StepConf Wizard

I have been trying to get the encoder working for the past 1.5 days.  It is an amt102-v  5 wire a b index.  It worked well in uccnc but all i get when m3 is at speed light comes on.
  • ok
  • ok
19 Jan 2026 17:36
Replied by ok on topic ARE YOU KIDDING ME YOUTUBE !!!

ARE YOU KIDDING ME YOUTUBE !!!

Category: Off Topic and Test Posts

Kind of relevant maybe, I don't want to post it as a new thread / ragebait, but I found it noteworthy enough and wonder what this crowd here thinks:


 
  • TAKUYA
  • TAKUYA
19 Jan 2026 17:30
Replied by TAKUYA on topic Absolute encoder homing

Absolute encoder homing

Category: General LinuxCNC Questions

Hi, having the same kind of issue. Did you find any solution for this?
  • PCW
  • PCW's Avatar
19 Jan 2026 16:50
Replied by PCW on topic 7i80db16 7i85s 7i37 firmware

7i80db16 7i85s 7i37 firmware

Category: Driver Boards

This should work just enable the encoders/stepgens/sserial ports you need in hal
and the I/O beyond the first 7I85S will revert to GPIO.

 

File Attachment:

File Name: 7i80db_16_...sx3d.zip
File Size:172 KB


 
  • PCW
  • PCW's Avatar
19 Jan 2026 15:47 - 19 Jan 2026 15:48
Replied by PCW 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

The error is a hal error, there is only one sserial port in that configuration.

BISS is not related to sserial and is set up differently in the hal file.

The hostmot2 man page describes the driver command line for BISS devices.
Unlike sserial devices, BISS devices are not "discoverable" so need to be setup
with device specific data in the driver command line.

man hostmot2

and scroll down to the BISS section.


 
  • cmorley
  • cmorley
19 Jan 2026 15:25
Replied by cmorley on topic Generating a own Popup

Generating a own Popup

Category: Qtvcp

No, we are customizing qtdragon to load a panel as a pop up and add a button to launch/hide it.
So to add a custom panel you need to add both files to the appropriate folders as I described.

I would suggest you add the qtdragon_handler changes then change the INI to this:

EMBED_TAB_NAME=Vismach demo
EMBED_TAB_COMMAND=qtvcp vismach_mill_xyz
EMBED_TAB_LOCATION=DIALOG

and test.
start qttdragon, on the top left you should see a arrow button - pressing it should show/hide the window that has a 3d milling machine graphic.

if that works then move on to adding the ui and handler of your custom panel (in the described different location) and changing the INI to load it instead.

if there are error messages please quote them exactly.
If you post your vacuum_pimp ui and handler files, I could test them on my end too.
  • NWE
  • NWE
19 Jan 2026 14:53 - 19 Jan 2026 15:21
Replied by NWE on topic Solving the USB Latency Dogma for HMI/MPG: Technical Feedback Request

Solving the USB Latency Dogma for HMI/MPG: Technical Feedback Request

Category: Driver Boards

The 7i73 will allow a reasonable HMI with just one cable as well. A 7i90 with SmartSerial firmware works in the same way.
 

+1
I have used 7i73 and it was really good. I will use 7i73 again whenever a project calls for it. Still, I celebrate everytime additional hardware support shows up for linuxcnc.

As I said, I had thought of doing this myself, but the fact is, I will never find the time to do everything I think of doing. I am really pleased bobwolf is doing this.
  • m.ruefenacht
  • m.ruefenacht
19 Jan 2026 14:24
Replied by m.ruefenacht on topic Jones and shipley cylindrical grinder CNC conversion, grinding camshafts, cranks

Jones and shipley cylindrical grinder CNC conversion, grinding camshafts, cranks

Category: General LinuxCNC Questions

Hello everyone,

Have you continued with the project? I ask because I have written several software programs to generate G-code for grinding camshafts. The software has functions for simultaneous 5-axis grinding. This is necessary to grind conical cams with small concave radii. If you are still interested, I would be happy to help you.
  • sataran
  • sataran
19 Jan 2026 14:09 - 19 Jan 2026 14:52
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=0x00xxxx 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
19 Jan 2026 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
19 Jan 2026 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!!!

 
Displaying 91 - 105 out of 19797 results.
  1. Forum
  3. Search
Time to create page: 0.191 seconds
Powered by Kunena Forum