1. Forum
  3. Search

Advanced Search

Search Results (Searched for: 7i76e)

03 Jan 2024 11:37 - 03 Jan 2024 21:35
Stepper Treiber Alarm Ausgang was created by nobby42

Stepper Treiber Alarm Ausgang

Category: Deutsch

Hallo,
ich bin gerade dabei meine Fräse auf Closed Loop Stepper umzurüsten und bin auf ein Problem gestossen.
Hier die Daten zur Maschine:
LinuxCNC Version 2.8.4
gmoccapy 3.1.3.8
Mesa7i76e
Ich möchte nun die Alarm Ausgänge der Steppertreiber (RTTAM Motor HSS60) nutzen und im Fehlerfall eines Treibers die ganze Maschine bzw. die Treiber abschalten. Ich habe das über Funktion joint.N.amp-fault-in. Leider haben diese Treiber die Eigenheit, dass beim Einschalten der Alarmausgang kurz aktiv ist und daher die Treiber wieder abschaltet werden (habe das aktuell über die Stromversorgung der Treiber gelöst).  Ich habe andere Treiber getestet. Die haben das Problem nicht. Leider passen diese aber nicht zu den Stepper die zum Einsatz kommen.

Meine Idee, ist nun, beim Einschalten der Maschine bzw. der Treiber einen Delay für die Abfrage der Eingänge zu haben. Leider lief meine Suche nach einer Software Lösung bis jetzt ins Leere. Hat jemand eine Idee? Falls das nicht über die Stromversorgung der Treiber funktioniert, kann ich die Funktion joint.N.amp-enable-out für die Deaktivierung der Treiber im Fehlerfall nutzen? Wie würde ich die mit dem estop verknüpfen?
Für die Spindel und den Notaustaster habe ich den estop so gelöst:

net estop-fu => logic.0.in-00 # Mesa Input 20 (Alarm FU) -> logic.0.in-00
#net motor-alarm-z => logic.0.in-01 # Mesa Input 31 (Alarm Z) -> logic.0.in-01
net estop-switch => logic.0.in-01 # Mesa Input 21 (Not aus Schalter) -> logic.0.in-02
net estop-ext <= logic.0.and # IO, sobald ein Eingang (Nothalt oder Z/FU Alarm) auf low ist.
net estop-out <= iocontrol.0.user-enable-out net estop-ext => iocontrol.0.emc-enable-in

Wäre es besser, die Spindelnotabschaltung und den Notaustaster auch über die joint Funktionen zu lösen?

Danke für eure Hilfe.

Norbert
02 Jan 2024 23:41
Looking for feedback on stepgen setup was created by vetsin

Looking for feedback on stepgen setup

Category: Driver Boards

Looking to validate my thoughts on setup here.

For reference, I have: And some assumptions/assertions/questions I have are:
  • Because I have an fpga:
    • I use the HostMot2 driver in a servo thread
    • I don't need to worry about latency (as this is for software stepping)
  • The mesa's step frequency is 0 to 500 kHz
    • I need to calculate my steps/in knowing my steps/rev to thread pitch
    • The pulses then must be less than (500kHz / 1e6) == .5 per μs? For each motor or all three?
  • My drivers Step Pulse times are 2.5 μs, and steps on the falling edge (I think?)
    • I would set the STEPLEN to 2500 and STEPSPACE to 0?
  • My drivers direction setup is 5 μs, but I have no idea what the hold time is? 5 μs also?
    • I would set the DIRSETUP to 5000 and DIRHOLD to 5000?
02 Jan 2024 14:35
Replied by PCW on topic Mesa CT and 7i97T

Mesa CT and 7i97T

Category: Driver Boards

The spindle pins would be:
hm2_7i76e.0.7i76.0.3.spindir
hm2_7i76e.0.7i76.0.3.spinena
hm2_7i76e.0.7i76.0.3.spinout
 and spindle parameters:
