SKU: 76940417559

TMPro2 - Motorcycle full package

Sale price$6479.55 Regular price$7199.50
Save 10%

Shipping Estimate
USA
  • USA
  • CAN

Ships within 48 hours · Estimated delivery Jul 15 - Jul 20

Promo Codes Available:

For Your Every Summer RSVP, with Code: SUMMER15

Description

TMPro2 - Motorcycle full packageMotorcycle full package contains all software modules for key making in motorcycles and scooters. This package contains: Software module 25 Seat, Peugeot, Piaggio bikes immobox Marelli Memory device is Motorola MCU MC68HC05E6 SO28 package. Expected file size is 160 bytes. Use T5 transponder. Written transponder is ready programmed to start the vehicle. Click here to see opened Piaggio Peugeot bikes immobox. Vehicles equipped with this unit: Seat:

Motorcycle full package - contains all software modules for key making in motorcycles and scooters. 

This package contains:

  • Software module 25 – Seat, Peugeot, Piaggio bikes immobox Marelli

Memory device is Motorola MCU MC68HC05E6 SO28 package.
Expected file size is 160 bytes.
Use T5 transponder.
Written transponder is ready programmed to start the vehicle.
Click here to see opened Piaggio/Peugeot bikes immobox.
Vehicles equipped with this unit:
Seat: Marbella
Fiat: Fiorino
Peugeot: Alise, Eliseo, Speedfight
Piaggio: Beverly, Liberty, Vespa, X8
Gilera: GP800

  • Software module 33 – Peugeot bike engine ECU Marelli

Memory device is Motorola MCU MC68HC05B16 QFP64 package.
Expected file size is 256 bytes.
Use T5 transponder.
Written transponder is ready programmed to start bike.
Click here to see opened Peugeot bike engine ECU Marelli.
Vehicles equipped with this unit:
Peugeot: Alise, Eliseo, Speedfight
Piaggio: Beverly, Liberty, Vespa, X8

  • Software module 58 – Ducati bikes dashboard Marelli 

Memory device is serial eeprom 24c02 or 24c16 SMD8 package.
Expected file size is 256 or 2048 bytes.
Use T5 transponder.
Written transponder is ready programmed to start the vehicle.
Vehicles equipped with this unit:
Ducati: 600, 620, 749, 800, 900, 999, 1000

  • Software module 66 – Yamaha bikes immobox Moric

Memory device is serial eeprom Seiko S29190 SMD8 package.
Eeprom can be located in 2 different position. Click here and here to see where to dig for to reach eeprom.
Expected file size is 128 bytes.
Use JMA TPX2 – Errebi TX2 or CN2/CN5 or YS-01 transponder.
Written transponder is ready programmed to start bike.
Note: latest Yamaha immobox Moric DO NOT HAVE serial eeprom, so please check your immobox before purchasing this software. If there is no serial eeprom, but 16 pin chip TMS3705 you need software module 108.
Vehicles equipped with this unit:
Yamaha: BT1100, FJR, FZR, FZ1, FZ6, FZS, XT, XTR, XTX, XVX, YZF
MBK: Skycruiser 125

  • Software module 68 – Kawasaki bikes engine ECU Denso, Mitsubishi

Memory device is serial eeprom 93c66/93c86/24c02/24c04/24c64 8 pin SMD package.
Expected file size is 256/512/2048/8192 bytes.
Use JMA TPX2 – Errebi TX2 or CN2/CN5 or YS-01 transponder.
Written transponder is ready programmed to start bike.
Click here to see opened Kawasaki bikes engine ECU Denso
Vehicles equipped with this unit:
Kawasaki: ZX-6R, ZX-10R, ZX-11R, ZX-12R, ZX-14, ZX-1000, Z-750S, Ninja, Z1000, Z800

  • Software module 90 – Yamaha scooter ECU Mitsuba

Memory device is serial eeprom 24c04 SMD8 package.
Expected file size is 512 bytes.
Use T5 transponder.
Written transponder is ready programmed to start car.
Vehicles equipped with this unit:
Yamaha:X-MAX 125

  • Software module 96 – Honda bikes ECU Keihin, OKI

