[As Good As Solved!] Watchguard Firebox Arm/Disarm LED
-
Another firebox resurrected. ;D
With any luck we might be able to get this included with the lcd driver soon. Stuck on some bugs at the moment though. I'll post here when things are closer to working.Steve
-
Another firebox resurrected. ;D
With any luck we might be able to get this included with the lcd driver soon. Stuck on some bugs at the moment though. I'll post here when things are closer to working.Steve
So there are bugs…. ;D Good to know, because my Light will not turn/change color no mater what i do, by script or by manual running the prog, its a no go.
When it did not work, i just ignored it and accepted that it would not work.
But now that you mention that there might be bugs in it i want to give it a go and see if i can get it to work.
So any pointer would be helpful to where to start looking....I am running pfSense-2.0.1-RELEASE-2g-i386-nanobsd.img.gz and the program runs like it should, no errors or feedback when i run it and nothing happens.
So if you think this could be a "bug" let me know and i will give you all the info you need.. ;)
-
The bugs I mentioned are in the LCD driver/package not WGXepc. Since lcdproc includes code for associated leds we hoped to eventually have the leds controllable through the lcd driver.
WGXepc should be working for any firebox however there are some models that are untested.
Which box is not working? What happens when you run the program?Steve
-
-
Hmm, interesting.
The code is absolutely terrible! :D I'm embarrased to release the source. So I could have easily overlooked some input condition that could causer that. However it should either operate correctly or spit out a message showing the correct syntax. Then it tries to recognise which box you have and either sets the led colour or displays a message saying 'you have an unknown box' or something similar.
Anyway the correct syntax is:WGXepc -l greenTry that.
Steve
-
i am pretty sure i did use -l when trying to get it to work but will check my script/manual tonight when done at work..
-
Hi Steve
as you can see from pic attached, that the app does run, gives no error.
And also you can see if i run it without any argument it does show the options, and this shows that the premissions are ok on the app…So you can see the enigma i have ... ::)
Could it be hardware problems?? I could pop in a 1.2.3 card and see if it work there... :)
-
Hmmm. Interesting.
Let me look through the code again…. -
it is a x500
I am working on including the LED support in the LCD driver. Can you start by answering this:
http://forum.pfsense.org/index.php/topic,44034.msg239376.html#msg239376
-
it is a x500
I am working on including the LED support in the LCD driver. Can you start by answering this:
http://forum.pfsense.org/index.php/topic,44034.msg239376.html#msg239376
Not sure what u want an answer too…
Do you want me to run this: lcdproc? if so what do you want me to look for? -
Nope. We need the output of this command:
pciconf -r pci0:31:0 0:256Run it at the console. We need it to develop the code that determines which model you have.
Steve
-
Nope. We need the output of this command:
pciconf -r pci0:31:0 0:256Run it at the console. We need it to develop the code that determines which model you have.
Steve
AHA, here is the result, hope it helps:
[2.0.1-RELEASE][root@Host.name]/root(1): pciconf -r pci0:31:0 0:256
24408086 0280000f 06010005 00800000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00004001 00000010 00000000 00000000
00000000 00000000 00004081 00000010
09060b0c 000000d0 0a058080 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00005475 00000000 00000000 00000000
00000200 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00004004 00000000 00000000
00002002 00001f02 00000004 00000000
c0000010 14050000 00112233 45670291
017c000f 00000000 00000f47 00000200
ffffffff
[2.0.1-RELEASE][root@root@Host.name]/root(2): -
Thanks for that! :)
Interesting looking at that and comparing it with Tix's from his X700, here.
They are almost identical but there is a difference.
Do you have any extra hardware in your box?
Hmm….Steve
-
Thanks for that! :)
Interesting looking at that and comparing it with Tix's from his X700, here.
They are almost identical but there is a difference.
Do you have any extra hardware in your box?
Hmm….Steve
Can not remember that i did see anything special in it when i had it open last time, compared to the first x500 i had that the LED prog did work on.
But i will crack it open again and have a look if needed… -
Aha!
The correct output should be:[2.0.1-RELEASE][root@pfsense.fire.box]/bin(20): WGXepc Found Firebox X-Peak WGXepc Version 0.3 17:2:2011 WGXepc can accept two arguments: -f (fan) will return the current fan speed or if followed by a number in hex, 00-FF, will set it. -l (led) will set the arm/disarm to the second argument: red, green, red_flash, green_flash, off Not all functions are supported by all modelsI suspect that you somehow have an old version of the program. Either that or it's been corrupted or your box isn't outputing some text! (unlikely).
Try downloading it again.Steve
Edit: In fact looking again you can see in the usage text is says 'WGXe' which is the first version of the program I wrote and only worked with the Xe box. You must have renamed it WGXepc without realising.
-
Aha!
The correct output should be:[2.0.1-RELEASE][root@pfsense.fire.box]/bin(20): WGXepc Found Firebox X-Peak WGXepc Version 0.3 17:2:2011 WGXepc can accept two arguments: -f (fan) will return the current fan speed or if followed by a number in hex, 00-FF, will set it. -l (led) will set the arm/disarm to the second argument: red, green, red_flash, green_flash, off Not all functions are supported by all modelsI suspect that you somehow have an old version of the program. Either that or it's been corrupted or your box isn't outputing some text! (unlikely).
Try downloading it again.Steve
Edit: In fact looking again you can see in the usage text is says 'WGXe' which is the first version of the program I wrote and only worked with the Xe box. You must have renamed it WGXepc without realising.
Well done spotting that one, i will get find the newest version and test it and let u know. But not sure how i managed to rename the old version…
-
Perhaps someone else has uploaded a renamed copy. :-\
Steve
-
I took the file that you attached on your reply #59 in this thread and now the output looks alot better.
I am not physical close to it now so can not check bet still output looks promising:[2.0.1-RELEASE][root@host.box]/usr/local/bin(11): ./WGXepc2
Found Firebox X-Core
WGXepc Version 0.3 17:2:2011
WGXepc can accept two arguments:
-f (fan) will return the current fan speed or if followed
by a number in hex, 00-FF, will set it.
-l (led) will set the arm/disarm to the second argument:
red, green, red_flash, green_flash, off
Not all functions are supported by all models
[2.0.1-RELEASE][root@host.box]/usr/local/bin(12): ./WGXepc2 -l green
Found Firebox X-Core
[2.0.1-RELEASE][root@host.box]]/usr/local/bin(13):;D
-
-
I took the file that you attached on your reply #59 in this thread and now the output looks alot better.
I am not physical close to it now so can not check bet still output looks promising:[2.0.1-RELEASE][root@host.box]/usr/local/bin(11): ./WGXepc2
Found Firebox X-Core
WGXepc Version 0.3 17:2:2011
WGXepc can accept two arguments:
-f (fan) will return the current fan speed or if followed
by a number in hex, 00-FF, will set it.
-l (led) will set the arm/disarm to the second argument:
red, green, red_flash, green_flash, off
Not all functions are supported by all models
[2.0.1-RELEASE][root@host.box]/usr/local/bin(12): ./WGXepc2 -l green
Found Firebox X-Core
[2.0.1-RELEASE][root@host.box]]/usr/local/bin(13):;D
This did work… for future reference..
Just my bubu renaming an old version, still do NOT know how that happened, but again thank U Steve for all your help..
