Mac
I'd like to use the 160x120 resolution in my project running ARC (the latest version) for Windows on a Windows 10 Surface Pro 2 but I get the following error:
11/3/2018 11:37:43 AM - Error Camera.SetCaptureImage: AForge.Imaging.UnsupportedImageFormatException: Source pixel format is not supported by the filter. at AForge.Imaging.Filters.BaseTransformationFilter.CheckSourceFormat(PixelFormat pixelFormat) at AForge.Imaging.Filters.BaseTransformationFilter.Apply(BitmapData imageData) at AForge.Imaging.Filters.BaseTransformationFilter.Apply(Bitmap image) at EZ_B.Camera.eihiq5ToKN(Object )
It runs at 320x240 okay but uses a lot of CPU and the image tends to hang or stutter and falls behind when face tracking. Anyone else have issues with the surface pro? The exact same builder file works fine on my laptop (with Windows 7).
Thanks
Vertigo, got the nail on the head. All up to you on what to use
. Funny, I use Blockly a ton! Not sure why because I can type a million miles an hour... there’s something about the colored shapes that gets me giddy
Vertigo is correct. They all do the same thing. It's a matter of organization for me. I never use Blocky for the same reason as Vertigo unless I can't figure out the syntax (it's great for that), Single EZ Script controls are great for me to have a much used script up front and easy to find, Script Manager is good for me to put scripts into like category scripts or areas of the robot (one script manager for the head section, one for arms another for legs, exc).
Thats kind of what I would expect to happen, and if that is true for Mac as well, we could have saved a lot of time trying to diagnose and troubleshoot wifi problems, because wifi problems wouldnt cause a reboot.
Of course, to know that, requires you actually witness the event to tell the difference between a reboot and a random wifi related disconnection. For future reference, should something like this happen again, do we have something like an "uptime" command for the ezb controller?
There is an uptime on the comm v2 which he’s using
I've been tracking the uptime using debug. It usually gives me the connect and disconnect times.
So, I diss and re assembled the head, checked the connections and swapped the camera cable but I didn't realize my extra long cable was just an extension (male/female) instead of an actual cable (female/female). So a no-go on verifying the cable integrity. I did, however, find a very small, hard to see, brown spot where one of the wires enters the connector on the camera cable. It's not burned through but definitely brown.
I decided to put it all back together but without the Nook and resin face to lighten the load on the servo. Thinking maybe the servo load was browning out the EZB. But it disconnected after about 15 minutes.
I'm just waiting for the new hardware at this point.
Thanks for explaining the scripting differences. I only have two servos controlling one camera so I have no need for script managers, etc.
That brown spot is suspect. Can you cut the good end off the extension and splice it to the old cable to replace that suspect connection? Just for testing?
Do you have a new camera cable coming also? If not you can make your own. Either way you should have a extra one on hand.
meaning, the disconnect was caused by (or at least happened along with) a reboot?
While waiting for the new camera, why dont you try without camera? Sure, your robot may not do a whole lot (I have no idea what it is or does), but you could still monitor your wifi and record your uptime. Maybe add some random servo movement if you want to add some stress to the system.
BTW, I took my camera apart to mount it in the inmoov eye. I noticed it had a pretty decent sized heatsink attached to the bottom, and I assume its not there for good looks. Is it possible it overheats after an extended period time? The camera casing doesnt have much, or well, any ventilation.
@Dave I thought about doing just that, splicing them together. But I wasn't sure how important shielding would be. I thought it best not to introduce any other variables but maybe you're right. I have some heat shrink tubing around here somewhere.
@vertigo camera overheating was one of the first things I thought about but the camera isn't in the housing; it's completely exposed to the air and isn't even warm to the touch after hours of being powered-up.
One of the reasons I didn't jump on Alan's suggestion of a bad camera right away was specifically because his EZB would reboot. Mine does not. Never has since the problem started. In AP mode, the camera disconnects first, followed by the EZB. Which makes sense if what Dave says is true; that commands sent to a non-functioning camera will make the EZB disconnect. In Client mode, it was the EZB disconnecting with no camera error.
Okay then, looks like I have some splicing to do. But first, @vertigo, this isn't as much a robot as it is an artwork. "iRobot; If you prick us, do we not bleed" is part of a series of sculptures I'm working on called The Classics. All the artworks are based on classic literature. Check 'em out
http://studio407.net/recent_work.htm