Memory device is serial eeprom 93c46,93c56,93c66,93c86 SMD8 package or Motorola MCU MPC5602.
For MPC5602 must read and write DATA FLASH area of MPC5602,you can use UPA-USB-S or XPROG-box, download connection diagram.
Because in UPA-USB-S MPC5602 is not listed,you can choose any of MPC560x devices.
For serial eeproms expected file size is 128,256,512 or 2048 bytes.
For MPC5602 expected file size is 65536 bytes.
Use PCF7936 or Silca T14 – JMA TP12 transponder.
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
Honda: CBR 600F, CBR 600RR, CBR 900, CBR 1000, CBR 1100F, Gold 2800, NT650V, SH300, Shadow 750, Silver Wind, Varadero, VT750, VTX1800, X11, Hornet, CB400

  • Software module 98 – Aprilia, Moto Guzzi bikes dashboard Digitek

Memory device is serial eeprom 24c01 or 24c16, both SMD8 package.
Expected file size is 128 or 2048 bytes.
Use T5 transponder.
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
Aprilia: SR, RSV, Scarabeo, Atlantic 500
Moto Guzzi:Bellagio, Griso, Norge, Stelvio

  • Software module 101 – Ducati bikes dashboard Digitek

Memory device is serial eeprom 24c16 SMD8 package.
Expected file size is 2048 bytes.
Use T5 transponder.
Written transponder is ready programmed to start the bike.
Vehicles equipped with this unit:
Ducati: 848, 948, 1049, 1098, 1198

  • Software module 108 – Yamaha bikes immobox Moric type 2

This is new variant of Yamaha immobox, where there is no serial eeprom S29190.
On place, where you must find serial eeprom S29190, you find 16-pin chip TMS3705.
Keys ARE NOT in this chip TMS3705!
Memory device is MORIC MCU 30 pins SSOP package.
MORIC MCU in this immobox IS NOT POSSIBLE TO READ!
Programming of MORIC MCU is thru TMPro, download connection diagrams and instructions
Use Yamaha key or Texas Crypto – Silca 4D-60 – JMA TP06/TP19 transponder.
Written transponder is ready programmed to start bike.
Also you can set immobox to virgin state.
IMPORTANT NOTE:you can program ONE MASTER key and ONE SLAVE key.If you want more slave keys, program a slave key and clone it with software 65.For cloning Yamaha keys with software 65 JMA TPX cloner is not needed.
IMPORTANT NOTE:If you want to program MASTER key, you also MUST MAKE ECU VIRGIN, because programming of MASTER key will delete synchronisation IMMO-ECU.
Vehicles equipped with this unit:
Yamaha: R1, T-MAX, R6, BT1100, FJR, FZR, FZ1, FZ6, FZS, XT, XJR, XTR, XTX, XVX

  • Software module 109 – BMW bikes engine ECU Bosch

BMW bikes engine ECU are 2 types – BMSK and BMSX:
For BMSKP ECU – keys are stored in ECU.
Memory device is flash chip ST M58BW0160 – 80 pin PQFP package.
Expected file size is 2097152 bytes.
Reading is thru BDM100 interface or with flash programmer.
For BMSX ECU – to see where keys are stored you must check what is on ignition barrel.
If there is IMMOBOX UNIT – keys are stored in this unit.To make key you need software 191.
If there is KEY READER UNIT – keys are stored in ECU.
Memory device is TRICORE MCU eeprom area.
Expected file size is 65536 bytes.
Use PCF7936 or Silca T14 – JMA TP12 transponder.
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
BMW: F800, R1200GS, K1600GT

  • Software module 128 – Gilera, Piaggio bikes engine ECU EFI

Memory device can be ST72334 QFP64 package or serial eeprom 25c080 SMD8 package.To see where keys are stored, check eeprom.If eeprom is 25c040, keys are in ST72334.If eeprom is 25c080, keys are in eeprom.
Reading of ST72334 MCU is thru TMPro interface, download connection diagram.
Expected file size for ST72334 is 256 bytes, for 95c080 is 1024 bytes.
Use T5 transponder.
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
Gilera: Nexus, Runner
Piaggio: Beverly, Vespa

  • Software module 129 – KTM bikes immobox ZADI

