From: Eric I. <eri...@gm...> - 2006-06-28 20:26:18
|
Hi all, the Magellan pro's here are up and running with player and looking sharp. Unfortunately I haven't been able to get the sony evid30 cameras working yet. I just tested them using the old Mobility software to make sure the hardware is still working. The configuration for the driver is very simple so I've quickly run out of things to try (the obvious stuff like hardware failure/wrong serial port). Here is what I'm getting: --------------config file------------- driver ( name "sonyevid30" provides ["ptz:0"] port "/dev/ttyS2" fov [3 30] ) --------------player ouput --------- Listening on ports: 6665 accepted client 0 on port 6665, fd 5 PTZ connection initializing (/dev/ttyS2)...SONY: poll timedout ! SonyEVID30::Send():read():: Resource temporarily unavailable Couldn't connect to PTZ device most likely because the camera is not connected or is connected not to /dev/ttyS2 warning : subscription failed for device 8:0 closing connection to client 0 on port 6665 -------------playerprint output -------- [root@grits1 player_work]# playerprint ptz playerc error : requested [1] access, but got [3] access terminate called after throwing an instance of 'PlayerCc::PlayerError' Aborted Any ideas? Thanks! -- Eric Innis Georgia Institute of Technology Electrical and Computer Engineering: GRITS Lab. Aerospace Engineering: Computational Combustion Lab. 404.312.0950 |
From: Brian G. <br...@ge...> - 2006-07-03 23:06:00
|
On Jun 28, 2006, at 1:26 PM, Eric Innis wrote: > Hi all, the Magellan pro's here are up and running with player and > looking sharp. Unfortunately I haven't been able to get the sony > evid30 cameras working yet. I just tested them using the old Mobility > software to make sure the hardware is still working. The > configuration for the driver is very simple so I've quickly run out of > things to try (the obvious stuff like hardware failure/wrong serial > port). Here is what I'm getting: > Listening on ports: 6665 > accepted client 0 on port 6665, fd 5 > PTZ connection initializing (/dev/ttyS2)...SONY: poll timedout ! > SonyEVID30::Send():read():: Resource temporarily unavailable > Couldn't connect to PTZ device most likely because the camera > is not connected or is connected not to /dev/ttyS2 > warning : subscription failed for device 8:0 > closing connection to client 0 on port 6665 That means that the driver's not receiving any data from the camera, which is usually because the camera isn't there. Perchance is your camera's address set to something other than 1? Those cameras can be attached to a bus, with each having a different address. I believe that the sonyevid30 driver will only control one camera, and assumes that its address is 1. brian. |
From: Eric I. <eri...@gm...> - 2006-07-04 07:10:58
|
Yeah, I tried that. Unfortunately changing the camera ID didn't fix it. Right now I'm digging into the driver. The mobility driver works fine, but the player driver never receives any reply from the camera. I can send commands successfully but not receive acks or data. On 7/3/06, Brian Gerkey <br...@ge...> wrote: > > On Jun 28, 2006, at 1:26 PM, Eric Innis wrote: > > > Hi all, the Magellan pro's here are up and running with player and > > looking sharp. Unfortunately I haven't been able to get the sony > > evid30 cameras working yet. I just tested them using the old Mobility > > software to make sure the hardware is still working. The > > configuration for the driver is very simple so I've quickly run out of > > things to try (the obvious stuff like hardware failure/wrong serial > > port). Here is what I'm getting: > > > Listening on ports: 6665 > > accepted client 0 on port 6665, fd 5 > > PTZ connection initializing (/dev/ttyS2)...SONY: poll timedout ! > > SonyEVID30::Send():read():: Resource temporarily unavailable > > Couldn't connect to PTZ device most likely because the camera > > is not connected or is connected not to /dev/ttyS2 > > warning : subscription failed for device 8:0 > > closing connection to client 0 on port 6665 > > That means that the driver's not receiving any data from the camera, > which is usually because the camera isn't there. > > Perchance is your camera's address set to something other than 1? > Those cameras can be attached to a bus, with each having a different > address. I believe that the sonyevid30 driver will only control one > camera, and assumes that its address is 1. > > brian. > > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > -- Eric Innis Georgia Institute of Technology Electrical and Computer Engineering: GRITS Lab. Aerospace Engineering: Computational Combustion Lab. 404.312.0950 |
From: Brian G. <br...@ge...> - 2006-07-04 16:44:17
|
On Jul 4, 2006, at 12:10 AM, Eric Innis wrote: > Yeah, I tried that. Unfortunately changing the camera ID didn't fix > it. Right now I'm digging into the driver. The mobility driver works > fine, but the player driver never receives any reply from the camera. > I can send commands successfully but not receive acks or data. I wonder if your camera is connected via a half-duplex serial cable, allowing only host->camera communication. It's possible to command the Sony PTZ unit without getting any feedback, which may be what Mobility is doing (this is how the PTZs were controlled by Ayllu when connected to the AUX port on P2OS-controlled robots). The Player driver requires full duplex comms. brian. |