TCIP4.exe on mobile, part 2

cape

cape

Hero member
Location
Finland
Second attempt, this time not on Android, but on Windows mobile and this is far more complicated than the previous one. I won't go through all the steps, but here is what you basically need:

1. A Windows mobile phone and it needs to be Microsoft Lumia 950 or 950 XL

2. Windows 10 or 11 ISO file. File size about 5Gb.

Download info using UUP dump -> take a look at WOA project link/guide. This takes a lot of time before there is an ISO file and install.wim that is used to deploy the Windows OS on the phone.

3. WP internals, this is used to unlock phone bootloader and to enter mass storage mode. There will some phone specific files that are needed, but they can be downloaded with WP internals. Download will take some time. Files are about 2.8Gb in total. The phone goes on and off several times and to different modes. And at some point it looked like it was failing to complete the task. But I just followed the instructions and got it right in the end.

WP internals download: https://github.com/ReneLergner/WPinternals/releases/tag/2.9.2

4. WOA, this is used to deploy the operating system on the phone. While using WOA, once again some files will be downloaded (automatically). And then windows will be deployed with developer menu (and some drivers will be downloaded)...

WOA download: https://github.com/WOA-Project/WOA-Deployer-Lumia/releases

After this, comes the actual Windows installation, which is being done by the phone itself. Just needed to reboot the phone and wait for the install to complete...

The overall installation takes several hours to complete, so a lot of patience is needed. If someone is planning to give this a try, please do it only if you have a spare Lumia 950 and you realize that there is a serious risk that it may become bricked…

Step by step instructions are available at WOA project homepage: https://woa-project.github.io/LumiaWOA/

There are also videos on Youtube…

So, that done, now I have a mobile with Windows 11 operating system. It turned the phone to some kind of mini PC.

First impression; the operating system itself is a bit slow, but considering the fact that it is running on an old phone, that was expected. Phone is probably running at its limits, it gets a bit hot and drains the battery in few hours and there is very little storage space left. Never the less, it gets the job done.

Tcip4.exe runs just fine and next I’ll have to find a way to install PL2303 driver and then I can finally test connection to ignition unit, which is the main goal. We’ll see how it goes…

edit: the phone actually has a dual boot option. You can choose Windows 11 or Windows 10 Mobile.

Cheers,

Sami
 

Attachments

  • lumia_tcip4.jpg
    lumia_tcip4.jpg
    83.7 KB · Views: 9
  • lumia_win11.jpg
    lumia_win11.jpg
    88.6 KB · Views: 9
Last edited:
Thats some heavy Voodo your messing with Sami, dedication without limits.

....well... MS version of patch it up until the processor peaks out.. have a mini tower with Win11 only for ipad repairs, the cooling system is on high much of the time, the 4 Unbuntu stations and a Linux DAW run much cooler on the same DELL optiplex 9020 -i5 and -i7

Wondering what USB hub is on a phone.... at least with Linux, you get a fighting chance to id USB attached hardware...

Nice work and effort Sami... j

lsusb
Bus 002 Device 006: ID 14cd:168a Super Top Elecom Co., Ltd MR-K013 Multicard Reader
Bus 002 Device 007: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Bus 002 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 004: ID 0e8d:7612 MediaTek Inc. MT7612U 802.11a/b/g/n/ac Wireless Adapter
Bus 002 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 004: ID 30fa:0400 USB OPTICAL MOUSE
Bus 001 Device 003: ID 046d:c336 Logitech, Inc. G213 Prodigy Gaming Keyboard
Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 
Philosophical standpoint, Native application from ignitech actual operational ( system calls ) under Winxx is not disclosed, or is not readily made known. When application software is supplied by any coder, there remains the adherence to conventional calls on the operating system platform. Temptation to subvert that conventional coding on the applicable platform, can be too tempting, let alone the all pervasive "security protection" that is always n-1, ( protection only works for the last known attack, never protects for a new attack, why security will never protect properly ).

Just had a look at what tablets are based on Win11, Surface Pro 9 at some $1500, bargain... leapfrog and hurdles with this project of yours Sami. The win ( no pun intended ) will be well earned there, suppose the best outcome is for you to have superior knowledge about coms and ignitech native application code, you could disassemble the ignitech .exe file....yes the old days, hacking a hackers code... what fun... frontier stuff... never found hacking the Win registry of much worth, save for emergencies sorting a customers workstation or similar, allowing me to get home before dawn.. j
 
