Datatek
Well-Known Member
Quicker and easier to hire a digital data logger or buy a PCB & software for my PC.
Malafax_Dand
Member
Hey guys.
The EAsunlock software does indeed use the Dot.Net framework. There really is no need to port this over to an android or IOS environment. The EAS protocol is extremely simple. It would not take very long for me to write a quick Android app that could communicate with the P38 Range Rover.
The problem is what you would use for the hardware interface. The reality of the situation is that the EAS computer protocol is not actually a RS232 physical protocol. An RS232 voltage protocol does work with the EAS computer but only barely and really looking back it is a wonder the RS232 voltage protocol works at all. It was random luck that I got it to work. The knowledge for the real physical protocol evolved later, is a bit different and is implemented in the EAS Buddy hardware design.
Also, there are absolutely no off the shelf OBDII based devices that have the physical pin outs to communicate with the EAS computer.
Does anyone have a reliable, working and inexpensive Bluetooth RS232 device that we can wire up to a special made EAS Serial cable? I have found it difficult to find all of the above in a bluetooth device.
The EAsunlock software does indeed use the Dot.Net framework. There really is no need to port this over to an android or IOS environment. The EAS protocol is extremely simple. It would not take very long for me to write a quick Android app that could communicate with the P38 Range Rover.
The problem is what you would use for the hardware interface. The reality of the situation is that the EAS computer protocol is not actually a RS232 physical protocol. An RS232 voltage protocol does work with the EAS computer but only barely and really looking back it is a wonder the RS232 voltage protocol works at all. It was random luck that I got it to work. The knowledge for the real physical protocol evolved later, is a bit different and is implemented in the EAS Buddy hardware design.
Also, there are absolutely no off the shelf OBDII based devices that have the physical pin outs to communicate with the EAS computer.
Does anyone have a reliable, working and inexpensive Bluetooth RS232 device that we can wire up to a special made EAS Serial cable? I have found it difficult to find all of the above in a bluetooth device.
Last edited:
O Bife
Active Member
Hi Storey,
Couldn't you fit some sort of Bluetooth adapter to your EAS Buddy? (just an idea)
Malafax_Dand
Member
Well Crap, now you've done it. You just given me a design idea in a slightly different direction that I may need to pursue.
I could take my existing MKIII All Comms device hardware and modify it. I could strip out the USB transciever portion of the board and replace it with a Bluetooth transciever. I have an All Comms design on the shelf that already has hardware design to interface with the EAS computer properly.
I can spread the design costs and manufacturing costs of a new bluetooth based MKIII All comms device across multiple vehicle and customers. This means that I could design a bluetooth device and Android application for multiple vehicles on one hardware platform. I am reluctant to invest all that time and money for the very old P38 Range Rover, but could justify it if bundled with other vehicle functionality.
It will still cost thousands to develop and run through the new manufacturing line, but it hurts less when there are multiple vehicles and multiple systems in one go. I will have to start researching.
I could take my existing MKIII All Comms device hardware and modify it. I could strip out the USB transciever portion of the board and replace it with a Bluetooth transciever. I have an All Comms design on the shelf that already has hardware design to interface with the EAS computer properly.
I can spread the design costs and manufacturing costs of a new bluetooth based MKIII All comms device across multiple vehicle and customers. This means that I could design a bluetooth device and Android application for multiple vehicles on one hardware platform. I am reluctant to invest all that time and money for the very old P38 Range Rover, but could justify it if bundled with other vehicle functionality.
It will still cost thousands to develop and run through the new manufacturing line, but it hurts less when there are multiple vehicles and multiple systems in one go. I will have to start researching.
Last edited:
O Bife
Active Member
Glad to be of help.
BTW, as I mentioned in the e-mail I just sent you, could there be a back door or something like that with their Bluetooth. Never know, you could piggy-back the system. (or is that a bit of wishful thinking?)
Last edited:
Datatek
Well-Known Member
Storey, why can you not use a USB to serial adaptor with Android as we all do with windows for the EAS software? Most Tablet computers have a USB port. It's possible to run net framework software on Android, but the app is expensive.
Malafax_Dand
Member
The answer to the USB to Serial adapter question has to do with basic USB fundamentals. Every USB communications session has a master slave relationship. The PC is usually the master and the device is the slave.
The problem with a tablet is that the tablet is also a slave USB device. So if you plug the tablet into a USB to serial adapter, nothing happens, they are both acting as a USB slave.
Now, some tablets can to what is called USB On The Go. This is a USB slave protocol where the slave can switch roles and become the master for very specific interactions. Like when a tablet could interact with a USB printer.
Anyway, you can see how it is not just a simple matter of plugging in a USB to serial adapter.
The problem with a tablet is that the tablet is also a slave USB device. So if you plug the tablet into a USB to serial adapter, nothing happens, they are both acting as a USB slave.
Now, some tablets can to what is called USB On The Go. This is a USB slave protocol where the slave can switch roles and become the master for very specific interactions. Like when a tablet could interact with a USB printer.
Anyway, you can see how it is not just a simple matter of plugging in a USB to serial adapter.
StuckAgainSteve
Well-Known Member
Android and iOS are also difficult to program when it comes to timing-dependant apps. Unlike desktop operating systems where you're handing processing power over to the application program, under iOS or Android the app is very much the client and cannot force any event - including IO or comms - it can request them - when they happen is a different matter!
Datatek
Well-Known Member
Bearing in mind I know sweet FA other than Android, like Linux, is a Unix derivative, I'm surprised about your comment on I/O since screen refresh is extremely rapid I assumed that I/O would also operate at a speed sufficient to drive slow RS232 type signals. We had no problem with time specific tasks when running Unix years ago. Many tablets also have a dedicated USB output port rather than OTG.
Don't know about Android programming, but I have used OTG adapter and USB-Ethernet dongles with Moto RAZR phones. We needed to do video streaming for a trade show, and WiFi was unusable. HLS Video was rock-solid over Ethernet to the Phone.
The interesting part was the 30Mbps down & 7Mbps up speed test through the dongles, which in my mind says Android can certainly send & receive data fast enough.
The challenge will be the USB-Eth to EAS interface.
Pete
The interesting part was the 30Mbps down & 7Mbps up speed test through the dongles, which in my mind says Android can certainly send & receive data fast enough.
The challenge will be the USB-Eth to EAS interface.
Pete
