EasyManua.ls Logo

Courion iLEARN - Frequently Asked Questions (FAQ)

Default Icon
64 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
46
ver.071217-2.10
iLEARN System Manual
Frequently Asked Questions (FAQ)
Q: I have a momentary pressure close system that, upon pressing and releasing the close
button, activates the close buzzer for a couple of seconds and then stops without closing the
opening. This only happens a few times out of a hundred – most times it works ne. What
conditions can cause this?
A: Once the close latch is activated in the iLEARN, only these things can cause the latch to reset:
iLEARN resetting
Reversing edge or Light Curtain reversal
EITHER hall or car STOP dropping (does NOT depend on HPB)
ILF/ILR dropping
FSH dropping
INS dropping
Valid open command
It’s also possible that EUD dropping or a second ILR/ILF zone activating could cause this latch to
reset but that would result in an EUD latch that would require the door to be closed manually before
power operation could resume. Keep in mind that any of these conditions only needs to be true for
1/10th second.
Q: I’m monitoring an iDRIVE’s Open Position register and see strange operation. It starts
out at 97”, climbs to 103” as the door opens, and then jumps back to 97” with the door still
opening. How is this possible?
A: Your iSENSOR to magnet coupling is poor. When this is the case, this number tends to drift
away from a reasonable range of +/- 18”. In this particular case, the iSENSOR has a tendency to
count more open pulses than close pulses and the number grows over time. Try to improve the
magnetic coupling by cleaning metal shavings off the magnet, aligning the iSENSOR, and shimming
the iSENSOR out to get closer to the magnet.
Q: I’ve just downloaded a different version of software to my iLEARN and now I get the Mi-
crosoft BSoD (Blue Screen of Death) and no activity on the iLEARN’s status LED. How do I
x this?
A: The downloading process has corrupted the bootloader. This is possible when the iDRIVE hex
le is inadvertently specied for the iLEARN hex le in nxLoader.
The only x is to return to the fac
-
tory for reprogramming.