Let’s continue.

PL2303 cable connection between Lumia950/win11/tcip4.exe combo and ignition unit didn’t work. PL2303 is a relatively old chipset and the manufacturer doesn’t actively support it anymore. There just aren’t any drivers available for arm64 architecture. Next I tried CH340 cable and at first the result was the same. Then I was able to find a working driver for it (ftdi-arm64). Now the Lumia device recognizes the cable and sets it as a COM port. I have connection from tcip4.exe to ignition unit and I’m able to change ignition settings with a mobile device! I would say mission accomplished!

The next obvious step is to try wireless connection. I have already ordered couple of cheap Bluetooth serial adapters to play with. We'll see how it goes.

Total costs for the project at the moment:
  • Second hand Lumia 950, 20€
  • CH340 cable, 3€
  • + hours to figure it all out
-Sami
 

Attachments

  • device_connected.jpg
    device_connected.jpg
    143.8 KB · Views: 24
Bloody good work, Sami. Once you've got it perfected, sell it to Ignitech ... and maybe you can sus why their advance correction function for each cylinder doesn't work!
 
Agreed, this could be useful to a whole bunch of Ignitec users, and not just us Laverda owners.

Commercialise it Sami !!!! A lot of folk will be grateful for your efforts

Now I go to Ebay and buy all the Lumina950s I can find... :)
 
Commercialize it? Haha, that's a good one. If I track down an old Lumia 950 + other parts needed and do all the installations, I would have to sell it for 200euros to cover work input and get some profit. And in good scenario this would happen maybe once a week. Brilliant, that would make me a millionaire in no time.

As a one time project for personal use, it makes sense.
 
Few know exactly the level of skill and perseverance this type of project takes, you did well Sami. Will look on as the many the few attempt to replicate what you have managed to make work...... in the league of re-installing a unix type platform on the older Galaxy phones, none but the brave. j
 
And the final step, trying wireless connection.

Here’s how it went with Irxon BT578 V3 Bluetooth Serial adapter (see attached picture). It has an internal battery, so it’s quite convenient to use. Pairing with the Lumia device was effortless, and it looked like all was set to go. There was no need for any driver installation. While pairing, there were two options to choose from, BT578_BLE and BT578_SPP. I’m not too familiar with Bluetooth technology, but I think BLE is a fast, low energy option and SPP is a serial port profile. So, I went with SPP. Pairing created two COM-ports. One for incoming and one for outgoing communication. This has something to do with which device is establishing connection, PC (Lumia) or connected remote device. The COM-port settings are otherwise the same as with Serial to USB cable (Bound Rate: 9600bps, Data Bit: 8, Parity: None, Stop Pit: 1, Flow Control: None).

So, pairing was successful, but the connection wasn’t stable. I opened the tcip4.exe and changed its COM-port to correspond adapters COM-port (outgoing). The BT device blinked the connection light, but tcip4.exe was still showing “No connection with PC”. Must be some sort of Windows bug, driver issue or communication protocol related problem. I have no clue. Well, never mind, I’m quite happy with cable connection! If I ever get the BT working, I will let you know.

This concludes the project. Good luck if you’re going to try this.

Cheers,

Sami
 

Attachments

  • Irxon_BT578_V3.jpg
    Irxon_BT578_V3.jpg
    41.5 KB · Views: 4
cape said:
And the final step, trying wireless connection.

Here’s how it went with Irxon BT578 V3 Bluetooth Serial adapter (see attached picture). It has an internal battery, so it’s quite convenient to use. Pairing with the Lumia device was effortless, and it looked like all was set to go. There was no need for any driver installation. While pairing, there were two options to choose from, BT578_BLE and BT578_SPP. I’m not too familiar with Bluetooth technology, but I think BLE is a fast, low energy option and SPP is a serial port profile. So, I went with SPP. Pairing created two COM-ports. One for incoming and one for outgoing communication. This has something to do with which device is establishing connection, PC (Lumia) or connected remote device. The COM-port settings are otherwise the same as with Serial to USB cable (Bound Rate: 9600bps, Data Bit: 8, Parity: None, Stop Pit: 1, Flow Control: None).

