IP Cam Talk

Welcome to the new IPCT! If you are having an issue logging in, please clear your cookies / cache.

Digital I/O causes BI4 to freeze

eeeeees

Young grasshopper
I would like to hear from anyone using the BI Digitial I/O feature. Most particularly the Sealevel SeaDAC device. My win 10 i7 system with 10 ONVIF generic cams runs perfectly and forever with no issues until "Open Sealevel SeaDAC device" is checked in BI Options. System will then run for a while until it freezes. Might be 10 minutes and it might run for 10 hours but never all night. The win application log reports the following at the time a freeze occurs:
Faulting application name: BlueIris.exe, version: 4.5.0.2, time stamp: 0x5893542c
Faulting module name: SeaMAX.DLL_unloaded, version: 3.4.0.1, time stamp: 0x56bdf4ee
Exception code: 0xc0000005
Fault offset: 0x0000000000002c10
Faulting process id: 0x6ac
Faulting application start time: 0x01d281743c61e4a7
Faulting application path: C:\Program Files\Blue Iris 4\BlueIris.exe
Faulting module path: SeaMAX.DLL
Report Id: cdefb1eb-1be0-4e3f-8f61-535eb08e4b18
Faulting package full name:
Faulting package-relative application ID:

BI seems to lock up whenever it thinks that it loses the connection to the seamax . After a freeze I use The Sealevel test utility MaxSSD to verify that the eI/O 120PoE is available and functioning,it will read sensors and switch relays.
A couple of revisions back Ken added the function to automatically "Re-open the device connection" every XX seconds. This helped a lot but not enough for a reliable system.
I'm at wits end trying to get external sensors to trigger recording and/or alerts. Any success stories out there?
 

fenderman

Staff member
I would like to hear from anyone using the BI Digitial I/O feature. Most particularly the Sealevel SeaDAC device. My win 10 i7 system with 10 ONVIF generic cams runs perfectly and forever with no issues until "Open Sealevel SeaDAC device" is checked in BI Options. System will then run for a while until it freezes. Might be 10 minutes and it might run for 10 hours but never all night. The win application log reports the following at the time a freeze occurs:
Faulting application name: BlueIris.exe, version: 4.5.0.2, time stamp: 0x5893542c
Faulting module name: SeaMAX.DLL_unloaded, version: 3.4.0.1, time stamp: 0x56bdf4ee
Exception code: 0xc0000005
Fault offset: 0x0000000000002c10
Faulting process id: 0x6ac
Faulting application start time: 0x01d281743c61e4a7
Faulting application path: C:\Program Files\Blue Iris 4\BlueIris.exe
Faulting module path: SeaMAX.DLL
Report Id: cdefb1eb-1be0-4e3f-8f61-535eb08e4b18
Faulting package full name:
Faulting package-relative application ID:

BI seems to lock up whenever it thinks that it loses the connection to the seamax . After a freeze I use The Sealevel test utility MaxSSD to verify that the eI/O 120PoE is available and functioning,it will read sensors and switch relays.
A couple of revisions back Ken added the function to automatically "Re-open the device connection" every XX seconds. This helped a lot but not enough for a reliable system.
I'm at wits end trying to get external sensors to trigger recording and/or alerts. Any success stories out there?
This is a bug you should report it to support. I have seen similar crashing when unplugging the sea level device....
 

eeeeees

Young grasshopper
This is a bug you should report it to support. I have seen similar crashing when unplugging the sea level device....
Thanks for the reply FM. I have worked with support on this bug but so far only improvements in stability but no solution. I can't believe that I am the only BI user that has tried to use Digital I/O and am looking to communicate with a few successful users. I believe that the serial port option can be successful but after spending $ on the e120 I would like to use it since the serial port option is poorly defined.
 

fenderman

Staff member
Thanks for the reply FM. I have worked with support on this bug but so far only improvements in stability but no solution. I can't believe that I am the only BI user that has tried to use Digital I/O and am looking to communicate with a few successful users. I believe that the serial port option can be successful but after spending $ on the e120 I would like to use it since the serial port option is poorly defined.
you can also trigger with vera and other zwave controllers...
Does he have access to a sealevel to test? did you provide access to yours?
 

tangent

IPCT Contributor
cabling issues are also possible (may be reason for disconnect) though I think the issue is probably sw.
 
Last edited:

eeeeees

Young grasshopper
you can also trigger with vera and other zwave controllers...
Does he have access to a sealevel to test? did you provide access to yours?
Its not cabling as demonstrated by using the seamax utility to exercise the e120 or just restarting BI and everything will work for a while. Everything is very repeatable except how long BI will stay up after a restart. No, support does not have a e120 to test, I lent him mine for a month to test with. Thats how BI works at all with the e120. My experience over a year or so is that it never worked so I am hoping to hear from a successful user or two that will prove me wrong. Tonight I even powered the e120 with its own private POE bridge to eliminate the possibility that all the camera LEDs coming on at dark was glitching the POE switch. No cigar!
I would switch to another interface if it was better documented. What I need is an ethernet device that accepts contact inputs and has a few relay outputs. There does not appear to be much documentation how to use the Digital I/O.
 

fenderman

Staff member
Its not cabling as demonstrated by using the seamax utility to exercise the e120 or just restarting BI and everything will work for a while. Everything is very repeatable except how long BI will stay up after a restart. No, support does not have a e120 to test, I lent him mine for a month to test with. Thats how BI works at all with the e120. My experience over a year or so is that it never worked so I am hoping to hear from a successful user or two that will prove me wrong. Tonight I even powered the e120 with its own private POE bridge to eliminate the possibility that all the camera LEDs coming on at dark was glitching the POE switch. No cigar!
I would switch to another interface if it was better documented. What I need is an ethernet device that accepts contact inputs and has a few relay outputs. There does not appear to be much documentation how to use the Digital I/O.
FYI, this should be fixed with the latest update...I test it when i get home...4.5.1 - February 13, 2017
 

