PcmHacks Versions Save

The big news for this release is that PCM Hammer now supports reading and writing P10 and P12 PCMs.

Kudos to Gampy and Antus and everyone who helped with investigating, troubleshooting, and testing.

Since P10 and P12 support is so new, you should consider yourself a beta tester if you're working with those PCMs. There's a difference between "it has worked" and "it always works," and we need your help to find out exactly where we're at. There may be some issues to address before P10 and P12 PCMs can be flashed as reliably as P01 and P59 PCMs.

Please post in this thread about what works for you, and what doesn't.

Also note that the community will need volunteers to:

• contribute bin files for P10 and P12 PCMs
• document variations of P10 and P12 PCMs
• document which makes / models / years used which PCMs and which variants
• figure out which operating systems can support the widest variety of vehicles
• create XDFs for the highest-value operating systems

And we'll need one or more volunteers to create and maintain a collection of P10 and P12 bin files and XDF files.

Please don't make OS or calibration changes in your only car. This software has a pretty good track record so far, but if something goes wrong, it may be a while before you drive that car again.

That said, writing to flash memory is the only thing that can do any harm. Reading and data logging are perfectly safe.

How to get it:

• If you're handy with computers, scroll down to the 'assets' section of this page, download the zip file, unzip all of the files into an empty directory, and run PcmHammer.exe or PcmLogger.exe. When the window appears, the first thing you'll need to do is select the device that you're using.

• If you'd rather not deal with zip files, you can get the apps from the Windows app store - but note that the version on the Windows Store will not be updated until a couple days after the release is posted on GitHub and PcmHacking.net. This release is the "Beta" version for now, and it will be moved to the non-preview version a few people report that all is well. Just click the links below, and click the "Get" button on each page:

PCM Hammer: https://www.microsoft.com/en-us/p/pcm-hammer-beta/9ntmspjf27tk PCM Logger: https://www.microsoft.com/en-us/p/pcm-logger-beta/9png38rdzntl

To test PCM Hammer, click Read Properties to confirm that you've selected the device correctly - it should print a few details about your PCM. Then try "Read Entire PCM" (it's in the Tools menu). And then, if you're feeling bold... and if you have a different car that you can use to drive to work... try writing the calibration or parameter blocks.

To test PCM Logger, select some parameters or open a log profile. Click the "record" button to save data to a file. The list of parameters we have so far is just the beginning, but it will take some work to figure out what we're missing. If you can help with that, please share at http://pcmhacking.net/ .

This project is still in its early stages. You may encounter bugs. The software may behave in strange ways. Please report such things to us so that we can fix them.

If anything goes wrong, please take detailed notes about the exact steps that you took, and please also copy the contents of the Debug tab and save it to a file. We'll need that to figure out what went wrong, how to fix it, and how to prevent it from happening to anyone else.

The developers can be reached by creating a new thread at pcmhacking.net: https://pcmhacking.net/forums/viewforum.php?f=42

While we think it is just about impossible for this software to make your car unusable, please keep in mind that we're just a bunch of hobbyists who have been working on this stuff in our spare time. It's a miracle that we've gotten this far. If you need the guarantees that come with a commercial product, you should buy a commercial product.

There are no changes to flashing, but there are significant improvements to data logging:

• The app can now tell the PCM to send a stream of data, rather than requesting each row of data.
• If you select an unsupported parameter, you'll get an error instead of just a bunch of zeros in the log.
• If you select too many parameters, you'll get an error instead of just no logging. (in RC2)
• With ELM devices, if you don't have enough parameters selected, you'll get an error message instead of erratic data rates.
• If you change devices while logging, the app doesn't crash, and the parameter grid repopulates correctly.

There are improvements in other areas as well:

• Support for more AVT devices, contributed by Antus.
• Support for a new OBDX Pro VC device, contributed by Tazzi.
• Support for command line parameters, contributed by Joukoy.
• Better initialization of ELM devices, contributed by Gampy.
• Depending on whether you've already done a test write or a full read, you'll either get a stern warning or a simple confirmation before you try to write to the flash.

Please don't make OS or calibration changes in your only car. This software has a pretty good track record so far, but if something goes wrong, it may be a while before you drive that car again.

That said, writing to flash memory is the only thing that can do any harm. Reading and data logging are perfectly safe.

How to get it:

