New EVODROID7 EvoScan Android GPS/Logger/Reflashing CarPC Touchscreen Review
#152
Evolving Member
Slightly irrelevant but relevant. What tablet did you guys end up using for this? Also, is the program going to be available on the Android market for others to use if they already have a serial or what?
#154
Hi all, I've been waiting for something like this for a long time, been on the torque scan forum for Android in whichhe says they will be rreleasing a update soon for MUTII but now I've stumbled over this.
Just need to ask before I even think about putting a order in, will this be usable with my fto? Also in March I will be purchasing a gen1 3000gt as same as before will this be compatible if that's the case I would be buying 2 of these as want to mount them in the double din.
Many thanks of anyone can help me on this
Phil
Just need to ask before I even think about putting a order in, will this be usable with my fto? Also in March I will be purchasing a gen1 3000gt as same as before will this be compatible if that's the case I would be buying 2 of these as want to mount them in the double din.
Many thanks of anyone can help me on this
Phil
#156
But a draw back from the evodriod7 is no bluetooth and from what I've been trying to find no Android release date. I'm undecided, whether to carry out my nexus 7 build and run torque, or await your software release if that is going ahead, or buy the evodroid7 and try to build that into the double din and go without bluetooth which isn't ideal.
I know in the long run your software at least would be the better option but I will admit I don't have the first clue on changing maps etc but can learn.
At least if I went ahead with the nexus 7 I can install the evo scan software if and when it becomes available.
#158
Payment's been processed. Those that pre-ordered should get some bonus for the wait/early payment at least for the interest that's being earned on the amount by the vendor.
#159
Evolved Member
iTrader: (2)
He has released MUTII protocol just awaiting the PIDS in the coming weeks.
But a draw back from the evodriod7 is no bluetooth and from what I've been trying to find no Android release date. I'm undecided, whether to carry out my nexus 7 build and run torque, or await your software release if that is going ahead, or buy the evodroid7 and try to build that into the double din and go without bluetooth which isn't ideal.
I know in the long run your software at least would be the better option but I will admit I don't have the first clue on changing maps etc but can learn.
At least if I went ahead with the nexus 7 I can install the evo scan software if and when it becomes available.
But a draw back from the evodriod7 is no bluetooth and from what I've been trying to find no Android release date. I'm undecided, whether to carry out my nexus 7 build and run torque, or await your software release if that is going ahead, or buy the evodroid7 and try to build that into the double din and go without bluetooth which isn't ideal.
I know in the long run your software at least would be the better option but I will admit I don't have the first clue on changing maps etc but can learn.
At least if I went ahead with the nexus 7 I can install the evo scan software if and when it becomes available.
If that doesn't matter to you and you just want to log MUT requests, then Torque will be fine for you.
What Hamish has done is used the true MUT protocol and the FTDI drivers to log the protocol and it's better speeds. I don't believe this is possible over bluetooth. But, not positive on that. Hamish can comment more.
#160
The torque implemenation, lets you send MUT requests over OBD. So, you can log requests, but it will be slow.
What Hamish has done is used the true MUT protocol and the FTDI drivers to log the protocol and it's better speeds. I don't believe this is possible over bluetooth. But, not positive on that. Hamish can comment more.
What Hamish has done is used the true MUT protocol and the FTDI drivers to log the protocol and it's better speeds. I don't believe this is possible over bluetooth. But, not positive on that. Hamish can comment more.
#161
@slix_88 Sorry for the waiting mate. It will be worth it, the more I work on it, the harder I realize this stuff is to build - test lots - assemble - test lots. The pre-order price is on special. Rest assured I'm still working on it every day after my day job. Just waiting on version two of the new openport 1.3DA and 2.0DA circuit boards for assembly, with a new fantastic 3 Amp inbuilt Android charger.
Here is a photo of a fully assembled new EvoScan OpenPort 1.3DA Android cable.
Lots of EvoDroid7's waiting for some cables to accompany them...
Here is a photo of a fully assembled new EvoScan OpenPort 1.3DA Android cable.
Lots of EvoDroid7's waiting for some cables to accompany them...
#163
Would it make sense for anyone else than me to have a quick connector for the 0-5v channels and not screws? I can of course make an extension cable where I put the quick connector, but still..
Eagerly waiting on the final product
Eagerly waiting on the final product
#165
Evolved Member
iTrader: (2)
Yeah correct you are, OBD is slow and Bluetooth is even dog slower. I still cannot believe other vehicles makes and clubs don't make super fast logging like us here at evom have built. I won't settle for anything less than the fastest I can make these damn things go. just like my engine tuning, haha. faster, faster.
Maybe something to put on your todo list to add to EvoScan...DMA logging.
I've had a carpc for years, but I will definitely pick up one of your cables when available separately. Also, I was toying with the idea of using a Nexus 7 in place of the carpc, so would be interested in your Android app as well when available separately.