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
Dave, thanks for the pointers. And I [i]really[i] like the idea of starting from scratch with Builder. But there's been a development: Last night I used my i5 laptop running windows 10, again turning off the sleep setting for the wife adapter, and it ran all night without disconnecting. So it's still possible! I reset the Surface, hoping to get it back to Win 8 but it wiped and reinstalled 10. When a person upgrades to 10, does it also upgrade the reset partition or did the Surface Pro 2 come with 10?
DJ, Hardwiring is plan B
Unknown but I'm sure someone here with more information can answer. Sorry.
Or Uncle Google might know. Sometimes I get plain lazy, lol. Or, more accurately, just busy. I will report back.
I've been doing some very careful testing, still trying to eliminate the dropped connection problem. The other night I ran builder along with the old command prompt Ping-t. What I discovered was that the wifi connection from the Surface Pro 2 to the EZB did not drop but builder did disconnect. Always with the camera error. I made a mistake; the wifi connection was not dropping, which would be why all the Windows settings changes didn't help. Today, I made a mobile app from my latest builder file and iRobot from that. After about 1.5 hours, the app was still connected but the camera picture had been replaced with the camera icon (like when builder is disconnected from the EZB). I touched the icon and camera image came back. It was like the camera went to sleep. But I have no sleep script running. I'm leaning towards a bad camera.
DJ, if you're still reading this thread, hard-wiring is still plan B but since the wifi isn't disconnecting, I have reservations. Is it possible to order a new camera without the housing since I won't be using it?
Our logistics warehouse doesn’t store inventory of the camera without housing
I doubt it’s a defective camera - because electronics work or don’t work. I’m guessing the disconnect is one of two things...
WiFi interference or driver causing delay resulting in a timeout
camera overheating if not vented
It’ll be one of those two. The option #1 still doesn’t mean the WiFi has to disconnect. It means something is causing the data to timeout. One option is to log icon pong responses with a datetime stamp to the ezb and see If there are transmission errors.
I did see a couple of ping responses around 3.8 seconds. Seems like a lot. It's odd though that the disconnect always happens in the middle of the night when there's less chance of interference.
"One option is to log icon pong responses with a datetime stamp to the ezb and see If there are transmission errors." Could you point me to somewhere I could learn to do this?
I thought about the camera overheating. It doesn't have a housing of any kind so shouldn't need venting but I do have a bit of epoxy on the side of the heat-sink.
Here, use this. I whipped it up for you: DJ'sSuperDuperICMPLogger.zip
It'll also log the time to a file in the same folder as the EXE. Enter the IP Address of the EZ-B in the textbox where it current says google.ca