Memory device is serial eeprom 24c04 SSOP8 package.
Expected file size is 512 bytes.
Use JMA TPX2 or CN2/CN5 or YS-01 transponder.
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
KTM: 690, 990, 1190

  • Software module 131 – Gilera, Piaggio bikes engine ECU Marelli

Memory device is ST10F269-T3 – 144 pins TQFP package.
You must open throttle body for to reach and read memory device.
Reading of ST10F269-T3 is thru TMPro interface, download connection diagram.
Expected file size is 256/262144/327680 bytes.
Use T5 transponder.
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
Piaggio: Beverly, Vespa, MP3
Gilera: Fuoco

  • Software module 168 – Peugeot JetForce bike dashboard Price:100 Euro

Memory device is serial eeprom 95c020 SMD8 package.
Expected file size is 256 bytes.
Use T5 transponder.
Written transponder is ready programmed to start the bike.
Vehicles equipped with this unit:
Peugeot:JetForce

  • Software module 171 – MV Agusta bikes dashboard

Memory device is PIC16F690 SSOP20 package.
You can read PIC16F690 with TMPro, download connection diagram
Use JMA TPX2 – Errebi TX2 or CN2/CN5 or YS-01 transponder.
Written transponder is ready programmed to start the bike.
Vehicles equipped with this unit:
MV Agusta:Brutale

  • Software module 177 – Ducati bikes with dashboard MAE Electronics

Memory device is PIC18F6585 QFP64 package.
You can read PIC18F6585 with TMPro, download connection diagram.
It is just necessary to cut a small hole for to access programming points, no need to open dash completely.
Use T5 transponder.
Written transponder is ready programmed to start the bike.
Vehicles equipped with this unit:
Ducati:Hypermotard, Streetfighter

  • Software module 178 – Ducati bikes handsfree ZADI

Memory device is serial eeprom 24c04, download connection diagram.
Expected file size is 512 bytes
Use Texas Crypto transponder or original Ducati key.
Written transponder is ready programmed to start bike.
If you program original handsfree key, handsfree will also work.
Vehicles equipped with this unit:
Ducati:Diavel, Multistrada

  • Software module 182 – Ducati Panigale bike immobox ZADI

Memory device is Motorola 9S12P128.
You can read Motorola 9S12P128 using TMPro, download connection diagram.
Expected file size is 4096 bytes.
Use Texas Crypto 4D-60 or 6D-60 transponder or original Ducati key.
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
Ducati:Panigale 899, 1099, 1199

  • Software module 183 – KTM bikes immobox ZADI type 2

Memory device is Motorola 9S12P128.
You can read Motorola 9S12P128 with TMPro, download connection diagram.
Expected file size is 4096 bytes.
Use JMA TPX2 – Errebi TX2 or CN2/CN5 or YS-01 transponder.
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
KTM:Duke, 660, 990, 1190

  • Software module 186 – BMW bikes C600, C650 Husqvarna Nuda dashboard

Memory device is serial eeprom 25c160 SMD8 package.
Exected file size is 2048 bytes.
Use TMS37145 80-bit transponder, for example Ford 80-bit
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
BMW:C600, C650
Husqvarna:Nuda, Terra

  • Software module 189 – Ducati 2013 Hypermotard bike dashboard MAE

Memory device is serial eeprom 24c02 SMD5 package.
Expected file size is 256 bytes.
Use TMS37145 80-bit transponder, for example Ford 80-bit
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
Ducati: Hypermotard 2013

  • Software module 191 – BMW bikes 2012 immobox EWS

Memory device is Motorola 9S12G128.
You can read Motorola 9S12G128 with TMPro, download connection diagram.
If Motorola is locked, TMPro will unlock it automatically before to read eeprom area.
Expected file size is 4096 bytes.
Also you can synchronise engine ECU and immobox if they are not matched pair.
Use TMS37145 80-bit transponder, for example Ford 80-bit
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
BMW motorbike: R1200GS, K1300, F800

  • Software module 192 – Ducati 821 bike dashboard MTA