hm2_7i76e.0.7i76.0.3.spindir-invert
hm2_7i76e.0.7i76.0.3.spinena-invert
hm2_7i76e.0.7i76.0.3.spinout-maxlim
hm2_7i76e.0.7i76.0.3.spinout-minlim
hm2_7i76e.0.7i76.0.3.spinout-scalemax

You can list all the hardware pins/parameters with:

halcmd show all hm2

(when LinuxCNC is running)
 
01 Jan 2024 15:34
Mes 7i76e Anschluss was created by stoeckl_grisi

Mes 7i76e Anschluss

Category: Deutsch

Servus miteinander,
vor kurzem hab ich auf kleinanzeigen eine Mesa 7i76 bekommen.
In diesem Beitrag  My 7i76e Connection Sheet#85072 hab ich eine gute Anschlussanleitung gefunden.
Da ich auch Nummer sicher gehen will, damit nix kaputt geht, wollte ich die Community nochmal drüber schauen lassen.
Ich hoffe, dass ich nix falsch angeschlossen habe
File Attachment:

 
 
 

Gruß und ein gutes neues Jahr
Christoph
26 Dec 2023 09:13 - 26 Dec 2023 09:15
MESA 7i97T, unable to ping board, strange lamp behavior was created by flyingbrick

MESA 7i97T, unable to ping board, strange lamp behavior

Category: Driver Boards

Hi all.

My card arrived today :-D

This took me some time to figure out what was going on and some time to figure out (well, 99.99% sure) that its not the controlling PC, but is the board itself.
  1. I have setup as per tutorial by Tommylight at www.forum.linuxcnc.org/27-driver-boards/...ethernet-mesa-boards (Thanks!)
  2. I have confirmed that I can connect my PC by ethernet cable to my homes network and ping other devices
  3. i have tried using both the default jumper settings of DOWN DOWN to select 192.168.1.121 as well as DOWN UP to select 10.10.10.10 addresses, all fail to return a ping.
  4. The board flashes as per this video when it is connected to my home network or direct to my control PC
    1. without connection to another device or network, only the yellow power lamp is illuminated.




      I hope someone can give me some tips :-) I have not tried mesaflash or anything like that yet- but it seems pointless if I cannot even get it to ping back to me.

      I hope someone can fire some wisdom my way :-D 

PS, thats my dog snoring in the background, not me breathing, haha
24 Dec 2023 15:52
Replied by PCW on topic mesa 7i96e+7i85s encoder problem

mesa 7i96e+7i85s encoder problem

Category: Driver Boards

If you have only one 7I85S, it should connect to P1

The only disadvantage of using the 7i85sx2 firmware with one
7I85S is that if you need the encoder on the 7I76E, you will
need to enable 9 encoders in the driver command line and there will be
4 wasted encoder accesses every servo thread cycle, though this
only adds a minor amount of time to the communications (about 7 usec)
24 Dec 2023 15:22
Replied by Raban on topic mesa 7i96e+7i85s encoder problem

mesa 7i96e+7i85s encoder problem

Category: Driver Boards

Thanks PCW ,
with 7i76e_7i76x1_7i85sx1D firmware
should i use the p1 or p2 connector?
Is there any problem if I leave the 7i76e_7i76x1_7i85sx2d.bit firmware with only one card?
24 Dec 2023 14:34
Replied by PCW on topic mesa 7i96e+7i85s encoder problem

mesa 7i96e+7i85s encoder problem

Category: Driver Boards

The 7i76E's encoder is encoder 8 with that firmware (the 7I85S card 1 and 2 encoders are 0..3 and 4..7)
If you only have one 7I85S, you can use 7i76e_7i76x1_7i85sx1D firmware, in which case,
the 7I76E encoder will be encoder 4.
24 Dec 2023 09:39
mesa 7i96e+7i85s encoder problem was created by Raban

mesa 7i96e+7i85s encoder problem

Category: Driver Boards

