RoboPlus - The new software that replaces BCP/Motion Edit,..
by PedroR
Fri Sep 18, 2009 2:47 pm
Hi Kashi
I'll try the "Edit all pages" again. I tested it but it didn't seem to have any effect. Maybe I missed the point LOL
With regards to 1.0.11.0 it was my mistake. There is only 1.0.10.0 available now.
With regards to the controller going to other modes, I think it depends on the program you are using.
For Roboplus Motion it sets itself to PROGRAM but for example for Roboplus Manager the controller is set to Manage I think.
Also, I am still having this odd behaviour where sometimes the Roboplus programs don't start. They show up in Task Manager but no window appears.
I'll download the Process Monitor from Sysinternals to inspect what's going on under the hood. Maybe it can give me some more insight.
I'll try the "Edit all pages" again. I tested it but it didn't seem to have any effect. Maybe I missed the point LOL
With regards to 1.0.11.0 it was my mistake. There is only 1.0.10.0 available now.
With regards to the controller going to other modes, I think it depends on the program you are using.
For Roboplus Motion it sets itself to PROGRAM but for example for Roboplus Manager the controller is set to Manage I think.
Also, I am still having this odd behaviour where sometimes the Roboplus programs don't start. They show up in Task Manager but no window appears.
I'll download the Process Monitor from Sysinternals to inspect what's going on under the hood. Maybe it can give me some more insight.
by PedroR
Fri Sep 18, 2009 4:05 pm
New things I have just learned:
1)
When you are running a R+ Task program and start seeing the TX light blink too much it means the interpreter is sending errors over the COM port.
Open R+ Terminal and you'll see them.
This is something really cool which I don't if it was available in BCP: the interpreter on the CM5 throws out any errors that may be encountered.
In my case I just upgraded a CM5 from a custom firmware to R+ firmware. Whenever I try to play a page it spits out "Invalid Page Read" on the Terminal, probably because the memory structure is not in conformity with what the firmware expected.
Nevertheless it's nice that it sends out the warnings.
2)
When reading parameters from non-existent devices it seems to return some odd numbers.
For example reading current position on an inexistent AX-12 will return -1 (makes sense).
However reading the "Center IR Sensor" and "Sound Count" from the AX-S1 returns 255 when the S1 is not connected to the bus.
For consistency sake it should return -1 as well.
This is some weird behaviour.
3)
I've also noticed there is not REDO command in R+ Task.
There is UNDO but no REDO.
Maybe things happens in other R+ modules as well.
1)
When you are running a R+ Task program and start seeing the TX light blink too much it means the interpreter is sending errors over the COM port.
Open R+ Terminal and you'll see them.
This is something really cool which I don't if it was available in BCP: the interpreter on the CM5 throws out any errors that may be encountered.
In my case I just upgraded a CM5 from a custom firmware to R+ firmware. Whenever I try to play a page it spits out "Invalid Page Read" on the Terminal, probably because the memory structure is not in conformity with what the firmware expected.
Nevertheless it's nice that it sends out the warnings.
2)
When reading parameters from non-existent devices it seems to return some odd numbers.
For example reading current position on an inexistent AX-12 will return -1 (makes sense).
However reading the "Center IR Sensor" and "Sound Count" from the AX-S1 returns 255 when the S1 is not connected to the bus.
For consistency sake it should return -1 as well.
This is some weird behaviour.
3)
I've also noticed there is not REDO command in R+ Task.
There is UNDO but no REDO.
Maybe things happens in other R+ modules as well.
by Khashi.E
Sat Sep 19, 2009 10:00 am
Hi Pedro,
I've downloaded process monitor v2.7 from here & more software(s) about that.I'm still working to find what roboplus is doing.
I've also found the answer of "why cm-5 goes to other modes?"
-because before I connect cm-5 to my pc, it was working in manage or play mode.this is one of roboplus motion or cm-5 new firmware problems.
any news?
BTW:did you try "edit all pages" tab? it works?
regards;
Khashi.E
I've downloaded process monitor v2.7 from here & more software(s) about that.I'm still working to find what roboplus is doing.
I've also found the answer of "why cm-5 goes to other modes?"
-because before I connect cm-5 to my pc, it was working in manage or play mode.this is one of roboplus motion or cm-5 new firmware problems.
any news?
BTW:did you try "edit all pages" tab? it works?
regards;
Khashi.E
by Suicidal.Banana
Sat Sep 19, 2009 11:26 am
PedroR wrote:Hi guys
Suicidal.Banana:
- Thank you for your input!
1)
I would like to ask you one more thing: have you performed the "Controller Recovery Wizard" after the installation of v 1.0.10.0?
I believe the philosophy ... on the toolbar you'll find a button for this function).
The Roboplus manager app wont start, it trows me an error "Unable to find control table"
PedroR wrote:2)
Also, have you tried creating and downloading and Roboplus Task file to the robot?
Does it work on Robolus Task when you download the file?
Yes, the RoboPlus Task thing does work, i made a simple test with it (rotate humanoid arm based on distance from center ir) and it worked great.
PedroR wrote:3)
I have just tested Roboplus on a new CM5 that I upgrade with this new version (1.0.10.0) using Controller Recovery Wizard and I was able to connect to the controller successfully so it may be a local issue to your computer that would be really nice if we could explore to further find any eventual bug.
I'd like to ask you: ifyou run the "Auto Search" functionality in Roboplus Motion to automatically detect in which com port it is attached, does it report that it finds any controller?
...
Regards
Pedro.
I cant reach the controller recovery wizard, because the roboplus manager wont start.
If i use the auto search option, i get the exact same error like before, the "No controller found. Please check the below." one
Some things that might have to do with it;
- Does it maybe have to do with 32/64bit? i run a 64bit vista
- I noticed some1 post they have a cm5 with 1.1960 firmware, mine says [CM-5 Version 1.15] at the top of robot terminal (1.07, pre R+) is that 1.15 the firmware version?
Also while i was testing things, after playing some pages trough the 'old' terminal, R+ trows the "Could not find file ... RoboPlus\Manager\ManagerFirmware.txt" error when i start it (the main R+ app), guess it does somehow relate to my previous install then, is there a reg file or such available to completelly remove R+?
by PedroR
Mon Sep 21, 2009 12:06 pm
HI
the 1.15 you see may be the bootloader version (not sure).
If you had previously ran the "Controller Recovery Wizard" with the previous version of R+ you should be running a later version of the firmware.
With regards to your issue thank you for the information that it is a 64bit Vista.
It is most likely the cause of the error. 64 bit windows uses an indirection mechanism to place the 32bit executables in a separate "PROGRAM FILES" directory ("PROGRAM FILES (x86)") although to the running app it should look like the regular "PROGRAM FILES" folder.
The other user who experienced the error had installed it to "c:\PROGRAMDATA" so it seems to indicate the error occurs whenever the software is installed to a folder other than "PROGRAM FILES".
I am inclined towards the fact that they hard coded "C:\PROGRAM FILES" as the location of the file mentioned instead of looking for the file in the same place where ROboplusManager.exe is installed.
I am running my own test on my side (installing R+ to "c:\rplus") to see if I can reproduce the problem.
Thank you for your info Suicidal.Banana. It seems we are closing in on this bug
I will let Robotis know about this issue.
Also if you have the opportunity try and install the previous Roboplus version (10.2.
and try to see if it works.
We haven't had any report of this issue with the previous version so you may be able to run that one...
the 1.15 you see may be the bootloader version (not sure).
If you had previously ran the "Controller Recovery Wizard" with the previous version of R+ you should be running a later version of the firmware.
With regards to your issue thank you for the information that it is a 64bit Vista.
It is most likely the cause of the error. 64 bit windows uses an indirection mechanism to place the 32bit executables in a separate "PROGRAM FILES" directory ("PROGRAM FILES (x86)") although to the running app it should look like the regular "PROGRAM FILES" folder.
The other user who experienced the error had installed it to "c:\PROGRAMDATA" so it seems to indicate the error occurs whenever the software is installed to a folder other than "PROGRAM FILES".
I am inclined towards the fact that they hard coded "C:\PROGRAM FILES" as the location of the file mentioned instead of looking for the file in the same place where ROboplusManager.exe is installed.
I am running my own test on my side (installing R+ to "c:\rplus") to see if I can reproduce the problem.
Thank you for your info Suicidal.Banana. It seems we are closing in on this bug
I will let Robotis know about this issue.
Also if you have the opportunity try and install the previous Roboplus version (10.2.
and try to see if it works.
We haven't had any report of this issue with the previous version so you may be able to run that one...
by Suicidal.Banana
Mon Sep 21, 2009 12:33 pm
Hey PedroR,
Thanks for the reply,
- I didnt run the 'Controller Recovery Wizard' before.
- Once im home ill try what happens if i copy over the R+ directory from 'Program Files(x86)' to the normal 'Program Files' dir, why didnt i think of that myself... if that wont work (some paths may not be hardcoded) ill try reinstalling in 'Program Files'
- If those dont make it work again, ill uninstall the last version and install the previous version, and see if that one works.
Will post again when im home later today.
Thanks for the reply,
- I didnt run the 'Controller Recovery Wizard' before.
- Once im home ill try what happens if i copy over the R+ directory from 'Program Files(x86)' to the normal 'Program Files' dir, why didnt i think of that myself... if that wont work (some paths may not be hardcoded) ill try reinstalling in 'Program Files'
- If those dont make it work again, ill uninstall the last version and install the previous version, and see if that one works.
Will post again when im home later today.
by PedroR
Mon Sep 21, 2009 4:56 pm
Hi suicidal.banana
Thank you for your input.
I was trying to test this behaviour myself by installing to a folder different from "PROGRAM FILES" but I can't seem to be able to start RoboplusManager.exe in this computer.
It's the behaviour that has been seen before by some other user where the process starts and appears in task manager but no window shows up.
(although running a stack trace on it, seems to indicate there are API calls to show the window).
It's most likely some .Net issue that someone with more experience might know. I'm on a dead end here.
Please note this only happens on this computer of mine (on others it works OK) and I have no clue as to what could be causing this.
Thank you for your input.
I was trying to test this behaviour myself by installing to a folder different from "PROGRAM FILES" but I can't seem to be able to start RoboplusManager.exe in this computer.
It's the behaviour that has been seen before by some other user where the process starts and appears in task manager but no window shows up.
(although running a stack trace on it, seems to indicate there are API calls to show the window).
It's most likely some .Net issue that someone with more experience might know. I'm on a dead end here.
Please note this only happens on this computer of mine (on others it works OK) and I have no clue as to what could be causing this.
by PedroR
Tue Sep 22, 2009 12:46 pm
Hi suicidal.banana
Glad to know we figured this one out (YAY)
I don't know if you've tested the samples I produce but I have found a kind of bug in Sample 2:
There is a condition that switches the AUX led on and off as you press the R key.
What I've come to realise is that it does not work reliably (you press it and sometimes it turns On or Turns Off) and after much though, I finally figured out why:
- The software iterates through the loop at a high speed.
Every time the software iterates through the IF it will see if R is pressed and if it is it will toggle the LED on or off.
The software does it so fast that the led seems to always be on while you're holding the button but that's no the case.
This happens because the language is not event driven. The way I programmed it I assumed it was an event driven model and was coding for something like a KEYDOWN event: when I pressed R it would trigger a one time event, toggle the led and wait for the next EVENT.
However Roboplus is more low-level meaning it just checks the state of the signal on the button. Whenever it iterates the loop, if the button is pressed it toggles the status of the LED.
So work around this issue, you probably need to add a line just bellow setting the LED on or off like this:
Instruction: CONDITIONAL STAND
It should say something like STAND WHILE (BUTTON R Pressed = TRUE)
This halts execution until you release button R fixing the bug.
However it will also halt execution altogether for other instructions so you may want to avoid this approach f you are coding a high performance app (there are other work arounds for this same issue for high performance scenarios but require some more fixing)
Glad to know we figured this one out (YAY)
I don't know if you've tested the samples I produce but I have found a kind of bug in Sample 2:
There is a condition that switches the AUX led on and off as you press the R key.
What I've come to realise is that it does not work reliably (you press it and sometimes it turns On or Turns Off) and after much though, I finally figured out why:
- The software iterates through the loop at a high speed.
Every time the software iterates through the IF it will see if R is pressed and if it is it will toggle the LED on or off.
The software does it so fast that the led seems to always be on while you're holding the button but that's no the case.
This happens because the language is not event driven. The way I programmed it I assumed it was an event driven model and was coding for something like a KEYDOWN event: when I pressed R it would trigger a one time event, toggle the led and wait for the next EVENT.
However Roboplus is more low-level meaning it just checks the state of the signal on the button. Whenever it iterates the loop, if the button is pressed it toggles the status of the LED.
So work around this issue, you probably need to add a line just bellow setting the LED on or off like this:
Instruction: CONDITIONAL STAND
It should say something like STAND WHILE (BUTTON R Pressed = TRUE)
This halts execution until you release button R fixing the bug.
However it will also halt execution altogether for other instructions so you may want to avoid this approach f you are coding a high performance app (there are other work arounds for this same issue for high performance scenarios but require some more fixing)
by Khashi.E
Tue Sep 22, 2009 3:11 pm
Pedro wrote:There is a condition that switches the AUX led on and off as you press the R key.
What I've come to realise is that it does not work reliably (you press it and sometimes it turns On or Turns Off) and after much though, I finally figured out why:
- The software iterates through the loop at a high speed.
Every time the software iterates through the IF it will see if R is pressed and if it is it will toggle the LED on or off.
The software does it so fast that the led seems to always be on while you're holding the button but that's no the case.
This happens because the language is not event driven. The way I programmed it I assumed it was an event driven model and was coding for something like a KEYDOWN event: when I pressed R it would trigger a one time event, toggle the led and wait for the next EVENT.
However Roboplus is more low-level meaning it just checks the state of the signal on the button. Whenever it iterates the loop, if the button is pressed it toggles the status of the LED.
So work around this issue, you probably need to add a line just bellow setting the LED on or off like this:
Instruction: CONDITIONAL STAND
It should say something like STAND WHILE (BUTTON R Pressed = TRUE)
This halts execution until you release button R fixing the bug.
However it will also halt execution altogether for other instructions so you may want to avoid this approach f you are coding a high performance app (there are other work arounds for this same issue for high performance scenarios but require some more fixing)
Good news Pedro
I've crated a task file that turns aux led on/off by pressing U button without any problem. when you press U button, aux turns on at the moment.if you hold the button, status of led will not change!
EDIT:the file is RAR and has a video & task file.download it here & try it yourself
regards,
Khashi.E
Last edited by Khashi.E on Wed Sep 23, 2009 7:53 am, edited 4 times in total.
by HGM
Tue Sep 22, 2009 7:41 pm
PedroR wrote:The other user who experienced the error had installed it to "c:\PROGRAMDATA" so it seems to indicate the error occurs whenever the software is installed to a folder other than "PROGRAM FILES".
Hi Pedro,
Not sure if this refers to my problem but in case it does, I don't have the program installed in C:\ProgramData. That is the error message I get every time I fire up RoboPlus (image below). Once I click on "OK", the program opens up normally. Then I have other problems that I can elaborate on in another post.
Harry
by PedroR
Mon Sep 28, 2009 12:24 pm
Hi Harry
Sorry for the late reply. I'm really busy preparing the Christmas season at Robosavvy (yes, we stores start preparing really early )
1) I would like to ask you which operating system you are running.
Is it Vista? If so is it 32bit or 64 bit?
2) I would also like to ask you in which folder you installed Roboplus.
In a last effort, if you can't fix your issue, then just copy the whole ROBOTIS folder where Roboplus is installed to the c:\ProgramData folder (if it doesn't exist create it).
This should get Roboplus running. It is not the correct fix but it will make it work for now until the error is fixed.
In any case please let us know the info I requested above, please, so we can further investigate the issue.
Regards
Pedro.
Sorry for the late reply. I'm really busy preparing the Christmas season at Robosavvy (yes, we stores start preparing really early
)
1) I would like to ask you which operating system you are running.
Is it Vista? If so is it 32bit or 64 bit?
2) I would also like to ask you in which folder you installed Roboplus.
In a last effort, if you can't fix your issue, then just copy the whole ROBOTIS folder where Roboplus is installed to the c:\ProgramData folder (if it doesn't exist create it).
This should get Roboplus running. It is not the correct fix but it will make it work for now until the error is fixed.
In any case please let us know the info I requested above, please, so we can further investigate the issue.
Regards
Pedro.
by HGM
Mon Sep 28, 2009 3:32 pm
Hi Pedro,
No problem with your late replay, I've been busy on other things also.
I'm running Vista 64 and installed RoboPlus in the installation default directories. That means it was put into C:\Program Files(x86).
I just tried to create a new folder called ProgramData in the C: directory but it doesn't show up in Explorer. When I do a search it does show up, with a whole bunch of subdirectories including Robotis. The Robotis directory doesn't have the executable in it. Not sure what is happening there.
I haven't got much time to play around with this Vista problem right now and will likely leave it till Windows 7 is available.
Cheers,
Harry
No problem with your late replay, I've been busy on other things also.
I'm running Vista 64 and installed RoboPlus in the installation default directories. That means it was put into C:\Program Files(x86).
I just tried to create a new folder called ProgramData in the C: directory but it doesn't show up in Explorer. When I do a search it does show up, with a whole bunch of subdirectories including Robotis. The Robotis directory doesn't have the executable in it. Not sure what is happening there.
I haven't got much time to play around with this Vista problem right now and will likely leave it till Windows 7 is available.
Cheers,
Harry
bugs
by syperious
Fri Oct 23, 2009 5:15 am
first post ever, woot
I'm playing with roboplus task editor right now.. aside from the error on the .txt file when clean install, I have found couple bugs (sorta) on the editor..
1. since i'm playing with a boomerang, I have this line "if (id[100]:IR COM RXD == U then )", it was easy enough since all i had to click through to get the values. now when i try to change the "U" value to, say, "R", that drop down list isn't there anymore, instead i got this Variable tag, and changing it doesn't work.
2. you can't import old motion files directly
( of course this isn't a bug, but it's super inconvenient...
Anyways, hope this is helpful!
edit:acutally, upon further inspection, for this phrase "if (id[100]:IR COM RXD == U then )", you have to change the first part to a value like 'U' 'R' 'L' 'D' or etc, to make the second part actually be able to pick them.. then you have to change the first part back to "IR COM RXD"
I'm playing with roboplus task editor right now.. aside from the error on the .txt file when clean install, I have found couple bugs (sorta) on the editor..
1. since i'm playing with a boomerang, I have this line "if (id[100]:IR COM RXD == U then )", it was easy enough since all i had to click through to get the values. now when i try to change the "U" value to, say, "R", that drop down list isn't there anymore, instead i got this Variable tag, and changing it doesn't work.
2. you can't import old motion files directly
( of course this isn't a bug, but it's super inconvenient...
Anyways, hope this is helpful!
edit:acutally, upon further inspection, for this phrase "if (id[100]:IR COM RXD == U then )", you have to change the first part to a value like 'U' 'R' 'L' 'D' or etc, to make the second part actually be able to pick them.. then you have to change the first part back to "IR COM RXD"