• If you're handy with computers, scroll down to the 'assets' section of this page, download the zip file, unzip all of the files into an empty directory, and run PcmHammer.exe or PcmLogger.exe. When the window appears, the first thing you'll need to do is select the device that you're using.

• If you'd rather not deal with zip files, you can get the apps from the Windows app store - but note that the version on the Windows Store will not be updated until a couple days after the release is posted on GitHub and PcmHacking.net. This release is the "Beta" version for now, and it will be moved to the non-preview version a few people report that all is well. Just click the links below, and click the "Get" button on each page:

PCM Hammer: https://www.microsoft.com/en-us/p/pcm-hammer-beta/9ntmspjf27tk PCM Logger: https://www.microsoft.com/en-us/p/pcm-logger-beta/9png38rdzntl

To test PCM Hammer, click Read Properties to confirm that you've selected the device correctly - it should print a few details about your PCM. Then try "Read Entire PCM" (it's in the Tools menu). And then, if you're feeling bold... and if you have a different car that you can use to drive to work... try writing the calibration or parameter blocks.

To test PCM Logger, select some parameters or open a log profile. Click the "record" button to save data to a file. The list of parameters we have so far is just the beginning, but it will take some work to figure out what we're missing. If you can help with that, please share at http://pcmhacking.net/ .

This project is still in its early stages. You may encounter bugs. The software may behave in strange ways. Please report such things to us so that we can fix them.

If anything goes wrong, please take detailed notes about the exact steps that you took, and please also copy the contents of the Debug tab and save it to a file. We'll need that to figure out what went wrong, how to fix it, and how to prevent it from happening to anyone else.

The developers can be reached by creating a new thread at pcmhacking.net: https://pcmhacking.net/forums/viewforum.php?f=42

While we think it is just about impossible for this software to make your car unusable, please keep in mind that we're just a bunch of hobbyists who have been working on this stuff in our spare time. It's a miracle that we've gotten this far. If you need the guarantees that come with a commercial product, you should buy a commercial product.

This release has no changes to the flashing utility but it fixes a bug in the logger that prevented RAM parameters from appearing in the parameter list.

Two warnings:

The logger might not work well until you add several parameters. If you notice it pausing 2-3 seconds between updates, just add a few more parameters. It should update every 100 milliseconds or so.

Please don't make OS or calibration changes in your only car. This software has a pretty good track record so far, but if something goes wrong, it may be a while before you drive that car again.

That said, writing to flash memory is the only thing that can do any harm. Reading and data logging are perfectly safe.

How to get it:

• If you're handy with computers, scroll down to the 'assets' section of this page, download the zip file, unzip all of the files into an empty directory, and run PcmHammer.exe or PcmLogger.exe. When the window appears, the first thing you'll need to do is select the device that you're using.

• If you'd rather not deal with zip files, you can get the apps from the Windows app store - but note that the version on the Windows Store will not be updated until a couple days after the release is posted on GitHub and PcmHacking.net. This release is the "Beta" version for now, and it will be moved to the non-preview version a few people report that all is well. Just click the links below, and click the "Get" button on each page:

PCM Hammer: https://www.microsoft.com/en-us/p/pcm-hammer-beta/9ntmspjf27tk PCM Logger: https://www.microsoft.com/en-us/p/pcm-logger-beta/9png38rdzntl

To test PCM Hammer, click Read Properties to confirm that you've selected the device correctly - it should print a few details about your PCM. Then try "Read Entire PCM" (it's in the Tools menu). And then, if you're feeling bold... and if you have a different car that you can use to drive to work... try writing the calibration or parameter blocks.

To test PCM Logger, select some parameters or open a log profile. Click the "record" button to save data to a file. The list of parameters we have so far is just the beginning, but it will take some work to figure out what we're missing. If you can help with that, please share at http://pcmhacking.net/ .

This project is still in its early stages. You may encounter bugs. The software may behave in strange ways. Please report such things to us so that we can fix them.

If anything goes wrong, please take detailed notes about the exact steps that you took, and please also copy the contents of the Debug tab and save it to a file. We'll need that to figure out what went wrong, how to fix it, and how to prevent it from happening to anyone else.

The developers can be reached by creating a new thread at pcmhacking.net: https://pcmhacking.net/forums/viewforum.php?f=42