Hi everyone,
I added the 7i85s to the 7i76e and used the firmware
7i76e_7i76x1_7i85sx2d.bit

Encoders 0,1,2,3 on the 7i85s board work fine and all inputs and stepgens on the 7i76e board work too
but the encoder on the 7i76e which was previously encoder 00 now doesn't work.

Encoder 00 has now become encoder 0 on the 7i85s board
In my hal configuration I declared 5 encoders.

Some idea ?
23 Dec 2023 10:02
Replied by rodw on topic select jog axis

select jog axis

Category: AXIS

Here is an example that decodes a 6 axis selector on a pendant that outputs  a 3 bit output (3 pins).  It uses a mux 8 and a select 8)
It also controls feed over ride and rapid override
You have to do a couple of data type conversions to make it work so its a bit long winded.

loadrt mux8 count=1
loadrt select8 count=1
loadrt conv_float_s32 names=pen-conv-float
loadrt conv_s32_bit names=pen-conv-s32

addf mux8.0                   servo-thread
addf select8.0                servo-thread
addf pen-conv-float           servo-thread
addf pen-conv-s32             servo-thread


#Axis Select (0=off, 1=x, 2=z, 3=y, na, 5=6, 6=4, 7=5) 
setp mux8.0.in0 0
setp mux8.0.in1 1
setp mux8.0.in2 2
setp mux8.0.in3 3
setp mux8.0.in4 4
setp mux8.0.in5 5
setp mux8.0.in6 6
setp mux8.0.in7 7
net mux8-sel0 <= hm2_7i76e.0.7i76.0.0.input-13
net mux8-sel1 <= hm2_7i76e.0.7i76.0.0.input-14
net mux8-sel2 <= hm2_7i76e.0.7i76.0.0.input-15
net mux8-sel0 => mux8.0.sel0
net mux8-sel1 => mux8.0.sel1
net mux8-sel2 => mux8.0.sel2

setp pen-conv-float.clamp 0
net mux-float <= mux8.0.out
net mux-float => pen-conv-float.in

net mux-s32   <= pen-conv-float.out
net mux-s32   => select8.0.sel
net axis-select-x <= select8.0.out1
net axis-select-y <= select8.0.out3
net axis-select-z <= select8.0.out2
net axis-select-a <= select8.0.out6
net axis-select-5 <= select8.0.out7
net axis-select-6 <= select8.0.out5

net axis-select-x => axis.x.jog-enable
net axis-select-x => halui.axis.x.select

net axis-select-y => axis.y.jog-enable
net axis-select-y => halui.axis.y.select

net axis-select-z => axis.z.jog-enable
net axis-select-z => halui.axis.z.select

net axis-select-a => axis.a.jog-enable 
net axis-select-a => halui.axis.a.select

net axis-select-5 => halui.feed-override.count-enable 
net axis-select-6 => halui.rapid-override.count-enable 
15 Dec 2023 07:59
Replied by blazini36 on topic Spindle encoder, but encoder is on the motor, 2:1 ratio

Spindle encoder, but encoder is on the motor, 2:1 ratio

Category: Basic Configuration

Here is my mill's hal file. My spindle is setup as a 2:1 reduction so you're obviously have to scale it the other way. I have a custom panel on Gmoccapy to switch from high to low gear so you'll have to figure that out but this should show you how to do it.

 

File Attachment:

File Name: PM25MV_7i7...2-15.hal
File Size:20 KB
14 Dec 2023 21:12 - 14 Dec 2023 21:13
Replied by CNC_ANDI on topic Machine stop working

Machine stop working

Category: QtPyVCP

^^ yes i do that for sure

you can see it here:

got this message

