Advanced Search

Yes, 7I96/7I96S TB3 pin 12 is the input common.
Isolated inputs accept +-5 to +-36V signals relative to input common.

If you connect +24V to input common, the inputs will be activated
when grounded (connected to the 24V negative output) This
is the normal way to setup the input for NPN sensors
(or switches with a common ground)

Thank you so much for your help, your video helped a lot, I was able to flash on Stlink V2, but how do I install and use pyqcd, I didn't find anything that helped me, I could explain to me, or point someone who has already asked this question to see what He did1

Hello,

I am new to the CNC world, and would like to convert my small-ish lathe to CNC.
I think motors with around 2Nm for Z and around 0.6Nm for X will be sufficient, based on some preliminary measurements. For X I am constrained to Nema 17 size to be able to integrate them well.
For I/O and the spindle encoder, I would like to use a Raspberrry Pi and Beckhoff EtherCAT terminals, which I have already gotten to work (thanks for all the great ressources on here!). I would also like to use EtherCAT-connected drives for the axis (and maybe later the spindle), though I am unsure, which path to take there.

Initially, I was looking at closed-loop stepper drivers such as the Rtelligent ECT60 or the Lichuan CL3-E57H , which close the loop on the driver. But then I also found the Beckhoff stepper terminals  EL7041 and  EL7047 , which would make integration quite elegant as I am already using other Beckhoff terminals. With these however, I am not quite sure if they support closing the loop on the driver. The EL7041 manual mentions some closed-loop control aspects (differing between the standard and the -1000 model), but I don't fully understand what it actually can and can't do. The EL7047 supports closed loop in conjunction with FOC, but it is officially only supported with Beckhoff motors and requires them to be unloaded on startup for referencing. I could not find out if non-FOC closed-loop operation similar to the ECT60 or CL3-E57H is possible as well.
What approach would you recommend here?

In general (e.g. if the Beckhoff drivers can only act as open loop drivers with encoder interfaces), is it advisable close the loop in LinuxCNC when using such an EtherCAT based setup without any FPGA for low level control?

Another option would be AC servo drives (probably the  Lichuan ones due to their comparable cost), at least for the Z axis as I haven't found a Nema 17 sized option that would fit X. These would probably provide better performance, but seem more complex to set up and tune.
What do you think about this alternative?

I am looking forward to your comments, and hope the questions are specific enough. Please let me know if any details are missing.

Best Regards
Daniel

I think I found source of LINUXCNC_CONFIG_PATH:

github.com/LinuxCNC/linuxcnc/blob/ceb434...rc/configure.ac#L702
github.com/LinuxCNC/linuxcnc/blob/ceb434...rc/configure.ac#L724

But I don't know if it will help me in any way.

A friend advised me that it might help if I added the following to pncconf.py:Unfortunately os.environ does not contain 'LINUXCNC_CONFIG_PATH'

  Copy only macros.

Hi, does anyone know how to change the speed sliders so that they stop when released on a touch screen. If I just move a small amount it's fine but if I hold too long they will keep going to the bottom or top of the scale before I can then go back slowly to the speed I want?

It worked with the USER_COMMAND_FILE = filename.py in the last line of the [DISPLAY] section.

I will try what happens if I move it to {RS274NGC]

With the USER_COMMAND_FILE = filename.py at the End of the [DISPLAY] section it works, when I put it in the [RS274NGC] section I cannot see a change.
In my ini file the [RS274NGC] comes after [DISPLAY] (no idea if the position is of relevance)

Greetings Timo 
 

Dear Forum
Time to restart working on my cnc, but I'm facing problems, all my apologies in advance if answers are obvious but I missed them anyway
- Fresh clean install of LinuxCNC (2.9.4) with udpates/upgrades done
- a 6I24 connected to a 7I53 (adhoc bitfile)
- a 6I25 connected to a 7I76 and to a 7I74, itself connected to a 7I70 & 7i71 & 7I73
- both 6I's have PC power disabled and 7i53, 7i76 & 7i74 are powered with 5V
-7i76, 7i70 &  7i71 are also powered with 24V (common com), 7I73 not yet ready

Now with preliminary pncconf config to run linuxcnc, when I run readhmid on the 6i25 it seems that I'm missing some ports and I cannot connect them through pncconf: What am I missing ?

Thanks a lot
Emeric


sudo mesaflash --device 5i25 --readhmid :

Configuration Name: HOSTMOT2

General configuration information:

  BoardName : MESA5I25
  FPGA Size: 9 KGates
  FPGA Pins: 144
  Number of IO Ports: 2
  Width of one I/O port: 17
  Clock Low frequency: 33.3333 MHz
  Clock High frequency: 200.0000 MHz
  IDROM Type: 3
  Instance Stride 0: 4
  Instance Stride 1: 64
  Register Stride 0: 256
  Register Stride 1: 256

Modules in configuration:

  Module: WatchDog
  There are 1 of WatchDog in configuration
  Version: 0
  Registers: 3
  BaseAddress: 0C00
  ClockFrequency: 33.333 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: IOPort
  There are 2 of IOPort in configuration
  Version: 0
  Registers: 5
  BaseAddress: 1000
  ClockFrequency: 33.333 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: QCount
  There are 1 of QCount in configuration
  Version: 2
  Registers: 5
  BaseAddress: 3000
  ClockFrequency: 33.333 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: SSerial
  There are 2 of SSerial in configuration
  Version: 0
  Registers: 6
  BaseAddress: 5B00
  ClockFrequency: 33.333 MHz
  Register Stride: 256 bytes
  Instance Stride: 64 bytes

  Module: StepGen
  There are 5 of StepGen in configuration
  Version: 2
  Registers: 10
  BaseAddress: 2000
  ClockFrequency: 33.333 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: LED
  There are 1 of LED in configuration
  Version: 0
  Registers: 1
  BaseAddress: 0200
  ClockFrequency: 33.333 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for P3
