Granted I haven't read the entire thread but does the camera and/or project have to run constantly 24hrs a day? Does anyone care at 3am if the camera isn't running? Ok if you need to run 24hrs a day can you not just write a looping script that checks to see if the camera is active (say once a minute or so)? So if it disconnects you can have the script try and re-esablish the connection... Maybe? Again, as mentioned I may be off base as I haven't read the whole thread....

I use one of these splitters for my hardwired project.

The splitter runs: -ezb usb -camera usb -xbox controller

There has never been an issue with Comm ports

@ Richard Hey dude, long time. Yeah, I'm afraid it has to run 24/7 for 4 to 6 weeks at a time. If this sculpture is in an art show, as it's supposed to be in January, it may be a long drive, as it is for the upcoming show. I'm very interested in the script you mentioned. I'm slowly learning to manipulate EZB interaction using script but I'm not that advanced. But I have been curious if some code could keep the EZB/camera awake. What might a looping script like that look like?

@56 that sounds pretty good. I'll look into it as a backup but yeah, I'm running out of time. The show quickly approaches.

Unfortunately I am away from my computer for a few days. I have just the script you are looking for in one of my projects. You could try looking at my public project called My Roli MkII, but it has a lot of stuff in it to dig through. It is a combination of two things. The init script and another keep alive, but I forget what I called it.

I'll post here after the holiday weekend with the details if no one else does first.

Alan

Im not much of a programmer and new to ezb but this should be easy enough. Try this

REPEATWHILE(true)
  IF (IsConnected(0)==false)
    ControlCommand("Connection", Connect0)
  ELSEIF ($IsCameraActive==false)
    ControlCommand("Camera", CameraStart)
  ENDIF
  sleep(3000)
ENDREPEATWHILE

Put that in a custom ezb script and run it. It will check if your board is connected every 3 seconds, and if its disconnect will attempt to reconnect board0. If the camera isnt started it will attempt to start the camera.

You can autostart the above script by giving it a name (I called it watchdog) and adding

ControlCommand("watchdog", ScriptStart)

to the "connection established cmd", so it will run the first time you connect to the board.

Test it by disconnecting your wifi.

You may need to ensure the laptop doesnt try to connect to a different, known wifi when losing the connection with the ezb AP.

@Mac... This script worked for me in testing (camera only not for the ezb4 itself) ... FYI this script will have to be kept running always as it monitors the camera connection... It will also enable face tracking if need be... Add a script to your project and name it whatever you want... copy and paste my script below into you script...

:top
waitforChange($IsCameraActive)
if($IsCameraActive != 1)
sleep(1000)
ControlCommand("Camera", CameraStart)
sleep(1000)
ControlCommand("Camera", CameraFaceTrackingEnable) #enables face tracking
sleep(1000)
endif
goto(top)

Richard, afaik, if facetracking was enabled it will re-start automatically when the camera is restarted (and if it wasnt enabled, you probably dont want to enable it) Your script also doesnt help if the wifi gets disconnected, which I thought was the OP's main problem.

And ahm..

:D

As always, you fellas offer help without chastising or attitude; you're all awesome....to the max

Okay, to clear a couple things up;

1. I thought originally that the problem was the EZB disconnecting, which it was. But.....
2. The camera disconnects first, followed sometimes by the EZB.
3. The above is when in AP mode. When I changed to clent with a dedicated router, it was a comm error and the EZB would disconnect. No camera error like in AP mode.

I actually found Alan's loop code late last night (when I remembered I could stop being lazy and search for myself) but the scripts you all shared should prove valuable. Also, and I think this is significant, when I connected last night before going to bed, the camera image on the laptop screen had a lot of horizontal blue lines running through it. That lasted for about two minutes and then cleared up. I'd never seen that until now. Add this to the fact that iRobot ran for weeks on end without disconnecting a year ago, before being stored, now I'm leaning towards a hardware problem. Or possible just the camera cable going bad. I've ordered a new EZB and camera but I think it's time for some major disassembly.