Sunday, October 02, 2016

CMT Freedom Solution, Boot Up Bug Fix....by Jim Thomas

            
  

If you have the CMT Freedom solution fitted in your Taxi, you may have had occasions where the system fails to boot up, using the reboot option from the off switch doesn't help.

It's very annoying, as you then have to park up, switch every thing off and wait for the card reader in the rear to go dark. Speaking to other users, this is common. 
CMT have set up a 24/7 number to take card payments over the phone, should your equipment fail completely. Most customers appear not to be too enthusiastic about this option.

I have spoken to CMT and they have sent me a quick fix solution, that doesn't involve parking up, switching off and wasting time. It can be done on the go.

Below is CMT'S solution:

Hi Mr Thomas,

Firstly here's our Out Of Hours number: 0203 608 1341. Their primary roll is to take payments if needed, but they can also advise on technical queries.

Now to the system reset. If your screen is saying 'waiting for communication' there will be a Config button on the bottom right. The other way of reaching this point is by pressing Menu from the Map screen. The process is:

Config (or Configuration)

Peripherals

TaxiLinq (with a blue box by it, situated at the bottom of the screen)

Then choose any of the options and press Reset. Message will read TaxiLinq is being restarted.

Then press Menu, followed by Map. You'll see the 9 icons drop away to 4 and gradually re-establish themselves and turn green with the final icon, which represents the pinpad, the last to go green. If any don't go green it points to where the fault lies.

This resets the communication between every element of the system. In addition to this, ensuring you sign off before powering off the tablet every evening will help the general health of the tablet ... as with all such devices it benefits from being powered off completely.

Hope that's all clear.

Nick, CMT. 

As luck would have it, the night after I receive this email, my system failed to boot up, and so I was able to try the fix. It worked. 

For those of you who find I written instructions confusing, I've made a short video, running through the process. 
Hope this helps.