DB25 pin#             I/O   Pri. func    Sec. func        Chan     Sec. Pin func   Sec. Pin Dir

 1                      0   IOPort       StepGen          0        Dir/Table2      (Out)
14                      1   IOPort       StepGen          0        Step/Table1     (Out)
 2                      2   IOPort       StepGen          1        Dir/Table2      (Out)
15                      3   IOPort       StepGen          1        Step/Table1     (Out)
 3                      4   IOPort       StepGen          2        Dir/Table2      (Out)
16                      5   IOPort       StepGen          2        Step/Table1     (Out)
 4                      6   IOPort       StepGen          3        Dir/Table2      (Out)
17                      7   IOPort       StepGen          3        Step/Table1     (Out)
 5                      8   IOPort       StepGen          4        Dir/Table2      (Out)
 6                      9   IOPort       StepGen          4        Step/Table1     (Out)
 7                     10   IOPort       SSerial          0        TXData0         (Out)
 8                     11   IOPort       SSerial          0        RXData0         (In)
 9                     12   IOPort       SSerial          0        TXData1         (Out)
10                     13   IOPort       SSerial          0        RXData1         (In)
11                     14   IOPort       QCount           0        Quad-IDX        (In)
12                     15   IOPort       QCount           0        Quad-B          (In)
13                     16   IOPort       QCount           0        Quad-A          (In)

IO Connections for P2
DB25 pin#             I/O   Pri. func    Sec. func        Chan     Sec. Pin func   Sec. Pin Dir

 1                     17   IOPort       SSerial          1        RXData0         (In)
14                     18   IOPort       SSerial          1        RXData1         (In)
 2                     19   IOPort       SSerial          1        RXData2         (In)
15                     20   IOPort       SSerial          1        RXData3         (In)
 3                     21   IOPort       SSerial          1        TXData0         (Out)
16                     22   IOPort       SSerial          1        TXData1         (Out)
 4                     23   IOPort       SSerial          1        TXData2         (Out)
17                     24   IOPort       SSerial          1        TXData3         (Out)
 5                     25   IOPort       SSerial          1        RXData4         (In)
 6                     26   IOPort       SSerial          1        RXData5         (In)
 7                     27   IOPort       SSerial          1        RXData6         (In)
 8                     28   IOPort       SSerial          1        RXData7         (In)
 9                     29   IOPort       SSerial          1        TXData4         (Out)
10                     30   IOPort       SSerial          1        TXData5         (Out)
11                     31   IOPort       SSerial          1        TXData6         (Out)
12                     32   IOPort       SSerial          1        TXData7         (Out)
13                     33   IOPort       SSerial          1        TXEn7           (Out)




 

The file, saved in the config folder of your machine, must have permission: executable. You can give a more descriptive name with ending py, preferable lowercase letters.
The entry in iniUSER_COMMAND_FILE = filename.py should be in [RS274NGC] section
 

Thanks for reply, I am still trying to figure out what the filename.py should do.

I made a file with the above content with the name filename.py

I added a line in the ini file.

 

This is for discussion about a potential feature which would automatically name/identify signals in HAL. Right now, a signal name always have to be given with the net command. But I see no technical reason why that is the case. New signal names could be generated automatically if none is given. And if trying to connect to a pin which already have a signal connected, that could simply be detected and linked to the already existing signal.

Right now I am using some code like:
I see very little additional value in the signal names geartrain_reverse_OR_stage1-3. It only clutters the "logic". And this clutter gets only worse the more complicated the logic is. Even the gearbox_search_slow provides little value. Instead, it could be like this:At least to my brain, the logic function is in this case easier to read. The net command could the automatically generate signal names where they are not provieded. For instance net_0001, net_0002, net_0003, net_0004 or similar. And if I want to use for instance geartrain.stage2.search_reverse for something else, the "net geartrain.stage2.search_reverse => hm2_7i95.0.7i84.0.0.output-03" command could automatically identify that the signal connected to the pin is named "net_0002" and just add to that same signal.

Similarly, if I want to for instance turn on a light when the spindle should be running, I could simply do "net spindle.0.on => hm2_7i95.0.7i84.0.0.output-01" instead of having to figure out where a signal was first connected to "spindle.0.on" and then use that signal name.

What are other peoples thoughts on this? I do think that giving meaningful names to signals is general good practice. But why force it in cases where "anonymous" signals would make more sense?

Hi,

I have spent a last few days to read a lot of forum posts related to this subject as well as general information on proximity switches. I still have my own questions, since this is completely new to me.

Please help me first with the following question. Page 14 of the Mesa 7I96S manual states:

[
For PNP type sensors or switches with a common positive, the input common pin is grounded and the sensor or switch applies a positive voltage to the input pin to activate the input.

For NPN type sensors or switches with a common ground, the input common is connected to +5 to +36V and the input pins are grounded to activate an input.
]



1. Is **the input common pin** in the two paragraphs above the pin marked in the diagram below?

2. And this pin can take 24V input?

I plan to use 24V NPN NO proximity switch. And I think I understand how to do the wiring.

I will have to seek further helps to check my wiring, too.

Thank you and best regards,

...behai.