Missing 1394 device on Windows 7 restart

We’re having an issue with our 1394(a) based cameras and Windows 7
that I’m hoping someone can help us with. Basically, if we have a
1394a camera installed and working on a Windows 7 system, and then
perform a system restart – sometimes the camera is not be present (in
Device Manager) when the system comes back up. If we disconnect and
then reconnect the camera, it re-appears.

It happens somewhat sporadically, but we’ve seen it with several
different cameras and several different Windows 7 machines (both 32
bit and 64 bit). When it does happen, performing a ‘scan for new
hardware’ does not find the camera. If I look at the ntblogfile, I
see that the system did not even attempt to load the camera driver,
but all of the 1394 drivers seemingly loaded fine. It’s like the PnP
Manager did not see the device when it enumerated the 1394 bus.

Any ideas?

Thanks.

/Paul

On Jan 27, 4:00*pm, Paul <paul.carr...@pixelink.com> wrote:
> We’re having an issue with our 1394(a) based cameras and Windows 7
> that I’m hoping someone can help us with. *Basically, if we have a
> 1394a camera installed and working on a Windows 7 system, and then
> perform a system restart – sometimes the camera is not be present (in
> Device Manager) when the system comes back up. *If we disconnect and
> then reconnect the camera, it re-appears.
It sounds like the enumeration problem the old XP also had.
It would mean that a simple Busreset on the firewire network would
probably solve.


>
> It happens somewhat sporadically, but we’ve seen it with several
> different cameras and several different Windows 7 machines (both 32
> bit and 64 bit). *When it does happen, performing a ‘scan for new
> hardware’ does not find the camera. *If I look at the ntblogfile, I
> see that the system did not even attempt to load the camera driver,
> but all of the 1394 drivers seemingly loaded fine. *It’s like the PnP
> Manager did not see the device when it enumerated the 1394 bus.
>
> Any ideas?
>
> Thanks.
>
> /Paul

On Jan 28, 5:01*am, Cedric Schmeits <cedric.schme...@boschrexroth.nl>
wrote:
> It sounds like the enumeration problem the old XP also had.
> It would mean that a simple Busreset on the firewire network would
> probably solve.
>

I was wondering the same thing. Did MS add the bus reset to XPs
initialization sequence?

I'm also wondering of other devices are experiencing similiar
behavior.

/Paul

On Jan 31, 3:29*pm, Paul <paul.carr...@pixelink.com> wrote:
> On Jan 28, 5:01*am, Cedric Schmeits <cedric.schme...@boschrexroth.nl>
> wrote:
>
> > It sounds like the enumeration problem the old XP also had.
> > It would mean that a simple Busreset on the firewire network would
> > probably solve.
>
> I was wondering the same thing. *Did MS add the bus reset to XPs
> initialization sequence?
>
> I'm also wondering of other devices are experiencing similiar
> behavior.
>
> /Paul

Here we experience the same sometimes, but a normal situation here we
almost never restart the PC. The problem we do have that sometimes
after a bus reset not all nodes in the network are seen by XP or Win7.
Luckily it happens 1:10.000 or so and an extra busreset always solves
the problem.