Differents PID´s for differents velocities
09 Sep 2013 19:25 #38561
by andypugh
Replied by andypugh on topic Differents PID´s for differents velocities
Can you have a look at the referenced file (/usr/bin/comp ) and see if it looks like this file
git.linuxcnc.org/gitweb?p=linuxcnc.git;a...c2b063426667fac573dd
Because the LinuxCNC "comp" script doesn't actually _have_ a line 1178....
git.linuxcnc.org/gitweb?p=linuxcnc.git;a...c2b063426667fac573dd
Because the LinuxCNC "comp" script doesn't actually _have_ a line 1178....
Please Log in or Create an account to join the conversation.
09 Sep 2013 19:47 - 09 Sep 2013 23:12 #38562
by casetero
Replied by casetero on topic Differents PID´s for differents velocities
In fact, is not the same file.
How is this possible??
Thank you.
How is this possible??
Thank you.
Last edit: 09 Sep 2013 23:12 by BigJohnT. Reason: delete long post with no code tags
Please Log in or Create an account to join the conversation.
09 Sep 2013 19:49 #38563
by casetero
Replied by casetero on topic Differents PID´s for differents velocities
At the end worpad has forgotten spaces, but i think the file is different.
Do you know what can be the problem??
Thank you.
Do you know what can be the problem??
Thank you.
Please Log in or Create an account to join the conversation.
09 Sep 2013 19:55 #38564
by andypugh
Replied by andypugh on topic Differents PID´s for differents velocities
It is at least the LinuxCNC "comp" and not a completely different package, which is what I was wondering.
I suspect that the comp.g file from the source code is expanded into the /usr/bin/comp file, and that explains the different line count.
I don't have a LinuxCNC machine here at work, so I can't explore what might be going wrong around line 1175 (and I don't really understand Python either)
I suspect that the comp.g file from the source code is expanded into the /usr/bin/comp file, and that explains the different line count.
I don't have a LinuxCNC machine here at work, so I can't explore what might be going wrong around line 1175 (and I don't really understand Python either)
Please Log in or Create an account to join the conversation.
09 Sep 2013 20:01 #38566
by casetero
Replied by casetero on topic Differents PID´s for differents velocities
Ok, i think the better solution maybe reinstall the linuxcnc package and dev-package to the last version.
Because this component i think it will be very usefull for me.
Thank you Andy.
Because this component i think it will be very usefull for me.
Thank you Andy.
Please Log in or Create an account to join the conversation.
10 Sep 2013 17:17 #38599
by casetero
Replied by casetero on topic Differents PID´s for differents velocities
Andy,
Have you seen something strange?
Do u think updating to the last version i will fix the problem?
If i update, will i loose my actual configurations??
I have installed the 2.5.0 version.
Thank you.
Have you seen something strange?
Do u think updating to the last version i will fix the problem?
If i update, will i loose my actual configurations??
I have installed the 2.5.0 version.
Thank you.
Please Log in or Create an account to join the conversation.
10 Sep 2013 17:25 #38600
by andypugh
Replied by andypugh on topic Differents PID´s for differents velocities
[quote="casetero" post=38599If i update, will i loose my actual configurations??
I have installed the 2.5.0 version..[/quote]
Your configs will be safe if you upgrade LinuCNC.
2.5.0 is far from the most recent. The most recent _released_ version is 2.5.3 which should be an automatic update from 2.5.0.
However, "lincurve" is not in 2.5.3 either, it is only in the development (unreleased) version. You can only get that by following the instructions at htp://buildbot.linuxcnc.org (to install pre-built packages) or by compiling and installing it yourself.
I have installed the 2.5.0 version..[/quote]
Your configs will be safe if you upgrade LinuCNC.
2.5.0 is far from the most recent. The most recent _released_ version is 2.5.3 which should be an automatic update from 2.5.0.
However, "lincurve" is not in 2.5.3 either, it is only in the development (unreleased) version. You can only get that by following the instructions at htp://buildbot.linuxcnc.org (to install pre-built packages) or by compiling and installing it yourself.
Please Log in or Create an account to join the conversation.
10 Sep 2013 18:46 #38605
by casetero
Replied by casetero on topic Differents PID´s for differents velocities
Hi,
I have updated it to version 2.5.3 whit dev version 2.5.3 too and continues giving me same error when making comp --instal lincurve.comp
Dont know what i am doing wrong.
Thank you.
I have updated it to version 2.5.3 whit dev version 2.5.3 too and continues giving me same error when making comp --instal lincurve.comp
Dont know what i am doing wrong.
Thank you.
Please Log in or Create an account to join the conversation.
10 Sep 2013 18:56 #38607
by andypugh
What happens with just
I am hoping that somebody who understands a bit of Python can chip in with a suggestion.
Replied by andypugh on topic Differents PID´s for differents velocities
I assume you mean "--install" ?I have updated it to version 2.5.3 whit dev version 2.5.3 too and continues giving me same error when making comp --instal lincurve.comp
What happens with just
comp lincurve.comp
I don't think _you_ are doing anything wrong.Dont know what i am doing wrong..
I am hoping that somebody who understands a bit of Python can chip in with a suggestion.
Please Log in or Create an account to join the conversation.
10 Sep 2013 19:09 #38608
by casetero
Replied by casetero on topic Differents PID´s for differents velocities
Hi,
Maybe this help you:
pablo@Pablo-cnc:~/Escritorio/MESA/componentes$ comp lincurve.comp
Traceback (most recent call last):
File "/usr/bin/comp", line 1338, in <module>
main()
File "/usr/bin/comp", line 1307, in main
process(f, mode, outfile)
File "/usr/bin/comp", line 1178, in process
a, b = parse(filename)
File "/usr/bin/comp", line 411, in parse
a, b = f.split("\n;;\n", 1)
ValueError: need more than 1 value to unpack
pablo@Pablo-cnc:~/Escritorio/MESA/componentes$ comp lincurve3.comp
Traceback (most recent call last):
File "/usr/bin/comp", line 1338, in <module>
main()
File "/usr/bin/comp", line 1307, in main
process(f, mode, outfile)
File "/usr/bin/comp", line 1178, in process
a, b = parse(filename)
File "/usr/bin/comp", line 410, in parse
f = open(filename).read()
IOError: [Errno 2] No such file or directory: 'lincurve3.comp'
The first time i try to comp it, it shows ValueError: need more than 1 value to unpack
Here im trying to comp the real file.
The second time, it shows IOError: [Errno 2] No such file or directory: 'lincurve3.comp'
Here im trying to comp a non real file.
The first time it shows the same dialog of comp, but changes at the end
File "/usr/bin/comp", line 411, in parse
a, b = f.split("\n;;\n", 1)
This is the only line that changed refered to the trying comping with a non real file.
Maybe helps...
Thank you.
Maybe this help you:
pablo@Pablo-cnc:~/Escritorio/MESA/componentes$ comp lincurve.comp
Traceback (most recent call last):
File "/usr/bin/comp", line 1338, in <module>
main()
File "/usr/bin/comp", line 1307, in main
process(f, mode, outfile)
File "/usr/bin/comp", line 1178, in process
a, b = parse(filename)
File "/usr/bin/comp", line 411, in parse
a, b = f.split("\n;;\n", 1)
ValueError: need more than 1 value to unpack
pablo@Pablo-cnc:~/Escritorio/MESA/componentes$ comp lincurve3.comp
Traceback (most recent call last):
File "/usr/bin/comp", line 1338, in <module>
main()
File "/usr/bin/comp", line 1307, in main
process(f, mode, outfile)
File "/usr/bin/comp", line 1178, in process
a, b = parse(filename)
File "/usr/bin/comp", line 410, in parse
f = open(filename).read()
IOError: [Errno 2] No such file or directory: 'lincurve3.comp'
The first time i try to comp it, it shows ValueError: need more than 1 value to unpack
Here im trying to comp the real file.
The second time, it shows IOError: [Errno 2] No such file or directory: 'lincurve3.comp'
Here im trying to comp a non real file.
The first time it shows the same dialog of comp, but changes at the end
File "/usr/bin/comp", line 411, in parse
a, b = f.split("\n;;\n", 1)
This is the only line that changed refered to the trying comping with a non real file.
Maybe helps...
Thank you.
Please Log in or Create an account to join the conversation.
Time to create page: 0.283 seconds