Classicladder sending M code back to Linucnc Possible ?

I finally got a working PnP Ladder logic operational and I am now looking to inprove it. Currently I am using M64 P## to signal a
feeder to fire and M65 P## to reset for the next feeder command. My question is, Is it possible to have ClassicLadder issue
the M65 P## instead of me writting it into the Gcode ?

Try to to connect PLC output to halui.mdi-command-xx

Aciera wrote:

Mind you, you cannot get classicladder to issue a gcode command while in AUTO mode (ie while running a gcode program). AUTO mode and MDI mode are mutually exclusive.
 

I was wondering if that's the case . Looks like I will have to get to work on an M1## code. For now though I will have to continue using
M64 and M65 codes . Or continue refining my Ladder logic.

 Well I no longer need M64 and M65 to fire the feeders . It was actually easier to write individual M1## codes to perform the
same function except way better. I had to change the ladder logic a little bit to get the feeders to fire correctly but Ironicly
it shortened the ladder read time . The catch ( their's always a catch ) is I have to currently use 48 seperate M1## codes
for the current setup to work. The next step is to write a Bash scheme to utillize the P word so that I need only 1 M1##
to actuate the feeders. One BIG caveat,  I am not a Bash , Python, or C programmer so it will take me a while to get up to
speed on making this next step work ,sigh . Problem number 2 for some dumb reason I cant get the LinuxPnP computer to
recognize the M1## codes . I got my computer at home to see them just fine . The exacutable box is
check marked on the properties tab for each M1## file. I'm not sure if it's a 6i26 / 7i76 problem or what.
That said I do know the codes work. (at home at least)

Aciera wrote:

Are you getting any error messages in the terminal?
 

The only warning I have seen is in linuxcnc " unknown M code used  ". Though I will say
I haven't look on terminal to see what it comes up with . Mainly because I don't know
what I am doing in that regard .

here are a couple of my M codes. Maybe someone will see something I am missing.

  So from one of my very recently acquired books (Linux Command Line and Shell Scripting Bible ) I went onto my 
home system to see if it would show if the files are executable . I cd to the linuxcnc file , cd to nc_files , cd to M_codes file
then ls -l the M codes. So far ( on my home system at least  ) they all read executable. I wonder if I will have to manually
set the M1## bash files on the system at work to executable.