Adding a status tab for MESA card
21 Jan 2018 21:47 #104819
by kor
Replied by kor on topic Adding a status tab for MESA card
when I start linuxcnc from the console I get a line telling me: module hitcounter skipped. import error no module named hitcounter
followed by: /usr/bin/gladevcp:212: runtime warning: missing handler 'on_LED_di05_hal_pin_changed'
and than it is waiting for gladevcp filling my console with points.
Oo
followed by: /usr/bin/gladevcp:212: runtime warning: missing handler 'on_LED_di05_hal_pin_changed'
and than it is waiting for gladevcp filling my console with points.
Oo
Please Log in or Create an account to join the conversation.
22 Jan 2018 08:36 #104835
by andypugh
Replied by andypugh on topic Adding a status tab for MESA card
Ah, yes, you have specified a handler file in the INI entry. (hitcounter.py)
I guess you followed an example file too carefully. The system is presumably silently failing because that file does not exist, and is then not getting to the point of loacding your postgui halfile.
Your simple GUI shouldn't need a handler file. Just remove thepart
See linuxcnc.org/docs/2.7/html/gui/gladevcp....command_line_options to see what the options do.
I guess you followed an example file too carefully. The system is presumably silently failing because that file does not exist, and is then not getting to the point of loacding your postgui halfile.
Your simple GUI shouldn't need a handler file. Just remove the
-u ./gladevcp/hitcounter.pySee linuxcnc.org/docs/2.7/html/gui/gladevcp....command_line_options to see what the options do.
Please Log in or Create an account to join the conversation.
22 Jan 2018 13:38 #104841
by kor
Replied by kor on topic Adding a status tab for MESA card
Now I don't have any error msgs an more. But My LEDs won't change their stus either.
The console is still telling me thati it is waiting for gladevcp:
The console is still telling me thati it is waiting for gladevcp:
Starting LinuxCNC...
Found file(REL): ./my_Lathe_7i76E.hal
Note: Using POSIX realtime
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: 192.168.1.121: Hardware address: 00:60:1b:10:41:52
hm2_eth: discovered 7I76E-16
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): IOPort
hm2/hm2_7i76e.0: IO Pin 005 (P1-16): IOPort
hm2/hm2_7i76e.0: IO Pin 006 (P1-04): IOPort
hm2/hm2_7i76e.0: IO Pin 007 (P1-17): IOPort
hm2/hm2_7i76e.0: IO Pin 008 (P1-05): IOPort
hm2/hm2_7i76e.0: IO Pin 009 (P1-06): IOPort
hm2/hm2_7i76e.0: IO Pin 010 (P1-07): Smart Serial Interface #0, pin TxData0 (Output)
hm2/hm2_7i76e.0: IO Pin 011 (P1-08): Smart Serial Interface #0, pin RxData0 (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): IOPort
hm2/hm2_7i76e.0: IO Pin 018 (P2-14): IOPort
hm2/hm2_7i76e.0: IO Pin 019 (P2-02): IOPort
hm2/hm2_7i76e.0: IO Pin 020 (P2-15): IOPort
hm2/hm2_7i76e.0: IO Pin 021 (P2-03): IOPort
hm2/hm2_7i76e.0: IO Pin 022 (P2-16): IOPort
hm2/hm2_7i76e.0: IO Pin 023 (P2-04): IOPort
hm2/hm2_7i76e.0: IO Pin 024 (P2-17): IOPort
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
Found file(REL): ./custom.hal
note: MAXV max: 25.000 units/sec 1500.000 units/min
note: LJOG max: 25.000 units/sec 1500.000 units/min
note: LJOG default: 6.000 units/sec 360.000 units/min
note: jog_order='ZX'
note: jog_invert=set(['X'])
Waiting for component 'gladevcp' to become ready.......................................................................................................................................................Please Log in or Create an account to join the conversation.
22 Jan 2018 14:07 #104842
by andypugh
Replied by andypugh on topic Adding a status tab for MESA card
That might be the -W command you gave it. Perhaps your GUI doesn't call itself "gladevcp".
-W defines a specific name to wait for and waits for that exact name to appear in the HAL.
-W defines a specific name to wait for and waits for that exact name to appear in the HAL.
The following user(s) said Thank You: kor
Please Log in or Create an account to join the conversation.
22 Jan 2018 14:42 #104845
by kor
Replied by kor on topic Adding a status tab for MESA card
Thanks Andy now one of the pins works because the other one is linked to home-z it crashed so I uncommented that one.
Is there a way to link the already connected signals to the LEDs? and still keep their function?
Is there a way to link the already connected signals to the LEDs? and still keep their function?
Please Log in or Create an account to join the conversation.
22 Jan 2018 15:20 #104849
by andypugh
Yes, just link the _signal_ to the gladevcp tab.
Anywhere that you haveYou can also have (anywhere in any HAL file)
Replied by andypugh on topic Adding a status tab for MESA card
Thanks Andy now one of the pins works because the other one is linked to home-z it crashed so I uncommented that one.
Is there a way to link the already connected signals to the LEDs? and still keep their function?
Yes, just link the _signal_ to the gladevcp tab.
Anywhere that you have
net a-specific-signal hm2_7i76E.0.input-00 => motion.something-elcenet a-specific-signal gladevcp.LED-something-or-other
The following user(s) said Thank You: kor
Please Log in or Create an account to join the conversation.
Time to create page: 0.127 seconds