MYGIG LOCKPICK
#41
![Default](https://dodgeforum.com/forum/images/icons/icon1.gif)
I just stole this from one of my previous posts..
Thecamera that is provided on the LockPick site doesn't need the Green wire connected to anything if you install it in the backof the car. The redgoes to the red of the LockPick's extrapower out and the black goes to the Black of the LockPick's Extra Ground wire. Otherwise you just plug the video of the camera into the cable marked Camera on the LockPick media cable (If you purchased it)
So its the green wire that doesnt need to be hooked up which will mirror the image if it is..
Thecamera that is provided on the LockPick site doesn't need the Green wire connected to anything if you install it in the backof the car. The redgoes to the red of the LockPick's extrapower out and the black goes to the Black of the LockPick's Extra Ground wire. Otherwise you just plug the video of the camera into the cable marked Camera on the LockPick media cable (If you purchased it)
So its the green wire that doesnt need to be hooked up which will mirror the image if it is..
#42
![Default](https://dodgeforum.com/forum/images/icons/icon1.gif)
So its the green wire that doesnt need to be hooked up which will mirror the image if it is..
Yes, tape the green wire so that it cannot touch anything metal and thus ground itself or you will not have the mirror effect.
I insulated the end but taped it next to the black camera ground and left the little yellow sticker attached that says to ground it if I don't want the mirror effect. I figure maybe a future owner might want it the opposite way.
Yes, tape the green wire so that it cannot touch anything metal and thus ground itself or you will not have the mirror effect.
I insulated the end but taped it next to the black camera ground and left the little yellow sticker attached that says to ground it if I don't want the mirror effect. I figure maybe a future owner might want it the opposite way.
#43
![Default](https://dodgeforum.com/forum/images/icons/icon1.gif)
Is it just me or is anyone else unable to input with the keyboard while moving onthe Point of Interestscreen.
The computer keeps denying me access to the keyboard as soon as I move the car. Ithought Lockpick was supposed to disable all thesefeatures so that we could access them while moving.
The computer keeps denying me access to the keyboard as soon as I move the car. Ithought Lockpick was supposed to disable all thesefeatures so that we could access them while moving.
#45
#46
#47
![Default](https://dodgeforum.com/forum/images/icons/icon1.gif)
Is it just me or is anyone else unable to input with the keyboard while moving onthe Point of Interestscreen.
Mine will do that unless I toggle the power on/off button twice rapidly. Then I can use the keyboard while moving.
If I don't do that I get the "This feature is disabled while in motion" message,or something like that. After I toggle the power button and try it again that warning doesn't pop back up.
Mine will do that unless I toggle the power on/off button twice rapidly. Then I can use the keyboard while moving.
If I don't do that I get the "This feature is disabled while in motion" message,or something like that. After I toggle the power button and try it again that warning doesn't pop back up.
#48
![Default](https://dodgeforum.com/forum/images/icons/icon1.gif)
Well, this is interesting. After I posted that comment yesterday about my POI keyboard input screen working while in motion I got to thinking that Imight have been using the nav street address keyboard instead of the POI.
On my way to work I tried the POI keyboard and it worked without me even having to toggle the power on/off button. I tried it again on the way home last night, without toggling the Lockpick mode on, and it worked again. Maybe it has something to do with the v9.713 update.
On my way to work I tried the POI keyboard and it worked without me even having to toggle the power on/off button. I tried it again on the way home last night, without toggling the Lockpick mode on, and it worked again. Maybe it has something to do with the v9.713 update.