Machsupport Forum

Mach Discussion => Mach4 General Discussion => Topic started by: Screwie Louie on June 06, 2015, 12:16:55 AM

Title: Mach 4 Logging...how do you get around this bugger?
Post by: Screwie Louie on June 06, 2015, 12:16:55 AM

...Can't transition from "Idle" on event "Stop"....

how do we make mach 4 transition to Idle?

sequence:
1. start movement
2. input0 changed from low to high
3. mcCntlCycleStop() called
4. Gcode running changed from high to low
5. mach_state_stop
6. S_IDLE_on_entry
6. waiting on SetStill is Done!
7. attempt transition from "MDI running" on event "stop"
8. can't transistion from "idle" on event "stop"

then it repeats last cycle.... >:(

any advice?

--josh

Title: Re: Mach 4 Logging...how do you get around this bugger?
Post by: Screwie Louie on June 06, 2015, 01:55:47 AM

assert function? "I assert you!" ...yah, and m4 gives me the middle finger! I tried that with the girlfriend. DIDN'T WORK OUT!

seriously though, this is the last step I need to get by.....so close!

Title: Re: Mach 4 Logging...how do you get around this bugger?
Post by: Screwie Louie on June 11, 2015, 06:48:53 AM

just wanted to say something. this error has nothing to do with Mach 4. It is my own error that was caused by me doing a work around on my limitations. (that's why I asked for help) I was trying to report messages to m4 core whereas m4 was receiving messages at the same time causing the conflict. I jut wanted to put that out there. that's all....

--j