While we think it is just about impossible for this software to make your car unusable, please keep in mind that we're just a bunch of hobbyists who have been working on this stuff in our spare time. It's a miracle that we've gotten this far. If you need the guarantees that come with a commercial product, you should buy a commercial product.

This release has no changes to the flashing utility but it fixes a bug in the logger that scrambled the values of some parameters (any parameter that requires two bytes of data).

Two warnings:

The logger might not work well until you add several parameters. If you notice it pausing 2-3 seconds between updates, just add a few more parameters. It should update every 100 milliseconds or so.

Please don't make OS or calibration changes in your only car. This software has a pretty good track record so far, but if something goes wrong, it may be a while before you drive that car again.

That said, writing to flash memory is the only thing that can do any harm. Reading and data logging are perfectly safe.

How to get it:

• If you're handy with computers, scroll down to the 'assets' section of this page, download the zip file, unzip all of the files into an empty directory, and run PcmHammer.exe or PcmLogger.exe. When the window appears, the first thing you'll need to do is select the device that you're using.

• If you'd rather not deal with zip files, you can get the apps from the Windows app store - but note that the version on the Windows Store will not be updated until a couple days after the release is posted on GitHub and PcmHacking.net. This release is the "Beta" version for now, and it will be moved to the non-preview version a few people report that all is well. Just click the links below, and click the "Get" button on each page:

PCM Hammer: https://www.microsoft.com/en-us/p/pcm-hammer-beta/9ntmspjf27tk PCM Logger: https://www.microsoft.com/en-us/p/pcm-logger-beta/9png38rdzntl

To test PCM Hammer, click Read Properties to confirm that you've selected the device correctly - it should print a few details about your PCM. Then try "Read Entire PCM" (it's in the Tools menu). And then, if you're feeling bold... and if you have a different car that you can use to drive to work... try writing the calibration or parameter blocks.

To test PCM Logger, select some parameters or open a log profile. Click the "record" button to save data to a file. The list of parameters we have so far is just the beginning, but it will take some work to figure out what we're missing. If you can help with that, please share at http://pcmhacking.net/ .

This project is still in its early stages. You may encounter bugs. The software may behave in strange ways. Please report such things to us so that we can fix them.

If anything goes wrong, please take detailed notes about the exact steps that you took, and please also copy the contents of the Debug tab and save it to a file. We'll need that to figure out what went wrong, how to fix it, and how to prevent it from happening to anyone else.

The developers can be reached by creating a new thread at pcmhacking.net: https://pcmhacking.net/forums/viewforum.php?f=42

While we think it is just about impossible for this software to make your car unusable, please keep in mind that we're just a bunch of hobbyists who have been working on this stuff in our spare time. It's a miracle that we've gotten this far. If you need the guarantees that come with a commercial product, you should buy a commercial product.

(I just realized that I skipped 16. Oh well, the zip is zipped and the branch is forked...)

This release has no changes to the flashing utility but has a bunch of changes to the logger:

• Merged many new parameters.
• Improved bit-flag support.
• Support for signed values may not be correct, but is certainly improved.
• Reloads last logging profile on startup.

There hasn't been a lot of interest in testing preview builds, and my car is still on jack stands, so consider this a beta quality release until you hear otherwise. :)

Two warnings:

The logger might not work well until you add several parameters. If you notice it pausing 2-3 seconds between updates, just add a few more parameters. It should update every 100 milliseconds or so.

Please don't make OS or calibration changes in your only car. This is new software, and you'll be among the first people in the world to use it. If something goes wrong, it may be a while before you drive that car again.

Reading and data logging are perfectly safe, though.

How to get it:

• If you're handy with computers, scroll down to the 'assets' section of this page, download the zip file, unzip all of the files into an empty directory, and run PcmHammer.exe or PcmLogger.exe. When the window appears, the first thing you'll need to do is select the device that you're using.

• If you'd rather not deal with zip files, you can get the apps from the Windows app store. This release is the "Beta" version for now, and it will be moved to the non-preview version a few people report that all is well. Just click the links below, and click the "Get" button on each page:

PCM Hammer: https://www.microsoft.com/en-us/p/pcm-hammer-beta/9ntmspjf27tk PCM Logger: https://www.microsoft.com/en-us/p/pcm-logger-beta/9png38rdzntl