Memoy device is serial eeprom 24c16 SMD8 package.
Expected file size is 2048 bytes.
Use JMA TPX2 – Errebi TX2 or CN2/CN5 or YS-01 transponder.
Software shows PIN code.
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
Ducati: Monster 821

  • Software module 193 – Ducati 1200 bike dashboard MTA

Memoy device is serial eeprom 24c512 SMD8 package.
Expected file size is 65536 bytes.
Use TMS37145 80-bit transponder, for example Ford 80-bit
Software shows PIN code.
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
Ducati: Monster 1200

  • Software module 196 – Kawasaki GTR1400 bike ignition switch Asahi-Denso

Memory device is serial eeprom 93c56 SMD8 package.
Expected file size is 256 bytes.
Use JMA TPX2 – Errebi TX2 or CN2/CN5 or YS-01 transponder.
Written transponder is ready programmed to start bike.
IMPORTANT:This software can programs ONLY SIMPLE TRANSPONDER. Transponder must be placed on ignition switch then bike can start. Original handsfree key can be programmed only by Kawasaki diagnostic tool.
Vehicles equipped with this unit:
Kawasaki: GTR 1400

  • Software module 197 – Ducati Scrambler bike dashboard

Memoy device is serial eeprom 24c16 SMD8 package.
Expected file size is 2048 bytes.
Use TMS37145 80-bit transponder or original Ducati key.
Software also shows PIN code.
Written transponder is ready programmed to start bike.
Vehicles equipped with this unit:
Ducati: Scrambler

  • Software module 198 – BMW bike handsfree key unit HUF

Memory device is Motorola 9S12XS256.
You can read Motorola 9S12XS256 with TMPro, download connection diagram.
Expected file size is 8192 bytes.
If Motorola is LOCKED, software will unlock it automatically before to read eeprom area.
Also you can synchronise engine ECU and handsfree key unit if they are not matched pair.
Use Texas Crypto 128-bit transponder, for example Toyota H transponder.
Written transponder is ready programmed to start bike.
IMPORTANT NOTE:you must place key or transponder close to antenna under seat for to start bike. Software CANNOT program handsfree function of original used key.
Vehicles equipped with this unit:
BMW: R1200GS

Electronic delivery only!

Shipping Notes
  • Free Standard Shipping on $100+ Orders to the USA.
  • Except Preorder products are shipped in 48 hours.
  • Delivery to the USA:
  1. Standard Shipping : 3-10 business days
  • If time is of the essence, please consider selecting expedited delivery for faster service.
Exchange/Return Notes
  • We offer a 30-day return/exchange service after receiving.
  • Final sale items are not eligible for returns or exchanges.
  • To process your return/exchange, please contact us at [email protected]
  • Please click here for more details>>> Return & Exchange Policy
SKU: 76940417559

Discover Niche Categories That Outsell

Top-Converting Item to Boost Your Average Order

