Some issues with Roborun 1.6
7 years 3 months ago #29532069
by maple
Some issues with Roborun 1.6 was created by maple
I don't know if these are bugs, just seems strange to me. Using controller MDC2230S.
1. I am configuring DOut2 for "no MOSFET failure" in my script. This works OK. If I go to configuration tab and change it to "Never", than save to controller it is saved OK too. Restarting script correctly re-configures it back to "no fail".
The problem, however, is that after I did this first time the DOut2 indicator on Run tab switched ON and it does not go away even if I manually reconfigure it to "never" and save to controller. The only way to switch it off is to configure output to trigger on something different from "never" or "no fail".
2. Sometimes after loading configuration from controller some settings immediately marked with "*" as if they have been changed already. I've seen this couple times with "Amps trigger action" and I believe another parameter (don't remember which one).
3. "Help" button on Scripting tab does not work anymore (worked fine in 1.5). I am getting message "The system cannot find the file specified".
1. I am configuring DOut2 for "no MOSFET failure" in my script. This works OK. If I go to configuration tab and change it to "Never", than save to controller it is saved OK too. Restarting script correctly re-configures it back to "no fail".
The problem, however, is that after I did this first time the DOut2 indicator on Run tab switched ON and it does not go away even if I manually reconfigure it to "never" and save to controller. The only way to switch it off is to configure output to trigger on something different from "never" or "no fail".
2. Sometimes after loading configuration from controller some settings immediately marked with "*" as if they have been changed already. I've seen this couple times with "Amps trigger action" and I believe another parameter (don't remember which one).
3. "Help" button on Scripting tab does not work anymore (worked fine in 1.5). I am getting message "The system cannot find the file specified".
The following user(s) said Thank You: blake
Please Log in or Create an account to join the conversation.
7 years 3 months ago #29532070
by blake
Replied by blake on topic Some issues with Roborun 1.6
Thank you for informing us of these possible bugs, we will look into them right away. For testing purposes can you please tell me which controller you are using?
Please Log in or Create an account to join the conversation.
7 years 3 months ago - 7 years 3 months ago #29532071
by maple
Replied by maple on topic Some issues with Roborun 1.6
it is right in the first line of my post - MDC2230S
Oh, and also
4. Roborun crashes when controller power switched off or USB disconnected. But I believe I've seen on forums that this is known bug.
One unrelated to Roborun problem - my customer recently ordered FDC3260 3-channel controller. The device came in with rear plate from some 2-channel brushless model, so all the markings on motor connectors are off. Just thought I'll post it here FYI.
Oh, and also
4. Roborun crashes when controller power switched off or USB disconnected. But I believe I've seen on forums that this is known bug.
One unrelated to Roborun problem - my customer recently ordered FDC3260 3-channel controller. The device came in with rear plate from some 2-channel brushless model, so all the markings on motor connectors are off. Just thought I'll post it here FYI.
Please Log in or Create an account to join the conversation.
7 years 3 months ago #29532082
by blake
Replied by blake on topic Some issues with Roborun 1.6
I apologize for the late reply I must have missed this post.
Yes the USB crash is a known bug, we are addressing it.
The mislabeling is a mistake in production and should not have happened. The wiring labels are available on the FBL2360 datasheet if you can live with the incorrectly labeled face plate of the controller. But if you'd like we will replace it with one that is correctly labeled. Contact me at This email address is being protected from spambots. You need JavaScript enabled to view it. if you'd like to do this.
Thanks again
Yes the USB crash is a known bug, we are addressing it.
The mislabeling is a mistake in production and should not have happened. The wiring labels are available on the FBL2360 datasheet if you can live with the incorrectly labeled face plate of the controller. But if you'd like we will replace it with one that is correctly labeled. Contact me at This email address is being protected from spambots. You need JavaScript enabled to view it. if you'd like to do this.
Thanks again
Please Log in or Create an account to join the conversation.
Moderators: tonysantoni
Time to create page: 0.060 seconds