To test PCM Hammer, click Read Properties to confirm that you've selected the device correctly - it should print a few details about your PCM. Then try "Read Entire PCM" (it's in the Tools menu). And then, if you're feeling bold... and if you have a different car that you can use to drive to work... try writing the calibration or parameter blocks.

To test PCM Logger, select some parameters or open a log profile. Click the "record" button to save data to a file. The list of parameters we have so far is just the beginning, but it will take some work to figure out what we're missing. If you can help with that, please share at http://pcmhacking.net/ .

This project is still in its early stages. You may encounter bugs. The software may behave in strange ways. Please report such things to us so that we can fix them.

If anything goes wrong, please take detailed notes about the exact steps that you took, and please also copy the contents of the Debug tab and save it to a file. We'll need that to figure out what went wrong, how to fix it, and how to prevent it from happening to anyone else.

The developers can be reached by creating a new thread at pcmhacking.net: https://pcmhacking.net/forums/viewforum.php?f=42

While we think it is just about impossible for this software to make your car unusable, please keep in mind that we're just a bunch of hobbyists who have been working on this stuff in our spare time. It's a miracle that we've gotten this far. If you need the guarantees that come with a commercial product, you should buy a commercial product.

Changes in this release:

• The logger has had a major rewrite, so you can now pick parameters from a list instead of editing XML files by hand.
• The reflash tool now has a progress bar and a time-remaining countdown.
• Lots of small fixes to make the apps more reliable and easier to use.
• You can also find PCM Hammer and PCM Logger in the Windows app store now. You get the same code that we posted here, but installation is simpler.

Two warnings:

The logger might not work well until you add several parameters. If you notice it pausing 2-3 seconds between updates, just add a few more parameters. It should update every 100 milliseconds or so.

Please don't make OS or calibration changes in your only car. This is new software, and you'll be among the first people in the world to use it. If something goes wrong, it may be a while before you drive that car again.

Reading and data logging are perfectly safe, though.

How to get it:

• If you're handy with computers, scroll down to the 'assets' section of this page, download the zip file, unzip all of the files into an empty directory, and run PcmHammer.exe or PcmLogger.exe. When the window appears, the first thing you'll need to do is select the device that you're using.

• If you'd rather not deal with zip files, you can get the apps from the Windows app store now. You get the same code either way. Just click the links below, and click the "Get" button on each page:

PCM Hammer: https://www.microsoft.com/en-us/p/pcm-hammer-beta/9ntmspjf27tk PCM Logger: https://www.microsoft.com/en-us/p/pcm-logger-beta/9png38rdzntl

To test PCM Hammer, click Read Properties to confirm that you've selected the device correctly - it should print a few details about your PCM. Then try "Read Entire PCM" (it's in the Tools menu). And then, if you're feeling bold... and if you have a different car that you can use to drive to work... try writing the calibration or parameter blocks.

To test PCM Logger, select some parameters or open a log profile. Click the "record" button to save data to a file. The list of parameters we have so far is just the beginning, but it will take some work to figure out what we're missing. If you can help with that, please share at http://pcmhacking.net/ .

This project is still in its early stages. You may encounter bugs. The software may behave in strange ways. Please report such things to us so that we can fix them.

If anything goes wrong, please take detailed notes about the exact steps that you took, and please also copy the contents of the Debug tab and save it to a file. We'll need that to figure out what went wrong, how to fix it, and how to prevent it from happening to anyone else.

The developers can be reached by creating a new thread at pcmhacking.net: https://pcmhacking.net/forums/viewforum.php?f=42

While we think it is just about impossible for this software to make your car unusable, please keep in mind that we're just a bunch of hobbyists who have been working on this stuff in our spare time. It's a miracle that we've gotten this far. If you need the guarantees that come with a commercial product, you should buy a commercial product.

This release contains a two big improvements and a few minor ones.

• Most critically, it addresses some reliability issues when using the app with the new ObdX Pro devices that came out a few weeks ago. They're now fast and reliable.
• Most operations with the AllPro are now much faster, and ObdLink LX devices are slightly faster.

One warning:

Please don't make OS or calibration changes in your only car. This is new software, and you'll be among the first people in the world to use it. If something goes wrong, it may be a while before you drive that car again.

Reading and data logging are perfectly safe, though.

To use this stuff, unzip all of the files into an empty directory, and run PcmHammer.exe or PcmLogger.exe. When the window appears, the first thing you'll need to do is select the device that you're using.