cnc@debian:~/linuxcnc/configs/cnc_andi$ linuxcnc CNC-ANDI.ini
LINUXCNC - 2.9.0~pre1+git20230208.f1270d6ed7
Machine configuration directory is '/home/cnc/linuxcnc/configs/cnc_andi'
Machine configuration file is 'CNC-ANDI.ini'
Starting LinuxCNC...
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Note: Using POSIX realtime
twopass:invoked with <> options
twopass:found ./CNC-ANDI.hal
twopass:found ./handrad.hal
twopass:found ./custom.hal
twopass:pass0: loadusr -W hal_manualtoolchange
twopass:pass0: loadusr -W xhc-whb04b-6 -HsfB
twopass:pass0: loadusr -W vfdmod fulingvfd.ini

identityKinematicsSetup: coordinates:XYYZBC
   Joint 0 ==> Axis X
   Joint 1 ==> Axis Y
   Joint 2 ==> Axis Y
   Joint 3 ==> Axis Z
   Joint 4 ==> Axis B
   Joint 5 ==> Axis C
identityKinematicsSetup: Recommend: kinstype=both

hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: 10.10.10.10: INFO: Hardware address (MAC): 00:60:1b:10:43:6d
hm2_eth: discovered 7I76E-16
hm2/hm2_7i76e.0: Low Level init 0.15
hm2/hm2_7i76e.0: Smart Serial Firmware Version 43
Board hm2_7i76e.0.7i76.0.0 Hardware Mode 0 = standard
Board hm2_7i76e.0.7i76.0.0 Software Mode 0 = io_spin
Board hm2_7i76e.0.7i76.0.0 Software Mode 1 = io_ana_spin
Board hm2_7i76e.0.7i76.0.0 Software Mode 2 = io_enc_ana_spin_fv
hm2/hm2_7i76e.0: 51 I/O Pins used:
hm2/hm2_7i76e.0:     IO Pin 000 (P1-01): StepGen #0, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 001 (P1-14): StepGen #0, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 002 (P1-02): StepGen #1, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 003 (P1-15): StepGen #1, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 004 (P1-03): StepGen #2, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 005 (P1-16): StepGen #2, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 006 (P1-04): StepGen #3, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 007 (P1-17): StepGen #3, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 008 (P1-05): StepGen #4, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 009 (P1-06): StepGen #4, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 010 (P1-07): Smart Serial Interface #0, pin tx0 (Output)
hm2/hm2_7i76e.0:     IO Pin 011 (P1-08): Smart Serial Interface #0, pin rx0 (Input)
hm2/hm2_7i76e.0:     IO Pin 012 (P1-09): IOPort
hm2/hm2_7i76e.0:     IO Pin 013 (P1-10): IOPort
hm2/hm2_7i76e.0:     IO Pin 014 (P1-11): Encoder #0, pin Index (Input)
hm2/hm2_7i76e.0:     IO Pin 015 (P1-12): Encoder #0, pin B (Input)
hm2/hm2_7i76e.0:     IO Pin 016 (P1-13): Encoder #0, pin A (Input)
hm2/hm2_7i76e.0:     IO Pin 017 (P2-01): StepGen #5, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 018 (P2-14): StepGen #5, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 019 (P2-02): StepGen #6, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 020 (P2-15): StepGen #6, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 021 (P2-03): StepGen #7, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 022 (P2-16): StepGen #7, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 023 (P2-04): StepGen #8, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 024 (P2-17): StepGen #8, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 025 (P2-05): IOPort
hm2/hm2_7i76e.0:     IO Pin 026 (P2-06): IOPort
hm2/hm2_7i76e.0:     IO Pin 027 (P2-07): IOPort
hm2/hm2_7i76e.0:     IO Pin 028 (P2-08): IOPort
hm2/hm2_7i76e.0:     IO Pin 029 (P2-09): IOPort
hm2/hm2_7i76e.0:     IO Pin 030 (P2-10): IOPort
hm2/hm2_7i76e.0:     IO Pin 031 (P2-11): IOPort
hm2/hm2_7i76e.0:     IO Pin 032 (P2-12): IOPort
hm2/hm2_7i76e.0:     IO Pin 033 (P2-13): IOPort
hm2/hm2_7i76e.0:     IO Pin 034 (P3-01): IOPort
hm2/hm2_7i76e.0:     IO Pin 035 (P3-14): IOPort
hm2/hm2_7i76e.0:     IO Pin 036 (P3-02): IOPort
hm2/hm2_7i76e.0:     IO Pin 037 (P3-15): IOPort
hm2/hm2_7i76e.0:     IO Pin 038 (P3-03): IOPort
hm2/hm2_7i76e.0:     IO Pin 039 (P3-16): IOPort
hm2/hm2_7i76e.0:     IO Pin 040 (P3-04): IOPort
hm2/hm2_7i76e.0:     IO Pin 041 (P3-17): IOPort
hm2/hm2_7i76e.0:     IO Pin 042 (P3-05): IOPort
hm2/hm2_7i76e.0:     IO Pin 043 (P3-06): IOPort
hm2/hm2_7i76e.0:     IO Pin 044 (P3-07): IOPort
hm2/hm2_7i76e.0:     IO Pin 045 (P3-08): IOPort
hm2/hm2_7i76e.0:     IO Pin 046 (P3-09): IOPort
hm2/hm2_7i76e.0:     IO Pin 047 (P3-10): IOPort
hm2/hm2_7i76e.0:     IO Pin 048 (P3-11): IOPort
hm2/hm2_7i76e.0:     IO Pin 049 (P3-12): IOPort
hm2/hm2_7i76e.0:     IO Pin 050 (P3-13): IOPort
hm2/hm2_7i76e.0: registered
error deleting "/tmp/tmp_CNC-ANDI.hal": not owner
    while executing