eeeeees

Young grasshopper
FYI, this should be fixed with the latest update...I test it when i get home...4.5.1 - February 13, 2017
Hello Fenderman

Thank you for the news! I downloaded 4.5.1.0 x64 and indeed it plays nice with the e120 and does not freeze for several hours but in the end BI4 stops responding. The revised BI seems more stable but not perfect. Speaking to your experience, disconnect e120 and BI stops working, I am not sure that that is a serious bug since it just makes BI stability dependent on e120 stability.

upload_2017-2-13_23-3-11.png

One other issue that perhaps you can shed some light on. If tiggering is not enabled on any camera there will be no triggering upload_2017-2-13_23-49-29.png. If DIO is enabled for one camera there will be lots of triggers, maybe every couple minutes. I am pretty sure, not absolutely sure but pretty close, that no contact closures are occuring. What can cause this?

When you unplug the e120 and BI locks At least you know that the trigger system has failed.
I have been communicating with Ken regarding this problem. How did you know that it was "fixed"?
Eric


FYI, this should be fixed with the latest update...I test it when i get home...4.5.1 - February 13, 2017
Hello Fenderman
 

fenderman

Staff member
The reported fix was mention in the release notes..see the link i posted...its a bad bug because power failure of the sealeave or network issues will cause BI to crash..
 

eeeeees

Young grasshopper
Hello Fenderman
Thanks for the pointer to the release notes. I have been wondering how users knew what was changing. My original post in this thread was looking for another user of DIO and sealevel. From my personal experience it never worked right as a trigger mechanism and sealevel disconnect always, for at least a year would cause a BI crash. Searching thru the archives I can only find users recommending the sealevel devices to others, there are no success stories. I wanted/want to communicate with a happy user. No takers from my post. Have you used yours or just experimented with it?
Eric
 

Ishaq Mir

Young grasshopper
Hi Eric

Any update on this problem as I was thinking of buying the sealevel to use with pir but there is no way I'm doing it if it's not reliable. Whole point of pir is for 100% reliable motion detection

Thanks
 

eeeeees

Young grasshopper
Hello Ishaq
I have been working with Support quite a bit and they have been responsive with updates but so far nothing that makes BI/e120 communication reliable for me. I have the e120 working as it should but not for very long periods, say 12 hours max. Then you get either a BI crash or the following SeaDAC could not be opened. The e120 is pingable when this error is reported, so it is there. I not sure whether it is an BI or e120 problem. From my testing it is obvious that the e120 does not like to be "connected" to more than one application at a time. To me this is strange IP behavior. I am thinking of going back to my Arduino solution now that I understand more about communicating with BI.
upload_2017-3-1_22-40-49.png
If you need a recommendation you will have to get it from someone else. I would like to hear from a successful user.
Eric
 

Ishaq Mir

Young grasshopper
Thanks for the reply, really appreciate it. I see another update was released yesterday, have you tried this yet?

Also, I'm now thinking of purchasing the USB version (8112) instead, may be this will not have the issues as it's not Ethernet?
 

Ishaq Mir

Young grasshopper
Also, what email address is it for support? I've emailed support and had no replies, I also included my serial number. it's been a good few days, I would like to ask if the USB would be 100% reliable.

Thanks
 

Ishaq Mir

Young grasshopper
I have called sealevel sales today and they are saying that the USB 8112 version is by far the most popular for blue iris and that they sell a few hundred each year just for use with blue iris. They haven't had any returns.

I'm going to give the USB 8112 a shot with my PIRs.
 

hotwire

Young grasshopper
Hello Ishaq
I have been working with Support quite a bit and they have been responsive with updates but so far nothing that makes BI/e120 communication reliable for me. I have the e120 working as it should but not for very long periods, say 12 hours max. Then you get either a BI crash or the following SeaDAC could not be opened. The e120 is pingable when this error is reported, so it is there. I not sure whether it is an BI or e120 problem. From my testing it is obvious that the e120 does not like to be "connected" to more than one application at a time. To me this is strange IP behavior. I am thinking of going back to my Arduino solution now that I understand more about communicating with BI.
View attachment 15718
If you need a recommendation you will have to get it from someone else. I would like to hear from a successful user.
Eric
Notes for Blue Iris version 4.5.2.4 say that the update includes stability updates for Sealevel Ethernet devices. Has it made any improvement for you?


Sent from my iPhone using Tapatalk
 

eeeeees

Young grasshopper
Notes for Blue Iris version 4.5.2.4 say that the update includes stability updates for Sealevel Ethernet devices. Has it made any improvement for you?


Sent from my iPhone using Tapatalk
Hi Hotwire
After a lot work on the part of support and myself (mostly bitching and refining my description of the problem) everything is working perfectly using the e120 POE. BI now does not crash due to anything that the Sealevel does. This is a good thing. Very helpful in debugging the system is the Sealevel MOD+ app running on my i6 and the SeaMAX utility on a PC. Both allow e120 operation to be verified independent of BI. Unfortunately you cannot have both programs accessing the e120 at the same time. I don't know why this is but it is an inconvenience because you have to shut down one to use the other. I am now moving on to try and get my Arduino Digital I/O going. I really want DIO hardware in two physical locations.
Good Luck Eric
 
Top