To test PCM Hammer, click Read Properties to confirm that you've selected the device correctly - it should print a few details about your PCM. Then try "Read Entire PCM" (it's in the Tools menu). And then, if you're feeling bold... and if you have a different car that you can use to drive to work... try writing the calibration or parameter blocks.

To test PCM Logger, open a log profile and click "start logging." To create your own log profile, open one of the examples in notepad.exe and... well, you're on your own. We'll add a proper UI for editing profiles in a future release. If you come up with something useful in the meantime, please share at http://pcmhacking.net/ . The existing log profiles are not guaranteed to be correct. The logger is still very much a work in progress, and help with the log profiles would be greatly appreciated.

This project is still in its early stages. You may encounter bugs. The software may behave in strange ways. Please report such things to us so that we can fix them.

If anything goes wrong, please take detailed notes about the exact steps that you took, and please also copy the contents of the Debug tab and save it to a file. We'll need that to figure out what went wrong, how to fix it, and how to prevent it from happening to anyone else.

The developers can be reached by creating a new thread at pcmhacking.net: https://pcmhacking.net/forums/viewforum.php?f=42

While we think it is just about impossible for this software to make your car unusable, please keep in mind that we're just a bunch of hobbyists who have been working on this stuff in our spare time. It's a miracle that we've gotten this far. If you need the guarantees that come with a commercial product, you should buy a commercial product.

