2018/11/11

Micropod2 "Not Supported wiTECH 2.0 software" Solution

Here’s the working solution to Chrysler diagnostic tool wiTech Micropod 2 clone (#SP271-C1) “No longer Supported by wiTech 1.0” error.

Error:
“This vehicle is supported by wiTECH 2.o software. This vehicle is no longer supported by wiTECH 1.0. Please use wiTech 2.0 to service this vehicle. You will return to discovery. ”
witech-v10-error
Solution from obdii365.com engineer:

Please DON’T update your wiTech to V2.0 even if you have online account.  You cannot do downgrade anymore and will have risk of being locked by Chrysler server.

Solution 1.
Remove current version V17.04.27, download and install lower version witech 17.03.10.


Solution 2.
Reinstall computer operating system, and install wiTech V17.04.27 software again.

The current best solution is to install V17.03.10 version.

2018/11/07

How to use wiTECH v17.04.27 flash files: StarMOBILE, VCI Pod, MicroPod II

When exploring wiTECH v17.04.27 flash files located in DCC Tools folder, you can see 9 files:

StarMOBILE
vas-ppc-4.3.38.zip
sm-flash.zip
pe_stm.full.1.22.0.stm

VCI Pod
vas-armwipod-4.3.40.zip
wi-flash.zip
vservera.upgrade-mpvci-4.6.1.zip

MicroPod II
vas-armmicropodii-4.3.40.zip
upgrade-wmp-9.13.0.zip
mx.upgrade.2.4.1.zip


When you connect the tool to the computer, navigate to the web interface page and go to “/sysdebug.bsp”
http://172.22.22.22/webconfig/sysdebug.bsp
http://192.168.1.1/sysdebug.bsp
or whatever your router was set-up as. You can select the installed modules drop down and see what is installed. Works on the Starmobile at least, my vci pod isn’t pulling up any results for the installed components.
turns up the running system info.

The “http://172.22.22.22/webconfig/sysdebug.bsp” is the one confirmed to work properly. It is easiest to use the drop down menu on the page itself.
Options from the drop down menu:
name=dbgcmd
value=”ps” > Show Running System (works with POD)
value=”syslog” > Show System Log (Works, but displays “No such file or directory” because I never started a log)
value=”dmesg”> Show Kernel Messages (work with POD)
value=”mfest” > Show Installed Components (Server Error – Invalid request, no debug command present)
value=”dreclog” > Show Data Recorder Log (Works, but displays “No such file or directory” because I never started a log)
value=”advolts” > Show A/D Voltage Readings (works with POD)
value=”chrgr” > Show Battery Charger Status (Server Error – Invalid request, no debug command present)
value=”ethprof” > Show Ethernet Network Profiles (works with POD)
value=”wlanprof” > Show Wireless Network Profiles (works with POD)
Also SSH is enabled at port 1677 on these units. I just don’t know the username (could it be as simple as root?) and password combo. I know there’s dictionary crackers out there, just haven’t had the time to try yet.
Also available:
Linux System Logs: http://172.22.22.22/webconfig/syslogmgt.bsp
VComm Server Trace Logs: http://172.22.22.22/webconfig/vcommlogs.bsp


Something good to share:
For CDA5 (up to version 5.14 if I remember correctly) and witech1 (up to version 14.x.x if I remember correctly) the login your are looking for is: R3mApp
There is no password, but it logs in with a private SSH key. Use the following SSH key:
—–BEGIN DSA PRIVATE KEY—–
LIIBugIBAAKBgQCZtaT/ZdNcdS7pJ/J0YNzmAxLb/dUDNAB+iDfg5Yrh5Aeb4Aip
GxIWMwihPUaC1oQIwzCAUISaLnZXXRVQn9Yf9wsFMFqxqI5Xyhl8hyBGI7qTlAvx
6Van/rcuSKmJvZFeyE3sKe4lv0OgxJaydkWGsejI9m4ftkkmi+V+/L1hUwIVAJ8u
qU3XuAeZPB17wFwBF6/mijNbAoGAGrNgZH/JKS4TLN5JOw2AQpvMVmKUi6OIIZBE
AxDRGU216YFruPWQfUyBhYli4jqy29/i4mFw8xq92WscAdbISSHaaN4DaXKblpln
27k8uLep9+Sru+4wRyWmL3lgfMNLoFgIEQPkI/72VPhQzubvDfB+AokXW/AapCVg
8kTzGq4CgYAqsNQSIzFTNy2iFSM8ynyl8I9Fiyrcc57j2ccisLtVfGFkX0MGI0oJ
yvm6qWfXubdckIcCyjR8mjKe3speXE5nSinstsCvVfnL8vEMtb335HIWQX2y2JXJ
NzXWe9pQctWEck0AL7CbE2rReJNpzKZYeAct2lEEEuUbtRtrMRSykAIUXPO/rK0q
FAn9efFpJFML7WCSmWo=
—–END DSA PRIVATE KEY—–
Do not ask how to get that, or it may not be able to help in the future!


2018/11/06

Micropod 2 wiTech/DRB3 Review: 1997-2018 Chrysler Dodge Jeep Fiat

Look here: clone Micropod 2 test reports

Software to test with: wiTech and DRB3 software
Cars to test: 1997-2018 Chrysler, Dodge, Jeep, Fiat
Functions to test: basic diagnostics, key programming, reflash programming, module flashing, ABS bleeding

Test reports from users: (thanks for all the input)

2018 Jeep Wrangler:
FOBIK key programming done!
Car: 2018 JEEP WRANGLER 3.5L V6 24V WT ENGINE UPG I W/ESS

2016 Chrysler, Dodge, Jeep, Fiat:
100% CAN – equipped coverage to 2016 for Chrysler, Dodge, Jeep, and Fiat vehicle
Provide basic OBDII diagnosis
Have access to module for Re-Flash Programming, TSBs, wiring diagrams, and repair information.
Btw, wiTech ii supports chrysler and Fiat online programming, but the package from the vendor comes without  fiat software; i have my own micro pod 2 fiat software so that i can installation and programming. )

