Re: Interpreter failure

[Ray Henry <rehenry-at-up.net>]

Hi Peter

I looked up the problems that I had with tkio and it is a couple of lines 
that were supposed to be commented with # but were commented with // instead. 
(all these languages are so confusing <g>)

line 865 change // to #
line 877 change // to #

That should keep tkio running rather than crapping out when it hits those 
errors.  I'll commit these changes to the sourceforce site in a bit.

The tkio file that runs during startup is in emc/plat/nonrealtime/bin so 
change that one.  If you plan to re-compile or re-install you will also need 
to change the same named file in emc/src/emcio.

Tkio does find the defined parport in the ini file.  It will default to 378 
if none is specified.

In order to use tkio you will need to specify bridgeporttask so that task 
based NML is there to pass info to the io module.

When you use bridgeporttask and bridgeportio, you will get a warning message 
saying that when you turned estop off through the gui, and emc turned estop 
off, nothing happened to the state of the estop pin on the i/o parport.  What 
is presumed to happen here is that when estop is turned off, and i/o parport 
output number 10 changes state, external hardware will pull a relay that 
grounds the corresponding input estop signal.  When that doesn't happen, the 
warning comes up.  (pretty confusing, eh!)  The purpose of this round robin 
approach is so that pressing an external estop will signal the controller 
that the machine has faulted out so it ought to also stop asap.

Hope this helps.

Ray


On Thursday 27 June 2002 22:02, Peter wrote:
> Hi Ray and list.
>
> I was wondering if you looked at the tkio thing.. I guess you may have seen
> my post saying that tkio started up no worries for me and you decided not
> to worry about it.
>
> Well, I can say that tkio starts up ok and the little window with heartbeat
> etc. gets going. Everything seems OK but I have been trying to set up
> hardware on the second parport (0x278)
> tkio does not seem to see the ports.
>
> When I use bridgeportio I can start ioshow and see what the bits are doing.
> Everything goes fine and I can turn limit and estop switches on and off.. I
> can make an old stepper motor out of a dead printer to turn on command.
> The only thing thaty doesn't happen is that the Estop send bit does not
> respond when the button is pushed, so I get a message saying something like
> "The Estop send bit was read back and indicates bit is still set......
> check connections port settings etc." (The program still comes out of
> estop. I ended up just editing the polarity of the bit to get rid of the
> message)
>
> Tkio seems to be completely port-deaf (and dumb)
>
> It would be good to find some more documentation about playing with
> tkio.tcl.
> I have tried to follow the stuff in the manual about inb and outb and iosh
> but I'm a tcl beginner.
>
> 8*d
>
> It would appear that if I can master this part of emc I can sort out some
> plc for my machine.
>
> thanks for your time and patience
>
> Peter Barrett
>
> > The last time that I ran tkio, there was some kind of problem with the
>
> code.
>
> > Seems like it had been crunched when it went thought someones editor.  If
>
> you
>
> > get a message about that file, try bridgeportio for a day or so and  I'll
> > look for the problems and list them.
> >
> > Ray