(There is no Release 13. There almost was, but it had an issue SparkFun's Scantool-based interface device.)

Improvements in this release:

1. Full writes for the P59 PCMs (aka 1mb PCMs) are now supported.
2. Write Parameters (Clone) works again.
3. The most frequently used features (Read Properties, Test Write, Write) still have buttons on the main window, however other operations have been moved to a Tools menu at the top of the window.
4. You'll also find an Options menu that lets you enable and disable 4x communications. You'll probably want to leave that checked, but some vehicles have modules that send 1x messages during 4x communication, which interrupts reads and writes. Disabling 4x should work around that problem.
5. And a few minor bug fixes.

There's just one known issue in this release: Non-ELM devices will report retry counts after a read or write operation. This slow things down a little bit, and we're looking into a solution.

One warning:

Please don't make OS or calibration changes in your only car. This is new software, and you'll be among the first people in the world to use it. If something goes wrong, it may be a while before you drive that car again.

Reading and data logging are perfectly safe, though.

To use this stuff, unzip all of the files into an empty directory, and run PcmHammer.exe or PcmLogger.exe. When the window appears, the first thing you'll need to do is select the device that you're using.

To test PCM Hammer, click Read Properties to confirm that you've selected the device correctly - it should print a few details about your PCM. Then try "Read Contents." And then, if you're feeling bold... and if you have a different car that you can use to drive to work... try writing the calibration or parameter blocks.

To test PCM Logger, open a log profile and click "start logging." To create your own log profile, open one of the examples in notepad.exe and... well, you're on your own. We'll add a proper UI for editing profiles in a future release. If you come up with something useful in the meantime, please share at http://pcmhacking.net/ . The existing log profiles are not guaranteed to be correct. The logger is still very much a work in progress, and help with the log profiles would be greatly appreciated.

This project is still in its early stages. You may encounter bugs. The software may behave in strange ways. Please report such things to us so that we can fix them.

If anything goes wrong, please take detailed notes about the exact steps that you took, and please also copy the contents of the Debug tab and save it to a file. We'll need that to figure out what went wrong, how to fix it, and how to prevent it from happening to anyone else.

The developers can be reached by creating a new thread at pcmhacking.net: https://pcmhacking.net/forums/viewforum.php?f=42

While we think it is just about impossible for this software to make your car unusable, please keep in mind that we're just a bunch of hobbyists who have been working on this stuff in our spare time. It's a miracle that we've gotten this far. If you need the guarantees that come with a commercial product, you should buy a commercial product.

This release fixes an issue that made in-vehicle reading and writing unreliable for some users.

The .zip file was updated on 1/05 to add a missing MathValues.configuration file required by the logger. The .zip file was updated on 2/04 to add a missing .profile files required by the logger.

This release also adds support for logging Math parameters. Parameters are defined in the MathValues.configuration file, and will be added automatically when the required regular parameters are present. For example, if you log both MAF and RPM, the calculated Load parameter will be added automatically. Or if you log both Load and RPM, the calculated MAF parameter will be added.

The logger profile file format is changing. Existing profiles should be renamed to end with ".json.profile" to work with this version. New files with names ending in ".xml.profile" will be created automatically when you open an older file. Please use the new .xml.profile files going forward.

There are still two known issues, both of which are expected to be fixed soon:

1. Write Parameters (Clone) is disabled due to risk of data corruption.
2. For the P59 PCMs (aka 1mb PCMs), calibration writes are supported, but full OS writes are not.

One warning:

Please don't make OS or calibration changes in your only car. This is new software, and you'll be among the first people in the world to use it. If something goes wrong, it may be a while before you drive that car again.

Reading and data logging are perfectly safe, though.

To use this stuff, unzip all of the files into an empty directory, and run PcmHammer.exe or PcmLogger.exe. When the window appears, the first thing you'll need to do is select the device that you're using.

To test PCM Hammer, click Read Properties to confirm that you've selected the device correctly - it should print a few details about your PCM. Then try "Read Contents." And then, if you're feeling bold... and if you have a different car that you can use to drive to work... try writing the calibration or parameter blocks.

To test PCM Logger, open a log profile and click "start logging." To create your own log profile, open one of the examples in notepad.exe and... well, you're on your own. As noted above, this will get easier in future releases. If you come up with something useful in the meantime, please share at http://pcmhacking.net/ . The existing log profiles are not guaranteed to be correct. The logger is very much a work in progress, and help would be greatly appreciated.

This project is still in its early stages. You may encounter bugs. The software may behave in strange ways. Please report such things to us so that we can fix them.

If anything goes wrong, please take detailed notes about the exact steps that you took, and please also copy the contents of the Debug tab and save it to a file. We'll need that to figure out what went wrong, how to fix it, and how to prevent it from happening to anyone else.

The developers can be reached by creating a new thread at pcmhacking.net: https://pcmhacking.net/forums/viewforum.php?f=42

While we think it is just about impossible for this software to make your car unusable, please keep in mind that we're just a bunch of hobbyists who have been working on this stuff in our spare time. It's a miracle that we've gotten this far. If you need the guarantees that come with a commercial product, you should buy a commercial product.

This release fixes an issue that prevented reflashing of 1mb Intel chips. The app will also print the estimated time remaining during read and write operations.

There are two known issues, both of which are expected to be fixed soon:

1. Write Parameters (Clone) is disabled due to risk of data corruption.
2. For the P59 PCMs (aka 1mb PCMs), calibration writes are supported, but full OS writes are not.

One warning:

Please don't make OS or calibration changes in your only car. This is new software, and you'll be among the first people in the world to use it. If something goes wrong, it may be a while before you drive that car again.

Reading and data logging are perfectly safe, though.

To use this stuff, unzip all of the files into an empty directory, and run PcmHammer.exe or PcmLogger.exe. When the window appears, the first thing you'll need to do is select the device that you're using.

To test PCM Hammer, click Read Properties to confirm that you've selected the device correctly - it should print a few details about your PCM. Then try "Read Contents." And then, if you're feeling bold... and if you have a different car that you can use to drive to work... try writing the calibration or parameter blocks.

To test PCM Logger, open a log profile and click "start logging." To create your own log profile, open one of the examples in notepad.exe and... well, you're on your own. As noted above, this will get easier in future releases. If you come up with something useful in the meantime, please share at http://pcmhacking.net/ . The existing log profiles are not guaranteed to be correct. The logger is very much a work in progress, and help would be greatly appreciated.

This project is still in its early stages. You may encounter bugs. The software may behave in strange ways. Please report such things to us so that we can fix them.

If anything goes wrong, please take detailed notes about the exact steps that you took, and please also copy the contents of the Debug tab and save it to a file. We'll need that to figure out what went wrong, how to fix it, and how to prevent it from happening to anyone else.

The developers can be reached by creating a new thread at pcmhacking.net: https://pcmhacking.net/forums/viewforum.php?f=42

While we think it is just about impossible for this software to make your car unusable, please keep in mind that we're just a bunch of hobbyists who have been working on this stuff in our spare time. It's a miracle that we've gotten this far. If you need the guarantees that come with a commercial product, you should buy a commercial product.