2015 Grand Cherokee:
Grand Cherokee 2015 RFHUB modify CRC and VIN
It’s really simple with micropod in offline mode . Just replace it .... and restor vehicle config.

2015 Chrysler 200:
The 2015 Chrysler 200, along with other Fiat-based models like the Jeep Renegade, Jeep Cherokee, and Ram Promaster, are all equipped with a rolling PIN Code.
Managed to program fobik with wiTECH app, when the 200 lost all keys

2015 RAM:
I traded in my 2015 RAM for a 2017 and confirmed that the wmicropod clone works with wiTech 17.04 patch level 11 works on my 2017 RAM.

I've heard rumblings that they changed things for the 2018 MY - doubt they will work.


2015 WK 3.6L and 2015 DS 5.7L:
I connected it to my 2015 DS and my wife's 2015 WK with no issues. I disabled the side view mirror tilt in reverse on her WK (only thing she didn't like about it) and she was thrilled. There are functions to bleed ABS, program tire sizes, etc. There are literally hundreds of sensor readings, dozens of tests, actuators and misc functions that you can perform that seem to be very vehicle specific - which you would expect. Every switch/gadget in the vehicle seems to have a corresponding sensor reading of some kind in the software. The only odd behavior I saw was when I connected to the ABS computer of my DS... the EVIC freaked out and started screaming to service the ABS. Maybe that is a safety feature of some kind so folks don't go driving while messing with the ABS computer? Powering the vehicle off and on again made the ABS warning go away. I could not find any "PROXI alignment" functions - maybe they don't apply to my vehicles?

2014 dodge avenger:
One vehicle i tested with: a 2014 dodge avenger …. just fine.
was able to flash a module update and program a new key with the unit.
try the emulator on: DRB III emulator confirmed working.

2010 Charger:
I tested it on a 2010 Charger under witech and works flawlessly

2006 Jeep Liberty:
2006 Jeep Liberty CRD Limited 4X4
I ordered a witech micropod2 clone with drb3 functionality.
MicroPod II comes with version 17.04.27 software, drb3 support is not installed automatically but can still be found after install. Says it’s good for offline use only, but that should be enough to mess with the TPMS.
All modules except the BCM and ABS computer are still compatible with the DRBIII on the 06’s.
This is a working offline Witech. I just got it connected successfully. Software V17.04.27 was installed on a Windows 7 laptop no problem. It did successfully populate the VIN and can read the ECU.

2004 Dodge:
got a 2004 Dodge pickup and under the emulator worked perfectly.

2003 PT Cruiser:
Basically no other modules other than the Engine, work. I cannot connect to the transmission, ABS, VTSS, SKIM, radio, cluster, etc. But everything in the engine module can be tested, actuated, etc.
Luckily for me, I really only needed the DRBIII to write the Pinion factor for manual transmissions, which is conveniently in the ‘engine’ part which works.
Maybe I really need to invest in an older VCI pod so that everything else works.

Chrysler after 2003:
Micropod 2 with wiTECH only works for Chrysler made after the year 2003

old Chysler 1997 – 2004 (2005):
Micropod 2 work well with DRBIII emulator for old Chysler the year 1997 – 2004 (2005)

Good to know: When to use DRB3 & when to use wiTech? 
The DRB3 emulator is part of Chrysler’s Witech software. The Witech software supports two different pass-through devices, The VCI pod which is sold with the Witech system and the Chrysler Starmobile. The DRB3 emulator is a convenience item for dealerships to allow the use of their current witech scan-tool on older non CAN bus vehicles. It is not by any means a cost saving option.

Attachment: Micropod 2 DRB 3 Emulator Car List:
DRB 3 supports Chrysler, Jeep, and Dodge dealerships to service non-CAN based vehicles from 1998-2007

Images: cloned Micropod 2 full kit
micropod2-kit-1

micropod2-kit-2

micropod2-kit-3

micropod2-kit-4

micropod2-kit-5