- Joined
- Jul 25, 2012
- Messages
- 482
- Reaction score
- 364
Hello David,
What you are suggesting is pretty much what we've just done. With each individual's LCU-1 having its own unique designation, it will not be possible to trigger anyone else's pad box with your single pad controller. That is how its been from the beginning. The only difference is that we've separated Armageddon Mode into a separate controller. A club has no need for a single-pad controller as they already have an LCU-64 or LCU-128.
An individual has no need for an Armageddon Switch, only clubs have that need. So separating the functions into two separate controllers is the best solution.
Wireless units communicating with other wireless units is not the problem. It is already part of our system architecture that only complete and correct commands can be received or responded to. Any command that is not perfect gets auto-dropped by the system and ignored. There's just no way that the wireless units have anything to do with the problem. Wireless units do replace hardwired connections, but that's all that they do. The signals must still be full and correct for a pad box to be able to respond to them.
I think I know what you mean by commands that are unexpected. But there's really no such thing with WFX systems. The single pad controller that was being used to fire an away cell was in Armageddon Mode where it should not have been. But you cannot call its signal to fire all the pads unexpected. In Armageddon mode it was doing exactly what it is supposed to do. The problem was that it should not have been in Armageddon Mode in the first place.
The only way to insure that this does not happen again, is to do what the Wilson F/X team has done. We've removed Armageddon Mode from single pad controllers. Your "solution" for creating "pseudo random numbers" seems to be ungainly and unnecessary. And because it is a false random number, the possibility of it being inadvertently generated leaves the WFX system open to even more incidents. Trying to create random numbered message keys seems to be completely unnecessary. Why muck up a great system with extraneous signal noise? its unnecessary.
I'll stick with our solution of separating Armageddon Mode and Single Pad controller mode into two separate controllers.
Problem solved.
As to there being "not much information on how the system works" on the website? Well if you read thru this whole thread from the beginning, you'll be amazed at how much information is available. I'm not a web-guy. I'm a hardware guy. And my web guy is family and its hard to get him to do any updating. It'll happen eventually. But for now what it there is pretty good,
Let me know if you have any more questions. But you might as well know that I will not be giving our programming away. We've got far too much invested to give it away.
Long ago when we first started doing Wilson F/X my wife said that it has to pay for itself or we can't do it.
Every penny we've made has gone right back into the business in more research and development.
Did you know we now have remote multi-pad bank voltage reading on the controller at the LCO table? You can read it by beeps or by an added text screen? 99% of the troubles folks have with Wilson F/X launch systems are bad batteries at the pads. Now we can "read" 'em and know!
We've now got an LCU-128 controller that handles up to 16 banks of eight pads each.
Our wireless units now operate out to mile line of sight even at Blackrock.
We've got a new pad-box between the original PBU-8 and the PBU-1. Its the PBU-4 and sells for just $275.
We never really thought about creating single pad systems. Our target customers have always been clubs. But suddenly individuals are wanting the same high quality in their own personal launch systems, hardwired and wireless that are available to clubs. So our own growth has caused this problem. Our solution is the best long term solution for the problem.
We've been at this for well over 20 years and we are in it for the long haul. So our solutions have to work for the long haul too.
Well that's enough for now. Let me know if you have any questions. I will try to answer them but I may not get to them for a couple of weeks. I've got to get back to building system components to fill a couple of very big orders.
Brad, the "Rocket Rev.," Wilson
What you are suggesting is pretty much what we've just done. With each individual's LCU-1 having its own unique designation, it will not be possible to trigger anyone else's pad box with your single pad controller. That is how its been from the beginning. The only difference is that we've separated Armageddon Mode into a separate controller. A club has no need for a single-pad controller as they already have an LCU-64 or LCU-128.
An individual has no need for an Armageddon Switch, only clubs have that need. So separating the functions into two separate controllers is the best solution.
Wireless units communicating with other wireless units is not the problem. It is already part of our system architecture that only complete and correct commands can be received or responded to. Any command that is not perfect gets auto-dropped by the system and ignored. There's just no way that the wireless units have anything to do with the problem. Wireless units do replace hardwired connections, but that's all that they do. The signals must still be full and correct for a pad box to be able to respond to them.
I think I know what you mean by commands that are unexpected. But there's really no such thing with WFX systems. The single pad controller that was being used to fire an away cell was in Armageddon Mode where it should not have been. But you cannot call its signal to fire all the pads unexpected. In Armageddon mode it was doing exactly what it is supposed to do. The problem was that it should not have been in Armageddon Mode in the first place.
The only way to insure that this does not happen again, is to do what the Wilson F/X team has done. We've removed Armageddon Mode from single pad controllers. Your "solution" for creating "pseudo random numbers" seems to be ungainly and unnecessary. And because it is a false random number, the possibility of it being inadvertently generated leaves the WFX system open to even more incidents. Trying to create random numbered message keys seems to be completely unnecessary. Why muck up a great system with extraneous signal noise? its unnecessary.
I'll stick with our solution of separating Armageddon Mode and Single Pad controller mode into two separate controllers.
Problem solved.
As to there being "not much information on how the system works" on the website? Well if you read thru this whole thread from the beginning, you'll be amazed at how much information is available. I'm not a web-guy. I'm a hardware guy. And my web guy is family and its hard to get him to do any updating. It'll happen eventually. But for now what it there is pretty good,
Let me know if you have any more questions. But you might as well know that I will not be giving our programming away. We've got far too much invested to give it away.
Long ago when we first started doing Wilson F/X my wife said that it has to pay for itself or we can't do it.
Every penny we've made has gone right back into the business in more research and development.
Did you know we now have remote multi-pad bank voltage reading on the controller at the LCO table? You can read it by beeps or by an added text screen? 99% of the troubles folks have with Wilson F/X launch systems are bad batteries at the pads. Now we can "read" 'em and know!
We've now got an LCU-128 controller that handles up to 16 banks of eight pads each.
Our wireless units now operate out to mile line of sight even at Blackrock.
We've got a new pad-box between the original PBU-8 and the PBU-1. Its the PBU-4 and sells for just $275.
We never really thought about creating single pad systems. Our target customers have always been clubs. But suddenly individuals are wanting the same high quality in their own personal launch systems, hardwired and wireless that are available to clubs. So our own growth has caused this problem. Our solution is the best long term solution for the problem.
We've been at this for well over 20 years and we are in it for the long haul. So our solutions have to work for the long haul too.
Well that's enough for now. Let me know if you have any questions. I will try to answer them but I may not get to them for a couple of weeks. I've got to get back to building system components to fill a couple of very big orders.
Brad, the "Rocket Rev.," Wilson