|
About Me
|
Written by Wilsosto
|
|
Saturday, 09 August 2008 08:33 |
There is not really much to say about me that you all would be interested in. I am just a regular guy who has had the fortune or misfortune, depends on how you look at it, to own a Range Rover.
When I first took ownership of 1996 P38a, it only had about 78,000 miles. Before then I think the most complex mechnical work I had ever done was to change spark plugs. Since then, things have changed significantly.
I will not bore you with all the petty little and some not so little things that have gone on with the Rover. I will tell you that I have had all the typical Rover problem ranging from major Cooling system leaks to a simple sagging headliner. I have attacked every problem on my rover with my own research abilities and hands on learning. I have personally repaired every failure with my Rover except for two times. Once when my transmission was rebuilt and the second was when the EAS would go into fault mode. The EAS would drive me absolutely nuts when I could not reset the computer.
Each experience has been a tremendous learning opportunity. Luckly for the Range Rover community, when I had a series of EAS faults in Winter of 2006, I simply could not let it go. I was determined to figure the EAS out once and for all. I then began what would be almost a year of research into every single scrap of information I could find on the EAS. I would spend days upon days just searching the internet for anything no matter how insignificant. I bought a spare EAS module off of Ebay and spent almost a month trying different physical layer protocols. One evening, I stumbled upon the correct physical layer voltage and bit patterns. The journey eventually led me to join forces with several people spread across the globe and we all colaborated to finally disect the remaining EAS communications messaging protocol.
After the free windows software for the majority of the EAS operations was complete, I began developing the EAS Buddy Box. The EAS buddy box took about three weeks of nonstop development on my part. I was pulling an 8 hour regular work day and then would come home and work on the EAS Buddy Box for another 8-10 hours before getting some sleep. For the project I had to learn how to program in assembly language and design my own PCB boards for the production numbers I wanted to reach. All of the components in the design had to be carefully examined and finalized for the current production version. Everything was then packaged up and designed to fit the tolerances for the current enclosure and cable specifications. Overall a tremendous amount of work went into this endevor.
What do I do for a living? Well it has nothing to do with automobiles nor does it have anything to do with electrical engineering. I write image analysis algorithms and design academic research studies in the field of prostate cancer. My daily job is performing prostate cancer research in a university setting.
|
|
Last Updated on Wednesday, 30 September 2009 20:17 |
|
Written by Wilsosto
|
|
Saturday, 09 August 2008 16:46 |
|
Participation in the Solihull Society 2008 Land Rover National Rally was an amazing experience. Time and time again, interested Land Rover owners would approach my vendor tent and tell me about their problems with the Discovery II ABS. This prompted me to begin investigating the most common problems with the Discovery II ABS. I found out very quickly that the ABS system was indeed a source of great frustration to just about every Discovery II owner.
The Discovery II vehicles rely heavily on the ABS system to modulate slipping wheels in an off road situation. If an ABS fault condition is triggered, the driver can be stuck without any ABS or TC. A Discovery II without TC effectively destroys any 4x4 traction. Without the TC, the front, center and rear differentials are completely open and nothing will prevent the wheels from spinning. As soon as one wheel leaves the ground, all power will goto that wheel. Usually the TC would apply brakes to that wheel but without the Traction Control System, the Discovery II is rendered almost completely useless off road.
There was clearly a need for some sort of solution. Even the tiniest signal interruption from any of the 4 wheel speed sensors, would result in a ABS fault condition. So I dedicated a good 6 weeks of intense work to a solution. I purchased a used ABS ECU off of Ebay and began to construct signal transcievers that would enable my laptop to communicate. Hundreds of hours were spent researching and just plain old trial and error.
Very quickly I began to do research into the various communications protocols that the Discovery II vehicles employ. Thankfully, the Discovery II series of vehicles followed a very different communications design from that of the older P38a communications subsystems. The Discovery II series of vehicles adhered to a very well documented ISO structured communications framework. This allowed me to very quickly get most of the lower communications layers established and operational.
To make a long story short, the Discovery II ABS system was a much more understandable and much more easily developed communications protocol. This enabled me to quickly develop the ABS Amigo.
|
|
Last Updated on Thursday, 19 November 2009 17:09 |
|
Written by Wilsosto
|
|
Monday, 11 August 2008 06:00 |
The Range Rover Electronic Air Suspension (EAS) is an amazing feature. As we all know however, it can be a very troublesome creature if left unchecked. In the beginning, even I was completely unable and unaware of how to interact with the Range Rover EAS. Over time and primarily due to absolute desperation, I began to study the EAS system avidly. In my opinion, the more information that I could glean about the system, the more money that I could save in the short and long term. My efforts to understand every aspect of the system eventually led to the project of talking to the system and trying desperately to get any kind of communications response.
Over time, communications with the EAS computer were established and slowly but surely we began to build the different layers of the communications protocol. Eventually, a more or less complete understanding of the EAS communications layers were understood. Surprisingly, for something that was so elusive and mysterious, the actual communications protocol is extremely simple and unsophisticated.
Persistence and perseverance were the key to building a complete functional understanding of the system. The knowledge that was gained about the communications protocol was built into a Windows application. After the protocol was built into a windows application, I then decided to build the protocol into a physical microprocessor. To be honest, at the time I knew very little about windows application programming and absolutely nothing about microprocessor coding. The learning process became an obsession. Luckily the outcome was a series of tools and knowledge that I can now pass onto you. It has always been and will continue to be my hope that these tools and knowledge will help keep these wonderful vehicles on the road for decades to come.
|
|
Last Updated on Tuesday, 15 September 2009 21:33 |
|
RSW Solutions Mission Statement |
|
|
|
Greetings, My name is R. Storey Wilson. I have owned several Land Rovers and absolutely love every positive and negative aspect of ownership. Everything from the amazing off road performance to the worrisome oil leaks make me smile.
I have owned several Land Rover vehicles over the years. Everyday I drive a Land Rover to work and every day I do my best to get it home in one piece. I design every tool that I manufacture. And I design every tool because at one time needed the diagnostic functions. If you have a problem with your Land Rover, let me know. Trust me I have been there too and am happy to help in any way that I can.
It is my mission at RSWsolutions.com, to guide the Rover owner through the best possible repair pathway. I accomplish this through providing the most efficient and most affordable Rover Reset tools available to the private owner. My tools will help you the owner, reset and potentially diagnose many of the most common system ailments that afflict most Rovers. Additionally, I do not consider my job done, until I help you the owner, get your vehicle repaired and working properly in the short term and long term. I will provide you with troubleshooting steps and repair steps to attempt on your own or at the least, troubleshooting steps that you can take to a mechanic.
Simply put, I will do our absolute best to get you pointed in the right direction towards fixing your beloved Rover with the least amount of financial and time impact.
|
|
Last Updated on Thursday, 18 April 2013 16:46 |
|
|
|
|
|
Copyright © 2013 . All Rights Reserved.
|
The information provided herewith is on "AS IS" basis without warranties of any kind either
express or implied. RSW Solutions nor any affiliate guarantee the completeness, usefulness or
accuracy of any information provided herewith either related to RSW Solutions LLC or any of
the links that are referenced from this Web site. However, the information provided herewith
is purely intended for your reference and information and does not express, nor intend to provide
any opinion or advice or endorsement of any kind to the services provided by the organizations
referenced in this Web site. Your use of this Web site (www.RSWsolutions.com) is at YOUR RISK.
IN NO EVENT SHALL RSW Solutions LLC, OR ITS affiliates BE LIABLE FOR ANY LOSS OR INJURY OR
DAMAGES, either direct, indirect, punitive, incidental, special incidental, or otherwise,
resulting from or connected to the use of the www.RSWsolutions.com web site. YOU HEREBY WAIVE
ANY AND ALL CLAIMS AGAINST RSW Solutions ARISING OUT OF YOUR USE OF THE SITE OR ANY
OTHER INFORMATION PROVIDED ON THIS SITE (www.RSWsolutions.com).
Disclaimer: Land Rover, Range Rover and Rover are registered trademarks of Land Rover North America, Inc.. This website has no affiliation with Land Rover North America, Inc.
|
|