"file delete $::TP($name)"
    invoked from within
"if $::tp::nodelete {
      verbose "nodelete: $::TP($name)"
    } else {
      verbose "deleting: $::TP($name)"
      file delete $::TP($name)
    }"
    (procedure "::tp::pass1" line 13)
    invoked from within
"::tp::pass1"
    (file "/usr/lib/tcltk/linuxcnc/twopass.tcl" line 768)
    invoked from within
"source $filename"
    invoked from within
"set result [source $filename]"
    (file "/usr/bin/haltcl" line 42)
Shutting down and cleaning up LinuxCNC...
vfdmod: close request received.
hm2_eth: in hm2_eth_reset
hm2_eth: HostMot2 ethernet driver unloaded
hm2: unloading
vfdmod: application closed.
Note: Using POSIX realtime
LinuxCNC terminated with an error.  You can find more information in the log:
    /home/cnc/linuxcnc_debug.txt
and
    /home/cnc/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal

14 Dec 2023 13:24
Replied by CNC_ANDI on topic Machine stop working

Machine stop working

Category: QtPyVCP

got this message

cnc@debian:~/linuxcnc/configs/cnc_andi$ linuxcnc CNC-ANDI.ini
LINUXCNC - 2.9.0~pre1+git20230208.f1270d6ed7
Machine configuration directory is '/home/cnc/linuxcnc/configs/cnc_andi'
Machine configuration file is 'CNC-ANDI.ini'
Starting LinuxCNC...
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Note: Using POSIX realtime
twopass:invoked with <> options
twopass:found ./CNC-ANDI.hal
twopass:found ./handrad.hal
twopass:found ./custom.hal
twopass:pass0: loadusr -W hal_manualtoolchange
twopass:pass0: loadusr -W xhc-whb04b-6 -HsfB
twopass:pass0: loadusr -W vfdmod fulingvfd.ini

identityKinematicsSetup: coordinates:XYYZBC
   Joint 0 ==> Axis X
   Joint 1 ==> Axis Y
   Joint 2 ==> Axis Y
   Joint 3 ==> Axis Z
   Joint 4 ==> Axis B
   Joint 5 ==> Axis C
identityKinematicsSetup: Recommend: kinstype=both

hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: 10.10.10.10: INFO: Hardware address (MAC): 00:60:1b:10:43:6d
hm2_eth: discovered 7I76E-16
hm2/hm2_7i76e.0: Low Level init 0.15
hm2/hm2_7i76e.0: Smart Serial Firmware Version 43
Board hm2_7i76e.0.7i76.0.0 Hardware Mode 0 = standard
Board hm2_7i76e.0.7i76.0.0 Software Mode 0 = io_spin
Board hm2_7i76e.0.7i76.0.0 Software Mode 1 = io_ana_spin
Board hm2_7i76e.0.7i76.0.0 Software Mode 2 = io_enc_ana_spin_fv
hm2/hm2_7i76e.0: 51 I/O Pins used:
hm2/hm2_7i76e.0:     IO Pin 000 (P1-01): StepGen #0, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 001 (P1-14): StepGen #0, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 002 (P1-02): StepGen #1, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 003 (P1-15): StepGen #1, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 004 (P1-03): StepGen #2, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 005 (P1-16): StepGen #2, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 006 (P1-04): StepGen #3, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 007 (P1-17): StepGen #3, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 008 (P1-05): StepGen #4, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 009 (P1-06): StepGen #4, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 010 (P1-07): Smart Serial Interface #0, pin tx0 (Output)
hm2/hm2_7i76e.0:     IO Pin 011 (P1-08): Smart Serial Interface #0, pin rx0 (Input)
hm2/hm2_7i76e.0:     IO Pin 012 (P1-09): IOPort
hm2/hm2_7i76e.0:     IO Pin 013 (P1-10): IOPort
hm2/hm2_7i76e.0:     IO Pin 014 (P1-11): Encoder #0, pin Index (Input)
hm2/hm2_7i76e.0:     IO Pin 015 (P1-12): Encoder #0, pin B (Input)
hm2/hm2_7i76e.0:     IO Pin 016 (P1-13): Encoder #0, pin A (Input)
hm2/hm2_7i76e.0:     IO Pin 017 (P2-01): StepGen #5, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 018 (P2-14): StepGen #5, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 019 (P2-02): StepGen #6, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 020 (P2-15): StepGen #6, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 021 (P2-03): StepGen #7, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 022 (P2-16): StepGen #7, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 023 (P2-04): StepGen #8, pin Direction (Output)
hm2/hm2_7i76e.0:     IO Pin 024 (P2-17): StepGen #8, pin Step (Output)
hm2/hm2_7i76e.0:     IO Pin 025 (P2-05): IOPort
hm2/hm2_7i76e.0:     IO Pin 026 (P2-06): IOPort
hm2/hm2_7i76e.0:     IO Pin 027 (P2-07): IOPort
hm2/hm2_7i76e.0:     IO Pin 028 (P2-08): IOPort
hm2/hm2_7i76e.0:     IO Pin 029 (P2-09): IOPort
hm2/hm2_7i76e.0:     IO Pin 030 (P2-10): IOPort
hm2/hm2_7i76e.0:     IO Pin 031 (P2-11): IOPort
hm2/hm2_7i76e.0:     IO Pin 032 (P2-12): IOPort
hm2/hm2_7i76e.0:     IO Pin 033 (P2-13): IOPort
hm2/hm2_7i76e.0:     IO Pin 034 (P3-01): IOPort
hm2/hm2_7i76e.0:     IO Pin 035 (P3-14): IOPort
hm2/hm2_7i76e.0:     IO Pin 036 (P3-02): IOPort
hm2/hm2_7i76e.0:     IO Pin 037 (P3-15): IOPort
hm2/hm2_7i76e.0:     IO Pin 038 (P3-03): IOPort
hm2/hm2_7i76e.0:     IO Pin 039 (P3-16): IOPort
hm2/hm2_7i76e.0:     IO Pin 040 (P3-04): IOPort
hm2/hm2_7i76e.0:     IO Pin 041 (P3-17): IOPort
hm2/hm2_7i76e.0:     IO Pin 042 (P3-05): IOPort
hm2/hm2_7i76e.0:     IO Pin 043 (P3-06): IOPort
hm2/hm2_7i76e.0:     IO Pin 044 (P3-07): IOPort
hm2/hm2_7i76e.0:     IO Pin 045 (P3-08): IOPort
hm2/hm2_7i76e.0:     IO Pin 046 (P3-09): IOPort
hm2/hm2_7i76e.0:     IO Pin 047 (P3-10): IOPort
hm2/hm2_7i76e.0:     IO Pin 048 (P3-11): IOPort
hm2/hm2_7i76e.0:     IO Pin 049 (P3-12): IOPort
hm2/hm2_7i76e.0:     IO Pin 050 (P3-13): IOPort
hm2/hm2_7i76e.0: registered
error deleting "/tmp/tmp_CNC-ANDI.hal": not owner
    while executing
