elfege
Hi,
Something is terribly annoying : ARC resets its default camera so if you are using a different camera than the ezb camera, any script that is supposed to boot your cam and then start it in the camera settings will not activate the one you want.
Is there a way to select a camera in the list as default and lock it so it stops bugging me like trying to force me to buy the low res ezb camera ?
thank you.
PS : ezb v4 is full of bugs. I can't count how many I meet. It is VERY unstable. Please, provide us with a firmware at some point. It is really very annoying. few examples :
-ezb disconnects -ezb has flawed digital ports : servos and motors won't respond ezb needs to be disconnected then connected again -ezb v4 used in conjunction with ezb V3 will screw all servos mixing up the old 100 position values and the new 180 positions. ARC has a very slow response rate - often due to a wifi board that is too slow, apparently, or a flawed buffer in the software, Idk. -digital ports will all lock to ON position and turn the robot totally nut and crazy -ARC will crash, very often, as soon as more than 3 scripts run at once. -i2C port is far too unstable. and so on... can't remember all the bugs I've encountered but it is really a lot.
As for the camera, save the project with the camera selected. The next time you load the project, the same camera will be started. If you wish to start the camera manually, consult the ControlCommand() specific to the camera control. The learn section can advise you on EZ-Script ControlCommand() as there is a tutorial regarding EZ-Script in the activities course.
PS, all ControlCommand() syntax for each control is visible in the Cheat Sheet tab when editing a script. The activity course in the learn section is a great place to start to learn ARC and to follow programming examples.
Also, use the Script Flow Control to see an overview of the scripts. It will help you see if there are circular references.
Please post your project so we can take a look at the issues you are experiencing. Here are responses to your points.
ez-b will disconnect if the data channel is flooded. a look at your project can resolve that
. Additionally, check to ensure proper delays are used in loops, etc.. this is a disciplinary technique which you will learn with programming. Sleeping allows other threads to share resources, such as network, user interface and more. Without a sleep delay in loops, single process will consume all available resources.
the v3 is discontinued and no longer supported by ez-robot. it is not advised to run both together for the reasons you stated. The servo position count between the two boards are not compatible (v3 has 1-100 positions, while the v4 has 1-180). The software will default to the servo position count of the last connected board.
ARC wifi is not very fast, as it's doing a lot of processing such as audio, video and data. we do have an upgrade available in the new year with a faster processor
. There is no flaw in the current ez-b v4, it's designed to spec.
digital ports float until they are configured by software.
upgrade ARC if you notice some crashes. Although, it does sound like your project can use a little advice. Post it and i'll have a look to clean it up and get you working.
i2c is a communication protocol and is out ez-robot's control. the i2c protocol information is available on the internet, perhaps wikipedia. if you're i2c device is having issues, consult an experienced engineer for a possible solution. i2c devices created by ez-robot are stable because they are designed around the i2c specification. if you are manually building i2c devices, you will run into problems because it's a very fragile protocol. specifically fragile in the sense that it does not like physical wires or long wires without much design consideration.
I personally would not use EZB3 With a EZB4, because of the servo position. DJ on a post long ago was having a buy back of the EZB3 for a credit to upgrade to EZB4 because at some point EZB3 will no long be support. Software wise. EDITED*
@elfege, my apologies for my frustration as well, never post when you're having a Christmas drink. Lol
Sorry DJ you're a lot more tactful then I am plus I'm having a Christmas drink tonight Lol
LOl, thanks Merne
Christmas drink would be a good idea!
Also, make sure you're using the latest ARC. You can submit a diagnostic report as well after crashes/issues, just make sure it's the latest ARC or the diagnostic report will be of no use to us. Instructions are here: https://synthiam.com/Tutorials/Help.aspx?id=220
Another tip for keeping your camera settings as you start new projects (including any recognition you have trained) is to open a new project and use the merge function to copy the camera object from your existing configured project rather than adding a new camera object.
Alan
@elfege Maybe ez robot isn't right for you? I mean it is obviously "annoying you" as stated in pretty much every one of your posts... Perhaps I could recommend ROS? Surely that would not annoy you....
Richard, be nice
everyone has a different threshold of frustration. I also suffer from a little frustration here and there. Mostly it's with using other people's products, which is why I put so much effort to make ezrobot better and continue to increase reliability.
I'm so excited for you all to get the new comm upgrade. Jer and I were running tests tonight, it's a tank! A serious marvel of performance and reliability. Henry, our new Scm is pushing hard at us to get it done - top priority. It will really revolutionize everything.
So, if this poster has some frustrations today - I'm okay with that. Because my days are consumed with ways to make it better
and feedback always helps.
However, it's important that I view projects that provide these experiences. We test really hard to break stuff, but with a programming environment, there's an infinite number of ways to do something, therefore an infinite number of ways to break stuff.
Once I receive his project, it will be easy for me to either identify an ARC fix, or fix the project. Mostly it's fixing projects, but that's also a win
So, post the project and let's get crack'n at fixing this issue.
@DJ.... You suffer from frustrations from this forum? Nah, not you... You're as cool as a cucumber dude...