ilyad
Well-Known Member
I was wondering if anyone here on the forum has experienced the same issue I just got. Of course it happens on a weekend, when no customer service is available. Walked downstairs and noticed that my Profilux touch screen had an error that read "Attention! No connection to Profilux over PAB!" I figured that it could possibly be where a wire came loose, opened my controller cabinet and noticed that the Profilux is power cycling.
It turn off, then turns back on, starts with the usual profilux 4, a memory test, FW version and then goes to Examine hardware and Slot 1 ADIN 2.0, then turns off and keeps repeating. I am not sure if the examine hardware is a normal step in the reboot, or its a prompt for me to check the hardware and then telling me to check the ADIN module.
I tried to power it off and leave it off, but when I plug it back in, it continues with the same issue. The system seems to be running right now, but thats because when it power cycles off, it doesnt seem to do it long enough for the power bars to turn off. However, I am pretty sure that none of the sensoring or anything is working. I cannot connect to it through myGHL as it keeps cycling off before it has a chance to connect.
Any and all help is very appreciated right now!
EDIT: I suspect I found what was causing it, but have no dang clue why. I previously used a controlled socket to run my supplemental t5 lighting. It was programmed in my Illumination option to turn on a power bar socket. However, the last few months I had the t5s off as I was considering only running my LEDs. Today I decided I do like the supplemental t5 and ended up adding it back in for an hour (I was going to up the amount weekly). Well, thank gosh it was only for an hour, because it just happens to perfectly line up with the hour it was on. As soon as the t5s turned off, the Profilux stopped power cycling.
This sucks, as I had ran t5s through this Profilux for years with no issue, so I am not sure what the heck changed now (although since I last used the t5, I did upgrade to the newest firmware).
For now I removed the t5 from the schedule until I can reach out to GHL, but has anyone else had anything like that happen?
EDIT 2: Was able to confirm that the issue is when my Illumination schedule turns on the t5s. I set up another start/end point for a few minutes and as soon as the t5s came on, the Profilux started to spaz out and powercycle. Once the scheduled time ended, it went back to normal.
I thought possibly the power draw or something was causing the issue, but I had no problem turning on the t5s using the app and it not causing the issue. But for whatever reason, when its automated its problematic.
Another thing I noticed is that when its power cycling, the line that has info about the illumination percentage has glitchy info. (See pics).
So it seems that there is certainly some sort of error going on thats causing it to crash. Will report back once I hear form GHL. Or if anyone has any pointers in the meantime, I wont say no.
It turn off, then turns back on, starts with the usual profilux 4, a memory test, FW version and then goes to Examine hardware and Slot 1 ADIN 2.0, then turns off and keeps repeating. I am not sure if the examine hardware is a normal step in the reboot, or its a prompt for me to check the hardware and then telling me to check the ADIN module.
I tried to power it off and leave it off, but when I plug it back in, it continues with the same issue. The system seems to be running right now, but thats because when it power cycles off, it doesnt seem to do it long enough for the power bars to turn off. However, I am pretty sure that none of the sensoring or anything is working. I cannot connect to it through myGHL as it keeps cycling off before it has a chance to connect.
Any and all help is very appreciated right now!
EDIT: I suspect I found what was causing it, but have no dang clue why. I previously used a controlled socket to run my supplemental t5 lighting. It was programmed in my Illumination option to turn on a power bar socket. However, the last few months I had the t5s off as I was considering only running my LEDs. Today I decided I do like the supplemental t5 and ended up adding it back in for an hour (I was going to up the amount weekly). Well, thank gosh it was only for an hour, because it just happens to perfectly line up with the hour it was on. As soon as the t5s turned off, the Profilux stopped power cycling.
This sucks, as I had ran t5s through this Profilux for years with no issue, so I am not sure what the heck changed now (although since I last used the t5, I did upgrade to the newest firmware).
For now I removed the t5 from the schedule until I can reach out to GHL, but has anyone else had anything like that happen?
EDIT 2: Was able to confirm that the issue is when my Illumination schedule turns on the t5s. I set up another start/end point for a few minutes and as soon as the t5s came on, the Profilux started to spaz out and powercycle. Once the scheduled time ended, it went back to normal.
I thought possibly the power draw or something was causing the issue, but I had no problem turning on the t5s using the app and it not causing the issue. But for whatever reason, when its automated its problematic.
Another thing I noticed is that when its power cycling, the line that has info about the illumination percentage has glitchy info. (See pics).
So it seems that there is certainly some sort of error going on thats causing it to crash. Will report back once I hear form GHL. Or if anyone has any pointers in the meantime, I wont say no.
Last edited:
