Hi all,
Got an issue I was hoping one of you wise people might have a solution for.
We've been having issues in one auditorium where the tamper system got triggered every so often. (NEC 900C Unit, perched high up in an inaccessible area inside the auditorium and is not actually in any way being tampered with)
Typically when this would happen (maybe once every other week) i'd just log into the DCC, re-marry it and it would be fine.
Suddenly it got worse and would not reset and ended up in us canceling shows for an entire day.
At that point we called in our local tech guy that services everybody in the area.
He came in and then said he temporarily bypassed all the tamper switches and that it should not happen anymore.
It was fine for a day but then started happening again around once a day.
When I look at the log in the DCC it shows the following repeatedly -
2023/02/22 04:31:47(U)(584) IMB:Marriage NOT Active
2023/02/22 04:31:47(U)(582) IMB:Physical Marriage Tamper
2023/02/22 04:31:47(U)(520) IMB:ICP Communications Status
2023/02/21 12:49:22(U)(177) Tamper Fail(2)
2023/02/21 12:28:48(U)(177) Tamper Fail(2)
2023/02/21 12:14:24(U)(177) Tamper Fail(2)
2023/02/21 11:28:18(U)(177) Tamper Fail(2)
2023/02/21 09:56:05(U)(177) Tamper Fail(2)
2023/02/21 09:44:51(U)(177) Tamper Fail(2)
2023/02/21 09:18:44(U)(177) Tamper Fail(2)
2023/02/21 08:31:11(U)(177) Tamper Fail(2)
2023/02/21 08:25:45(U)(177) Tamper Fail(2)
2023/02/21 08:10:31(U)(177) Tamper Fail(2)
2023/02/21 08:05:45(U)(177) Tamper Fail(2)
2023/02/21 06:51:46(U)(177) Tamper Fail(2)
Interestingly enough the log changed. I took a screen shot to send to tech a few days ago and rather than say -
2023/02/21 08:10:31(U)(177) Tamper Fail(2)
it originally said -
2023/02/21 08:10:31(U)(177) Tamper Fail(2B8738F705)
I feel like this error log is telling exactly what the problem is - but tech guy says it could be any one of around 6 boards and that they'd need to be swapped out one at a time. (which involves a lot of time and trips that I cant afford)
Does this error log tell any of you specifically what the problem is ?
Thanks everybody !!!
Got an issue I was hoping one of you wise people might have a solution for.
We've been having issues in one auditorium where the tamper system got triggered every so often. (NEC 900C Unit, perched high up in an inaccessible area inside the auditorium and is not actually in any way being tampered with)
Typically when this would happen (maybe once every other week) i'd just log into the DCC, re-marry it and it would be fine.
Suddenly it got worse and would not reset and ended up in us canceling shows for an entire day.
At that point we called in our local tech guy that services everybody in the area.
He came in and then said he temporarily bypassed all the tamper switches and that it should not happen anymore.
It was fine for a day but then started happening again around once a day.
When I look at the log in the DCC it shows the following repeatedly -
2023/02/22 04:31:47(U)(584) IMB:Marriage NOT Active
2023/02/22 04:31:47(U)(582) IMB:Physical Marriage Tamper
2023/02/22 04:31:47(U)(520) IMB:ICP Communications Status
2023/02/21 12:49:22(U)(177) Tamper Fail(2)
2023/02/21 12:28:48(U)(177) Tamper Fail(2)
2023/02/21 12:14:24(U)(177) Tamper Fail(2)
2023/02/21 11:28:18(U)(177) Tamper Fail(2)
2023/02/21 09:56:05(U)(177) Tamper Fail(2)
2023/02/21 09:44:51(U)(177) Tamper Fail(2)
2023/02/21 09:18:44(U)(177) Tamper Fail(2)
2023/02/21 08:31:11(U)(177) Tamper Fail(2)
2023/02/21 08:25:45(U)(177) Tamper Fail(2)
2023/02/21 08:10:31(U)(177) Tamper Fail(2)
2023/02/21 08:05:45(U)(177) Tamper Fail(2)
2023/02/21 06:51:46(U)(177) Tamper Fail(2)
Interestingly enough the log changed. I took a screen shot to send to tech a few days ago and rather than say -
2023/02/21 08:10:31(U)(177) Tamper Fail(2)
it originally said -
2023/02/21 08:10:31(U)(177) Tamper Fail(2B8738F705)
I feel like this error log is telling exactly what the problem is - but tech guy says it could be any one of around 6 boards and that they'd need to be swapped out one at a time. (which involves a lot of time and trips that I cant afford)
Does this error log tell any of you specifically what the problem is ?
Thanks everybody !!!
Comment