4.4 ★★★★★
Based on 542 reviews
Sort
Highest Rating
Newest First
Oldest First
Product Reviews
S
Verified Purchase
Shirley G.
Charlottesville, US
★★★★★ 4
Heavy
Color: Brushed Nickel
Very nice , l liked it cause it’s heavy, and doesn’t fall over when you pull a sheet off.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on September 9, 2025
A
Verified Purchase
Amazon Customer
Grantham, US
★★★★★ 5
Perfect bronze holder
Color: Oil Rubbed Bronze
Great paper towel holder that matches all my other bronze kitchen items.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on January 26, 2026
J
Verified Purchase
Bozeman, US
★★★★★ 5
Looks nice, good construction and good value
Color: Warm Gold
Looks nice, good construction and good value. Stays in place when tearing off sections of paper towels and looks more expensive than it was.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on December 5, 2025
M
Verified Purchase
MommaWolf
Port Orchard, US
★★★★★ 5
Great product!
Color: Oil Rubbed Bronze
Beautiful and easy to assemble and use, good weight to it so doesn’t get knocked over. I have three of these and love them!
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on September 19, 2025
B
Verified Purchase
B. Marold
Lexington, US
★★★★★ 5
Great Guide for Specialized Bible Study or Pastoral Use.
Format: Hardcover
`Commentary on the New Testament Use of the Old Testament', edited by G. K. Beale and D. A. Carson supports the idea that given any approach to the examination of the New Testament you may think of, someone has written a book about it. And a superb book it is, if you have need for an examination of this subject from almost every angle. I say almost, because there is actually one thing I would like to have seen in this book, and it is not there. More on this anon. For the lay reader, be aware that this is a scholarly book, with all the Greek, Hebrew, Aramaic, and (I suspect) even Coptic terms used freely, just when I've gotten in the habit of tracking down Greek, I have to deal with two even more difficult languages. I mention that primarily for those who are allergic to footnotes and phrases in languages other than English. Otherwise, I am delighted in how easy the reading is in all the contributions from eighteen (18) major scholars on the New Testament. Much of this is attributable to the marching orders given to the writers by the two editors. This list of guidelines makes the diverse contributions very uniform, which contributes to the value of this book as the guide to a specialized type of Bible study based on this book's subject. Anyone who has tracked down more than a handful of OT passages used in the NT will realize that the NT writers often take some liberties with their interpretations, reading in a prophesy about Jesus which, in the original text actually referred to something completely different. And, one has also run across a wide range of different ways in which OT texts are used, from `exact' quotes to paraphrases to allusions. The editors address this range by asking all authors to address their OT citations from at least five different points of view. These are: 1. What is the NT context of the citation? What is the genre and literary structure of the book or chapter? 2. What is the OT context of the citation? Do these Markan citations come directly from Exodus, for example, or are they quoted from Isaiah's use of Exodus verses? 3. How was the OT quote handled or interpreted by Second Temple Judaism, or early Judaism in general? 4. From what text is the OT quotation copied. The Septuagint (LXX), the Masoretic text, or a Targum (scripture translated into Aramaic or Coptic). 5. What is the ultimate use or connection being made by the NT author's use of the OT. Is it simply to emote a connection, is it a use of a common OT idiom, is it a parable use, shorthand to evoking an OT story, or is there a belief that events in NT times fulfill a specific OT prophecy. Of course, many commentaries on individual NT books do this as well, but most do not go into detail on points 2, 3, and 4. In looking at those parts of the NT I know best, I find this book delivers everything it promises on these five points, but that the book cannot replace good commentaries and study Bibles for NT books. In looking at one of the most famous uses of OT scripture in Luke, at 4:18 - 19, where Jesus teaches from Isaiah 61:1 - 2, the authors, David Pao and Eckhard Schnabel cover all the editors' points admirably, including references to important opinions by famous scholars such as Rudolph Bultmann. For this passage and for all others in this chapter on Luke, the actual passage is NOT presented in any translation. Therefore, one has to have a copy of the Bible open to the passage, as you read the authors' interpretation of it. Less important is the fact that the explanation of this section of Luke on Jesus' teaching in the Nazareth synagogue says nothing about the puzzling climax, where the congregation turns on Jesus. But that is a logical limitation of the approach, and is not relevant to the subject of the book. The introduction to Lucan passages was illuminating, as it tells us that even though one of Luke's primary objectives was to show the resolution of OT prophesies, Luke actually uses fewer OT quotes than Matthew. This is rarely discussed in commentaries on Luke. So, especially with regard to the synoptic Gospels, this would be an excellent book to use as a guide to OT references in the NT. For the scholar, there is the usual tower of bibliographical references after each article, plus the usual index to Biblical citations at the back of the book. There was just one thing I wanted which is missing. This is a `reverse' index, if you will, of OT books, with the number and locations of where verses are cited in the NT. The reason for wishing such an index is as a guide to selecting which OT books may best be studied together, as with Luke and Deuteronomy (some commentators claim the 10 chapter journey of Jesus to Jerusalem is patterned after Deuteronomy). Ultimately, this is a great reference if you make a habit of studying NT scriptures in depth, as either a pastor or bible study teacher.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on December 19, 2007

recommand products