So, pairing was successful, but the connection wasn’t stable. I opened the tcip4.exe and changed its COM-port to correspond adapters COM-port (outgoing). The BT device blinked the connection light, but tcip4.exe was still showing “No connection with PC”. Must be some sort of Windows bug, driver issue or communication protocol related problem. I have no clue. Well, never mind, I’m quite happy with cable connection! If I ever get the BT working, I will let you know.

This concludes the project. Good luck if you’re going to try this.

Cheers,

Sami
Click to expand...
Sure...I'll just throw something together on my lunch break :ROFLMAO:
 
...one from the past, serial RS232 comms, may find a slower rate than 9600 would assist, perhaps.. if able 1200baud for initial try out, parity bit is throwback to very basic error detect, though can cause errors in of itself when invoked, i would turn parity bit off, stop bits, another misnomer, 1 or 1 1/2 or 2 stop bits, no serial comms hardware chip ever checks for more than 1 stop bit. DTR RTS hardware handshake also a hurdle at times, can lead to no transmission if either end expects hardware handshake. Xon Xoff ( control C control Q ) causes many issues, due to encoded ASCII format, ie Hex code transmit. A few suggestion Sami, acted upon or no, in your own good time. j.
 
One of the selling points of the new Sydny-produced Ignition system, HAND HELD DINO, is the ability to use your smartphone to control its features and download data to your phone. Great adaption Sami, love to see blokes in sheds still cracking this even today.
 
iis_iis said:
...one from the past, serial RS232 comms, may find a slower rate than 9600 would assist, perhaps.. if able 1200baud for initial try out, parity bit is throwback to very basic error detect, though can cause errors in of itself when invoked, i would turn parity bit off, stop bits, another misnomer, 1 or 1 1/2 or 2 stop bits, no serial comms hardware chip ever checks for more than 1 stop bit. DTR RTS hardware handshake also a hurdle at times, can lead to no transmission if either end expects hardware handshake. Xon Xoff ( control C control Q ) causes many issues, due to encoded ASCII format, ie Hex code transmit. A few suggestion Sami, acted upon or no, in your own good time. j.
Click to expand...

Thanks for the tips “iis_iis”, I may try it later.

I had another try with BT device. First, when I powered the device and had Bluetooth on in Lumia, it didn’t connect. But when I opened tcip4.exe with outgoing Bluetooth serial port, the connection was established, and it stayed on. So that part seems to be OK after all. But when I try to read the ignition settings (or do anything with tcip4.exe), it causes the program to crash. That makes me believe that the problem is the actual tcip4.exe. Perhaps it’s just not developed to work with Bluetooth virtual serial port. I don't know if compability mode would help, haven't tried.

Earlier, maybe two years ago, I had an email conversation with Ignitech software developer. I asked if they had any plans to develop a mobile app for their ignition system. The answer was NO, he found it to be too complicated and risky. After getting my serial cable connection working, I send him a teaser. The basics of my setup, and the positive results I got with it. He never replied…
 
cape said:
Thanks for the tips “iis_iis”, I may try it later.

I had another try with BT device. First, when I powered the device and had Bluetooth on in Lumia, it didn’t connect. But when I opened tcip4.exe with outgoing Bluetooth serial port, the connection was established, and it stayed on. So that part seems to be OK after all. But when I try to read the ignition settings (or do anything with tcip4.exe), it causes the program to crash. That makes me believe that the problem is the actual tcip4.exe. Perhaps it’s just not developed to work with Bluetooth virtual serial port. I don't know if compability mode would help, haven't tried.

Earlier, maybe two years ago, I had an email conversation with Ignitech software developer. I asked if they had any plans to develop a mobile app for their ignition system. The answer was NO, he found it to be too complicated and risky. After getting my serial cable connection working, I send him a teaser. The basics of my setup, and the positive results I got with it. He never replied…
Click to expand...
I think you'll have very little luck getting Ignitech to reply to your email. The word I got from Liam at Fast Bikes gear (NZ) is that they get too many emails from all over the planet and now only communicate with 'dealers' of their product. Liam is liaising with them to try and find out why the advance correction factor (and other things) don't work in my TCIP4. I'm going to video the issue and the settings - but I need my effing bike assembled before I can do that!
 
You must log in or register to reply here.
Back
Top