On 03/14/2011 06:16 PM, Kirk Wallace wrote: > On Mon, 2011-03-14 at 12:22 -0400, Mark Wendt wrote: >> On 03/14/2011 12:20 PM, Kirk Wallace wrote: >>> On Mon, 2011-03-14 at 05:37 -0400, Mark Wendt wrote: >>> ... snip >>>> Are you already starting it from a launcher on the desktop? >>> ... snip >>> >>> Yes, I tried that a couple of times, but mostly I have been trying to >>> get back to the terminal from the halcmd: prompt, which needs to happen >>> first. >> >> Kirk, >> >> Can you post your startup script? >> >> Mark > > I have a shell script called config_modio that contains: > " > cd /home/kwallace/emc2/homann/modio_config > halrun -I h_modio_config.hal
Make sure there's no CR/LF after the h_modio_config.hal. If that doesn't fix it, try "exit" with no quotes as your last line. I think you forgot the "-f" switch to call out the <filename>. > " > > I then created a launcher that calls the config_modio script. From the > launcher, the pyVCP window comes up but the threads immediately stop and > the keyboard locks up. I have to power off to reboot. If I invoke the > script from a terminal, the pyVCP window works fine, but when I close > the window, I am left with a halcmd: prompt, which I need to type exit > to get back to the terminal prompt. Then just put "exit" with no quotes as your last line in the script. Do you really need the halcmd prompt to come up? If not, you can leave out the "-I" > > I tried a bare bones LED pyVCP window with my launcher and it doesn't > lock up the keyboard, but it flashes the LED window and immediately > exits back to the desktop. > > I think the latency test launcher does what I need to do, but it is > fairly involved and will take some time to figure out how it works and > then pick out the juicy bits. > > I also need to go through my modio_config component to see where things > get locked up. I think I need to make it more fault tolerant, especially > when it is trying to set up the serial port, but doesn't succeed. It > seems the -I option gets ignored from the launcher, so the window pops > up, but disappears while the serial port is getting setup. When I run > the script from a terminal, the -I option gets honored and all is well, > except I get returned to the halcmd: prompt because I'm in interactive > or -I mode. Or that's my story so far. If you leave out the -I option, you won't get the halcmd prompt. Mark ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
