In trouble after update
- Mike_Eitel
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 1150
- Thank you received: 184
25 Dec 2018 15:19 #122870
by Mike_Eitel
In trouble after update was created by Mike_Eitel
Hi
I did an update yesterday and now I have no glue how to get my system running again.
It was running perfect before.
Such kind of errors I saw never.
4 axes stepper with Master / 7i76e / Gmoccapy / ncam
Any idea where to start ?
THX in advance
Mike
P.S.
Will try to send config, having trouble with file size....
I did an update yesterday and now I have no glue how to get my system running again.
It was running perfect before.
Such kind of errors I saw never.
4 axes stepper with Master / 7i76e / Gmoccapy / ncam
Any idea where to start ?
THX in advance
Mike
P.S.
Will try to send config, having trouble with file size....
Please Log in or Create an account to join the conversation.
- Mike_Eitel
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 1150
- Thank you received: 184
25 Dec 2018 15:25 #122871
by Mike_Eitel
Replied by Mike_Eitel on topic In trouble after update
And here my config.
I deleted everything inside ncam otherwise it was over 4MB.
Mike
I deleted everything inside ncam otherwise it was over 4MB.
Mike
Please Log in or Create an account to join the conversation.
25 Dec 2018 16:27 - 25 Dec 2018 16:32 #122873
by dgarrett
Recent commits to master branch add multispindle
capability and name changes for spindle hal pins.
The update_ini script fixes most name-change
occurrences and updates [EMC]VERSION to 1.1.
However, your display.hal file is probably not detected
since it is sourced within the postgui_call_list.hal
and not handled by the update_ini script:
LinuxCNC stopped on first error (display.hal) but you
have additional name change errors in spindle_vfd.hal.
You will need to update all hal pin names normally
fixed by update ini as illustrated by:
See also: man pages for halui,motion:
linuxcnc.org/docs/master/html/man/man9/motion.9.html
linuxcnc.org/docs/master/html/man/man1/halui.1.html
Candidates in your hal files:
Replied by dgarrett on topic In trouble after update
display.hal:78: Pin 'motion.spindle-speed-out-rps-abs' does not exist
...
LINUXCNCVERSION: 2.8.0-pre1-4081-g48726d6ea
Recent commits to master branch add multispindle
capability and name changes for spindle hal pins.
The update_ini script fixes most name-change
occurrences and updates [EMC]VERSION to 1.1.
However, your display.hal file is probably not detected
since it is sourced within the postgui_call_list.hal
and not handled by the update_ini script:
$ grep source *.hal
postgui_call_list.hal:source analog_in.hal
postgui_call_list.hal:source estop_and_enable.hal
postgui_call_list.hal:#source home_limit.hal
postgui_call_list.hal:source display.hal
postgui_call_list.hal:source mpg.hal
postgui_call_list.hal:source tool.hal
postgui_call_list.hal:source spindle_vfd.hal
LinuxCNC stopped on first error (display.hal) but you
have additional name change errors in spindle_vfd.hal.
You will need to update all hal pin names normally
fixed by update ini as illustrated by:
$ grep spindle `which update_ini`
'motion.spindle-brake' : 'spindle.0.brake',
'motion.spindle-forward' : 'spindle.0.forward',
'motion.spindle-index-enable' : 'spindle.0.index-enable',
'motion.spindle-inhibit' : 'spindle.0.inhibit',
'motion.spindle-on' : 'spindle.0.on',
'motion.spindle-reverse' : 'spindle.0.reverse',
'motion.spindle-revs' : 'spindle.0.revs',
'motion.spindle-speed-in' : 'spindle.0.speed-in',
'motion.spindle-speed-out' : 'spindle.0.speed-out',
'motion.spindle-speed-out-abs' : 'spindle.0.speed-out-abs',
'motion.spindle-speed-out-rps' : 'spindle.0.speed-out-rps',
'motion.spindle-speed-out-rps-abs' : 'spindle.0.speed-out-rps-abs',
'motion.spindle-orient-angle' : 'spindle.0.orient-angle',
'motion.spindle-orient-mode' : 'spindle.0.orient-mode',
'motion.spindle-orient' : 'spindle.0.orient',
'motion.spindle-is-oriented' : 'spindle.0.is-oriented',
'motion.spindle-orient-fault' : 'spindle.0.orient-fault',
'motion.spindle-locked' : 'spindle.0.locked',
'motion.spindle-at-speed' : 'spindle.0.at-speed',
'halui.spindle.brake-is-on' : 'halui.spindle.0.brake-is-on',
'halui.spindle.brake-off' : 'halui.spindle.0.brake-off',
'halui.spindle.brake-on' : 'halui.spindle.0.brake-on',
'halui.spindle.decrease' : 'halui.spindle.0.decrease',
'halui.spindle.forward' : 'halui.spindle.0.forward',
'halui.spindle.increase' : 'halui.spindle.0.increase',
'halui.spindle.is-on' : 'halui.spindle.0.is-on',
'halui.spindle.reverse' : 'halui.spindle.0.reverse',
'halui.spindle.runs-backward' : 'halui.spindle.0.runs-backward',
'halui.spindle.runs-forward' : 'halui.spindle.0.runs-forward',
'halui.spindle.start' : 'halui.spindle.0.start',
'halui.spindle.stop' : 'halui.spindle.0.stop',
'halui.spindle.override.count-enable' : 'halui.spindle.0.override.count-enable',
'halui.spindle.override.counts' : 'halui.spindle.0.override.counts',
'halui.spindle.override.decrease' : 'halui.spindle.0.override.decrease',
'halui.spindle.override.direct-value' : 'halui.spindle.0.override.direct-value',
'halui.spindle.override.increase' : 'halui.spindle.0.override.increase',
'halui.spindle.override.scale' : 'halui.spindle.0.override.scale',
'halui.spindle.override.value' : 'halui.spindle.0.override.value'
See also: man pages for halui,motion:
linuxcnc.org/docs/master/html/man/man9/motion.9.html
linuxcnc.org/docs/master/html/man/man1/halui.1.html
Candidates in your hal files:
MeBigCNC3 $ grep -E motion\.spindle\|halui\.spindle *hal
display.hal:net t4 motion.spindle-speed-out-rps-abs => toolpara.in-spin-rps
spindle_vfd.hal:net auto_spindle_enable <= motion.spindle-on
spindle_vfd.hal:net auto_spindle_dir <= motion.spindle-reverse
spindle_vfd.hal:net spindle_auto-ra spind-scaler.in1 <= motion.spindle-speed-out-abs
spindle_vfd.hal:net spindle-rps => motion.spindle-speed-in
spindle_vfd.hal:net spindle-revs motion.spindle-revs <= hm2_7i76e.0.encoder.00.position
spindle_vfd.hal:net spindle-ind-ena motion.spindle-index-enable <=> hm2_7i76e.0.encoder.00.index-enable
spindle_vfd.hal:#net spindle-at-speed => motion.spindle-at-speed
Last edit: 25 Dec 2018 16:32 by dgarrett. Reason: show candidates
Please Log in or Create an account to join the conversation.
- Mike_Eitel
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 1150
- Thank you received: 184
25 Dec 2018 16:54 #122879
by Mike_Eitel
Replied by Mike_Eitel on topic In trouble after update
Big THX
That makes sense to me.
I remember now having read about spindle instantiateing.
Hope this is nit also in gmoccapy and ncam..
Will give it a test, as soon my govern allows it
Happy Christmas
Mike
That makes sense to me.
I remember now having read about spindle instantiateing.
Hope this is nit also in gmoccapy and ncam..
Will give it a test, as soon my govern allows it
Happy Christmas
Mike
Please Log in or Create an account to join the conversation.
- Mike_Eitel
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 1150
- Thank you received: 184
25 Dec 2018 18:32 #122884
by Mike_Eitel
Replied by Mike_Eitel on topic In trouble after update
Hi dgarrett
I had half an hour an now my machine is up again!
SUPER
Mike
P. S. Debugging became very easy and fast since I installed on ssd.
One try and error cycle is far below one minute since.
I had half an hour an now my machine is up again!
SUPER
Mike
P. S. Debugging became very easy and fast since I installed on ssd.
One try and error cycle is far below one minute since.
Please Log in or Create an account to join the conversation.
29 Dec 2018 14:37 #123076
by andypugh
I should fix that.
Replied by andypugh on topic In trouble after update
However, your display.hal file is probably not detected
since it is sourced within the postgui_call_list.hal
and not handled by the update_ini script:
I should fix that.
The following user(s) said Thank You: Mike_Eitel
Please Log in or Create an account to join the conversation.
- Mike_Eitel
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 1150
- Thank you received: 184
29 Dec 2018 16:02 #123098
by Mike_Eitel
Replied by Mike_Eitel on topic In trouble after update
I'm aware that I use a bit complicated way to structure my hal files.
Two pass was not working as I expected so I use this form.
I would like the idea two have:
All hw dependent i/o definitions in one hal file
(Inputs are OK, but I was not able to have that with outputs too)
All according loadrt and addf on top of each according hal, but that did not work.
(That's why I stuffed them all in one file)
P. S.
I know that I'm a bit old fashioned as I like clear declaration on one place and also program parts structured to functionalities.
Mike
Two pass was not working as I expected so I use this form.
I would like the idea two have:
All hw dependent i/o definitions in one hal file
(Inputs are OK, but I was not able to have that with outputs too)
All according loadrt and addf on top of each according hal, but that did not work.
(That's why I stuffed them all in one file)
P. S.
I know that I'm a bit old fashioned as I like clear declaration on one place and also program parts structured to functionalities.
Mike
Please Log in or Create an account to join the conversation.
29 Dec 2018 16:20 #123100
by pl7i92
Replied by pl7i92 on topic In trouble after update
hi i did found me in the same position on updating systems to debian9 and 2.7.14
CAN Someone Please EDIT the Main linuxcnc.org PAGE to tell this and the Download Pages of the NEW OS
that woudt help in first hand
What to expect
CAN Someone Please EDIT the Main linuxcnc.org PAGE to tell this and the Download Pages of the NEW OS
that woudt help in first hand
What to expect
Please Log in or Create an account to join the conversation.
29 Dec 2018 17:37 #123105
by PCW
I think its a really good idea to keep hardware specific parts (pins and parameters)
of the hal file located in one hardware specific file, (that links to signals with standard names)
so the basic structural parts of the hal file are hardware independent.
What was the issue with outputs?
Replied by PCW on topic In trouble after update
I'm aware that I use a bit complicated way to structure my hal files.
Two pass was not working as I expected so I use this form.
I would like the idea two have:
All hw dependent i/o definitions in one hal file
(Inputs are OK, but I was not able to have that with outputs too)
All according loadrt and addf on top of each according hal, but that did not work.
(That's why I stuffed them all in one file)
P. S.
I know that I'm a bit old fashioned as I like clear declaration on one place and also program parts structured to functionalities.
Mike
I think its a really good idea to keep hardware specific parts (pins and parameters)
of the hal file located in one hardware specific file, (that links to signals with standard names)
so the basic structural parts of the hal file are hardware independent.
What was the issue with outputs?
Please Log in or Create an account to join the conversation.
- Mike_Eitel
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 1150
- Thank you received: 184
29 Dec 2018 18:02 #123106
by Mike_Eitel
Replied by Mike_Eitel on topic In trouble after update
Hi Peter
If you look in my config (included here earlier) you can find that in 7i76e.hal I commented out the output declarations. And have them in the according hal uncommented.
I'm not sure anymore, either it simply did not work, or stopped with error on startup. I had both variants in the process of finding my way of writing hal.
You can easy test the output part by using my directory (yes you have to correct 4 or 5 spindle.0. replacements in that version) MeBigCNC3. Ini
Mike
If you look in my config (included here earlier) you can find that in 7i76e.hal I commented out the output declarations. And have them in the according hal uncommented.
I'm not sure anymore, either it simply did not work, or stopped with error on startup. I had both variants in the process of finding my way of writing hal.
You can easy test the output part by using my directory (yes you have to correct 4 or 5 spindle.0. replacements in that version) MeBigCNC3. Ini
Mike
Please Log in or Create an account to join the conversation.
Time to create page: 0.126 seconds