c++ grab in position signal

More
24 Sep 2014 15:48 #51517 by bkt
Replied by bkt on topic c++ grab in position signal
@AndyPugh ... I'm not sure but I think I already ran into this issue .... infinite loop and M66 are not much agree . In fact, # 5399 is stored in xxx.var , read only once at the start of Gcode ..... or I said a big bullshit ? .... I have the bad habit of reading with little conviction manuals..... I open a new thread in Gcode session for #<_hal[e.pin]> not working

Please Log in or Create an account to join the conversation.

More
24 Sep 2014 15:58 - 24 Sep 2014 15:58 #51518 by bkt
Replied by bkt on topic c++ grab in position signal
@AndyPugh ... I'm not sure but I think I already ran into this issue .... infinite loop and M66 are not much agree ...... I open a new thread in Gcode session for #<_hal[e.pin]> not working
Last edit: 24 Sep 2014 15:58 by bkt.

Please Log in or Create an account to join the conversation.

More
24 Sep 2014 16:06 - 24 Sep 2014 16:09 #51519 by ArcEye
Replied by ArcEye on topic c++ grab in position signal

I open a new thread in Gcode session for #<_hal[e.pin]> not working


It works fine

Instructions are here
www.linuxcnc.org/docs/devel/html/remap/s...d_sub_ini_features_a

Add to the [RS274NGC] section of the ini file

FEATURES = 8

Below the result




regards
Attachments:
Last edit: 24 Sep 2014 16:09 by ArcEye.
The following user(s) said Thank You: bkt

Please Log in or Create an account to join the conversation.

More
24 Sep 2014 17:04 #51524 by bkt
Replied by bkt on topic c++ grab in position signal
I try with your same pin.....





I try with my custom pin .....




[EMC]
MACHINE = my-mill
DEBUG = 0

[DISPLAY]
DISPLAY = axis
EDITOR = gedit
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
MAX_FEED_OVERRIDE = 1.2
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 5
PROGRAM_PREFIX =  /home/k1/linuxcnc/open
INCREMENTS = 5mm 1mm .5mm .1mm .05mm .01mm .005mm
PYVCP=panel.xml

[FILTER]
PROGRAM_EXTENSION = .png,.gif,.jpg Greyscale Depth Image
PROGRAM_EXTENSION = .py Python Script
png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python

[TASK]
TASK = milltask
CYCLE_TIME = 0.010

[RS274NGC]
FEATURES = 8
PARAMETER_FILE = linuxcnc1.var



[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
COMM_WAIT = 0.010
BASE_PERIOD = 78125
SERVO_PERIOD = 1000000
#loadrt trivkins
loadrt deltakins_A_catch_GFX
loadusr -W ethloop
#loadrt tripodkins
while [#<_hal[ethloop.fstop] EQ 1]
...
....>
:blink:
Attachments:

Please Log in or Create an account to join the conversation.

More
24 Sep 2014 17:15 #51526 by andypugh

(debug,#<_hal[e.fstop]>
... I get ######
(debug,#<_x>
... I get ###### with FEATURES=12 and 28 too


Which version of LinuxCNC are you using? G-code access to HAL only appeared in 2.6.
The predefined, named parameters ought to work in 2.6: www.linuxcnc.org/docs/html/gcode/overview.html#sec:parameters
But those were not there in 2.5: www.linuxcnc.org/docs/2.5/html/gcode/ove....html#sec:parameters
So perhaps you are running a 2.5 version?

Incidentally, you might want to look at the Machinekit project, that is completely re-working the internal communications of LinuxCNC which might make what you are trying to do a lot easier.
The following user(s) said Thank You: bkt

Please Log in or Create an account to join the conversation.

More
24 Sep 2014 17:22 - 24 Sep 2014 17:26 #51527 by bkt
Replied by bkt on topic c++ grab in position signal
2.5.4 ..... ubu10.04 .......................so I have to install the 2.6 ?? the upgrade can cause particular problems ?
Last edit: 24 Sep 2014 17:26 by bkt.

Please Log in or Create an account to join the conversation.

More
24 Sep 2014 17:39 - 24 Sep 2014 17:40 #51528 by ArcEye
Replied by ArcEye on topic c++ grab in position signal
No quite straight forward

wiki.linuxcnc.org/cgi-bin/wiki.pl?UpdatingTo2.6

It never occurred to me that you were using 2.5, because you have been amending the sources for Linuxcnc, so assumed you got them from the git repo and were running a RIP

regards
Last edit: 24 Sep 2014 17:40 by ArcEye.
The following user(s) said Thank You: bkt

Please Log in or Create an account to join the conversation.

More
24 Sep 2014 19:18 #51529 by bkt
Replied by bkt on topic c++ grab in position signal
do not worry .... I hope that by installing the version 2.6 to solve this thing ..... unfortunately are accustomed to using at least 2 versions of ubuntu back .... I did the same with LinuxCNC .... I have not even thought about it .... I assumed it was something about hal ini file or similar to..... more late updates.

Please Log in or Create an account to join the conversation.

More
24 Sep 2014 21:37 #51530 by bkt
Replied by bkt on topic c++ grab in position signal
ok it works!

... new linuxcnc-dev compiler have found an error on one my comp .... nothing of special ... an unused variable :huh:

now with in ini file
[RS274NGC]
FEATURES = 28  ##or 8 or 12 it is the same for my result, this is try.
PARAMETER_FILE = linuxcnc1.var



one comment about infinite loop in gcode: Now I try it directly, but the same problem I had seen in the past. Linuxcnc trajectory planner (I don't now how it work....) but must have some sort of buffer. In fact, if I run an infinite loop with the variable X#<_hal[e.fpxdue]> that is updated with a command M160 UP and later a M170 DOWN command, must insert an M66 that says when the variable X#<_hal[e.fpxdue]> is updated. Otherwise the gcoge runs n times until for some magic trick decides to refresh the variable X#<_hal[e.fpxdue]> alone. I think that when its buffer is full deletes, and updates of new variables.
Attachments:

Please Log in or Create an account to join the conversation.

More
24 Sep 2014 23:33 #51539 by andypugh

must insert an M66 that says when the variable X#<_hal[e.fpxdue]> is updated. Otherwise the gcoge runs n times until for some magic trick decides to refresh the variable X#<_hal[e.fpxdue]> alone. I think that when its buffer is full deletes, and updates of new variables.


Yes, buffering (lookahead) is likely to be a problem.

There are some G-codes that force execution to start again (queue-busters) but I am not sure which ones they are. I don't know of one that does it as its prime function, but I think that your M66 might be doing it by accident.

M71 looks like a candidate.
The following user(s) said Thank You: bkt

Please Log in or Create an account to join the conversation.

Time to create page: 0.203 seconds
Powered by Kunena Forum