Ok Guys I'm back. Once again thanks for all the help to this point.

The cameras have been exchanged between Robotshop and myself. Just for clarity this time I thought I would give the particulars of the environment: ...Windows 7 "with all current updates and hardware driver updates" ...Linksys router 2500 "The EZB connects very fast" ...ARC 2017.03.06.00 software ...Microsoft security software "Turned Off" ...Brand new EZBv4 ...Brand new "second" Camera ...3---7.4v lipo batteries "all brand new and charged" ...Disconnected all servo's to avoid interference and loaded a blank environment to avoid interference from other 12C devices.

So far no luck getting the camera to connect. Please watch the short video below to make sure I'm procedurally connecting to the camera correctly. I'm sorry for the bad editing upfront. In the video I clicked twice on the scan button for camera but it makes no difference. Both times it see's the camera but give the Same results. "I posted below"

https://youtu.be/j7A1goevXJs

The debug results are below. First half is EZB connecting Second half is camera. It's been almost a month now since I purchased the EZB so I probably need to decide quickly if the EZB camera port has an issue to comply with Robotshops return policy. Any help would be great! Thanks again everyone.

Reports EZB v4 OS With Comm 2 EZ-B v4 ID: 78-49-0-0-46-255-57-60-59-38-37-37 Setting battery monitor voltage: 7 Setting battery protection: True Setting i2c rate: 100000 EZ-B voltage is 7.999100814 EZ-B temperature is 24.44489368264605312C Connected

Object Recognition Initialized. Object Recognition Initialized. Camera Initialized: EZB://192.168.1.123:24 @ 320x240 EZ-B v4 Camera Error: System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at EZ_B.EZBv4Video.dr0AP6qn6r(Int32 , Object ) Camera Disabled

Have you tried in AP mode instead of client mode?

I always drop back to AP mode when troubleshooting hardware to make sure the router is not causing an issue (it could potentially be blocking port 24, which is used for camera communication, although blocking 23 would have been more likely).

If you get the same error in AP mode, then looks like a problem with the EZ-B (fairly unlikely to have gotten 2 bad cameras in a row). If it works in AP mode, then we need to start looking at your network some more.

Alan

Thanks for responding Alan

I reset the EZB and put it back to default then connected "via" AP mode. Still the same results. I also put the EZB back to client mode, went into my router and changed the EZB to static IP 192.168.1.123 and saved port forwarding to include ports 23 and 24.

I tried to attach the image of the port forwarding so you could tell me if it's correct or not but I don't see where the attachment file is or goes. "there may be two attached of the same". Anyways the port forward didn't seem to work either. Still trying different things.

Attachment was formatted wrong. Here's the port forward

Quote:

I reset the EZB and put it back to default then connected "via" AP mode. Still the same results.

I think we can rule out port forwarding then. Seems either you got another bad camera (unlikely) or there is something wrong with the EZ-B. I think you should try an exchange.

Where are you located? If you are in the Washington/Baltimore area, I would be happy to find a time to bring over a known working EZ-B to try with your computer and make absolutely sure it is an EZ-B issue and not a computer/network issue.

Alan

@Alan... in post #18 he said he got a brand new ezb4 and camera... I think it's his PC and or configuration/antivirus software etc...... Again, I haven't read the whole thread but @Novo did you try a different computer and or Windows OS version?

EDIT Ok, he said brand new ezb4 he never said Brand new "second" exb4... Alan could be right maybe your ezb4 was defective not the camera? This would be an absolute rarity so if it is defective that's just plain bad luck.... I am sure robotshop will exchange the ezb4 too...

@thetechguru I'm in Hurst, Texas "little town" Between Dallas and Fort Worth to be exact. Wonderful offer! Thank you! But a bit of a drive for us both. I have a RV trip planned your way but not till summer I'm afraid.

@thetechguru and Alan It's just hard for me to believe too that it's the EZB considering everything works just as Tutorials / Lessons describe. The EZB connects fine unless the battery's low and the servo's work fine with pre-programed scripts. I don't have any other 12C devices to check those ports yet. However as Alan said "Bad Luck" about the EZB, well bad luck is my middle name so I guess it's possible I'm going to try it on my laptop "Has Older WinXP loaded and see if anything changes. Not sure what to do after that except exchange it. Robotshop is going to think I have lost my mind! eek Report back my findings shortly. Rod

WindowsXP won't work, so that isn't going to help unfortunately.

It could be just a bad connection on the camera port (cold solder or otherwise poor connection). Everything else would work except the camera in that case.

When the V4 and camera first came out I recall someone had a bad cable and the symptom was the same, but he was able to fix the cable himself, but if it is the connector on the board, it would be harder to self correct.

Alan