I know that there are probably several people out there watching these progress reports for good news. I had originally estimated that the hardware and software would be completed after a period of 45 days, ending sometime in the middle of February. Good news is that I am still working on the project, bad news is that I will certainly not be complete by the middle of February.

I am in discussions with an Enclosure manufacturer. I am placing a special order for the enclosures. This will take a substantial up front cost for me, but should result in a much better product enclosure. The enclosures are partially translucent and will encorporate a USB cable with strain relief.

The hardware board design is almost complete but has been held up on the final enclosure decision. I am making progress every day, but it is a slow road. Please be patient and we will all get throguh this to the end and have an awesome tool for working with the Rovers.



Tremendous progress to report today. I decided to pursue the route of using dedicated IC chips to handle all of the analog multiplexing, signal inversions and voltage shifting. The result was a much more straight forward signal pathway and very very stable circuit design. This is definately the way to proceed. The previous method of designing my own transistor circuits to accomplish this was a waste of time. Now that the primary circuits have been proven, I am ready to proceed to the actual board design in full using smaller form factor chips.





Slow progress and several dead ends over the past few days. I have attempted to accomplish several hardware circuit designs but they are not working as I expected. I am backing up and pursuing a different hardware design. I am going to find off the shelf ICs that will hopefully accomplish the same goal. Voltage shifting, voltage inverters and digital multiplexing will be accomplished through fabricated ICs rather than seperate transistor circuits. This will unfortunately raise the price by a few USD. The upside is that the end product will be of better and more durable quality.



Progress over the past week has been slow but steady. It does not help that everyone in the house has the Flu. Aside from all of that, I have made developments in the hardware design. I am not an electronics engineer, so when a design requirement arises that would call on me to design something from scratch, it takes considerable time. Hand built through hole hardware prototypes should be constructed by this weekend. I am simultaneously developing the SMD circuit board designs for manufacturing. More soon hopefully...




I have made considerable progress with the All Comms project. First and foremost, I have decided upon the hardware platform. The hardware platform has been constructed and is working properly. The hardware platform will enable any windows PC to simply connect the USB device and then connect with the Rover of their choice. The hardware has a USB bridge chip and the ability to, through software, select one of three different physical communications protocol circuits.

I have also made considerable progress on the software development. The software tool is almost complete in establishing communications to all three different vehicles. Once I have established communications, I will then begin the tedious process of programming all of the different vehicle subsystems.

It is still the goal of this project to establish the software platform and make the software platform an open source project. If all goes well, the project will have a momentum oif its own in a few months.

{slimbox images/stories/myimages/allcomms/rover_all_comms_p1.jpg, images/stories/myimages/allcomms/rover_all_comms_p1_small.jpg}


Announcing the development of a new product called the All Comms. The intent of this product is to provide a multi vehicle communications protocol transciever. The device will enable any Windows PC with a USB port, to communicate with the different vehicle subsystems across three different Rover vehicles. This will be accomplished through a piece of software, in which the vehicle owner can send commands to different systems like the HEVAC or the EAS. Aditionally, this will also be possible across three different vehicles.


It is my hope that this will be the last and final piece of hardware that I develop for the Rover community. The hardware will enable very simple Windows software to trigger the time sensitive and complex message framing that must be accomplished for most of the vehicle computer subsystem communications. Initially, the software developed for the system may be a bit rough and could be missing some vehicle subsystem modules. The long term goal, is that this hardware will encourage persons independent of myself to carry the diagnostic software development.



{slimbox images/stories/myimages/allcomms/overall_plan.jpg, images/stories/myimages/allcomms/overall_plan_small.jpg}




Announcing the release of the EAS Activate MKIII. After a month of juggling a new born baby, a full time day job and my daily email, manufacturing and shipping responsibilities with this job, I have finished development on the EAS Activate MKIII. It was easy really Once you are resigned to not having any sleep because of a new born in the house. :)

The EAS Activate MKIII is similar to my previous diagnostic tools. The device will read and clear the EAS Fault codes on the MKIII Range Rover. Once the EAS Faults are cleared, the device can be plugged into the USB port on any windows based PC. When plugged into a USB port, the EAS Activate MKIII turns into a USB flash drive. Contained within this USB flash drive is a text file which contains all the fault codes that were stored on the MKIII EAS computer. Sales of the EAS Activate MKIII will begin in approximately one weeks time. If you would like to pre-order, I can be contacted through email.


{slimbox images/stories/myimages/easactive/eas_activate_v1_usb_5.jpg, images/stories/myimages/easactive/eas_activate_v1_usb_5_small.jpg}


{slimbox images/stories/myimages/easactive/eas_activate_text.jpg, images/stories/myimages/easactive/eas_activate_text_small.jpg}




After a very full weekend of sitting at my computer and occasionally cursing loudly, I have finished the entire EAS communications protocol.  There was however, one casuality in the process. It turns out, that a fully charged battery can not power a laptop for more than a few hours. I completely discharged my battery. So it is now on the charger.

Awesome, I am thrilled. Looks like I may have to fork up the cash for a new battery.


I have completed the process of integrating the MKIII EAS communications protocol into a hand held microprocessor device. The functionality of the new MKIII EAS Activate Tool will be almost identical to the EAS Buddy and the ABS Amigo. The new tool, EAS Activate (Name Pending), will read and clear the stored MKIII EAS Faults.


The incorporation of the MKIII EAS protocol into the portable microprocessor is going slower than expected. As with everything, the process is slow in the beginning and then speeds up significantly towards the end. The primary problem is lack of avaliable used EAS ECUs on Ebay or through other part supplier sources. This means that I must literally set up all of my testing environment and several Laptops all plugged into my MKIII Rover OBDII port. This is much more difficult than just sitting down at a desk and testing. Working at the vehicle is cramped uncomfortable and each night is getting colder working in the garage. I will get there soon enough. I still expect a working prototype by this weekend.


development_1_small development_2_small


Difficulties encoutered revolved around the differences with the input and output buffers between a PC development environment and the specific microprocessor environment.


Happy to announce that the Communications protocol discovery process for the MKII Range Rover EAS disgnostic subsystem is complete. I have a 99% complete understanding of the fault code reporting structure and am now ready to begin incorporation of the communications protocol into a microprocessor driven device.

development_3_small development_4_small

The timeline for release of this new EAS device for the Range Rover MKIII has been moved up. I expect a device to be ready within the month. Any interested parties who wish to perform actual beta testing, please contact me through email. Please, only interested parties who know what the hell they are doing with the EAS. If you have never had an EAS fault DO not bother requesting a beta product.

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 ( 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 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 (

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.