"file delete $::TP($name)"
    invoked from within
"if $::tp::nodelete {
      verbose "nodelete: $::TP($name)"
    } else {
      verbose "deleting: $::TP($name)"
      file delete $::TP($name)
    }"
    (procedure "::tp::pass1" line 13)
    invoked from within
"::tp::pass1"
    (file "/usr/lib/tcltk/linuxcnc/twopass.tcl" line 768)
    invoked from within
"source $filename"
    invoked from within
"set result [source $filename]"
    (file "/usr/bin/haltcl" line 42)
Shutting down and cleaning up LinuxCNC...
vfdmod: close request received.
hm2_eth: in hm2_eth_reset
hm2_eth: HostMot2 ethernet driver unloaded
hm2: unloading
vfdmod: application closed.
Note: Using POSIX realtime
LinuxCNC terminated with an error.  You can find more information in the log:
    /home/cnc/linuxcnc_debug.txt
and
    /home/cnc/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal
 
12 Dec 2023 15:36
Replied by Aciera on topic Maschinen an/aus auf Externe Taste legen

Maschinen an/aus auf Externe Taste legen

Category: Deutsch

Beispiel, hier für Kühlung (hm2_7i76e.0.7i73.0.1.input-03-not  ist das Signal vom Taster):
#  --- Toggle M8 on/off ---
net machine-is-on     => paneltoggle.m8.enable
net m8-panel            <= hm2_7i76e.0.7i73.0.1.input-03-not     => paneltoggle.m8.input
net m8-is-on             <= halui.flood.is-on  => paneltoggle.m8.status
net m8-set                <= paneltoggle.m8.set           => halui.flood.on
net m8-reset             <= paneltoggle.m8.reset        => halui.flood.off
08 Dec 2023 23:30
Replied by tommylight on topic linuxcnc terminated with an error

linuxcnc terminated with an error

Category: General LinuxCNC Questions

What type of mesa boards do you use or have you used?

5i25, 6i25, 7i92, 7i96, 7i95, 7i77, 7i76, 7i76E, 7i74, 7i73, 7i70, 7i71, 7i72, THCAD, ...
Probably forgot some.

if they are the type with serial communication (ethernet type for example) can you insert the firmware that is convenient for your machine into the internal eeprom???

I would not call Ethernet "serial", there are some differences there, but yes, some are Ethernet boards and no you can not "load" firmware, all of these require flashing the firmware once and do not need to load the firmware from the PC as it is located in their own internal memory.
And yes, anytime i needed some strange firmware that did not exist, it was generously provided by PCW (he is the owner of Mesa).
Now, this begs the question, what are you changing that often that you need to load different firmware?
I needed once, only once on a very big machine, firmware that was not standard, and once or twice for testing some strange contraptions i made, otherwise there is no need to change firmware most of the time.
Displaying 451 - 465 out of 630 results.
  1. Forum
  3. Search
Time to create page: 1.047 seconds
Powered by Kunena Forum