Hi Guys:
As you can see from the left picture above, I turn the do[91]/do[93] on, and the GO[2] should be number 5 while it responds with nothing. It's shown in the right picture that I group out number 2, and the corresponding digital out signals don't change.
I check the Group Output signals configuration which is correct.
Group Output[2] Signal shows number 1 after moving robot to "Home" Position while the corresponding digital output signals take no change.
I take the test with painting tool, and everything works all right with handing tool.
So....
Has anybody happen to know the cause of this Group output signals problem?
Check the configuration (rack, slot, start, num) of the GO via MENU > I/O > Group > CONFIG. Post a picture of the mapping if you are not sure about it.
I have no idea about PaintTool, sorry... It seems that the GO is controlled by a KAREL program. Is your IO configuration a default PaintTool setting or did you do this by your own?
Display More
I check the Group Output signals configuration which is correct.
Group Output[2] Signal shows number 1 after moving robot to "Home" Position while the corresponding digital output signals take no change.
I take the test with painting tool, and everything works all right with handing tool.
So....
Has anybody happen to know the cause of this Group output signals problem?
in start instead of 91,92,93 and 94 put only 1
in start instead of 91,92,93 and 94 put only 1
But that would map the signals to another place in the I/O-area specified by Rack/Slot....
Or Maybe you just menat to say that he could map DO[91-94] on one line?
DO[91-94] RACK:67 SLOT:1 START:91
I have no idea about PaintTool, sorry... It seems that the GO is controlled by a KAREL program. Is your IO configuration a default PaintTool setting or did you do this by your own?
I took the test with a virtual robot created using onsite backup files, I also test with a default PaintTool setting, and neigher way works.
But, it works as the instructional video of youtube when I tested with a default handtool setting.
All the tests are done in the roboguide.
GO Config is ok, so it's your karel program issue.
1. guess that .pc is background running? so condition will force the GO value...
2. replace POS_TOL 0.1 to a bigger value , e.g 1 and try again
GO Config is ok, so it's your karel program issue.
1. guess that .pc is background running? so condition will force the GO value...
2. replace POS_TOL 0.1 to a bigger value , e.g 1 and try again
Thanks for your response.
The point is the configured Digital Output Signals do not respond with corresponding Group Out Signal.
when robot is at home position, Group Out #2 signal Ought to be number 1 which means the robot is Home.
