<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Questions &amp; Answers - Questions récentes tagguées p0513</title>
<link>/en/qa/tag/p0513</link>
<description>Powered by Question2Answer</description>
<item>
<title>JEEP patriot  2008 2.4 4*4 Fortin EVO-All +CHRT5 error p0513 in memory</title>
<link>/en/qa/100736/jeep-patriot-2008-2-4-4-4-fortin-evo-all-chrt5-error-p0513-in-memory</link>
<description>

&lt;pre class=&quot;tw-data-text tw-text-large XcVN5d tw-ta&quot; dir=&quot;ltr&quot; id=&quot;tw-target-text&quot; style=&quot;text-align:left&quot;&gt;
&lt;span lang=&quot;en&quot;&gt;Good day!
JEEP Patriot 2008 2.4 connected Fortin EVO-ALL via CHRT5.
Everything works as it should, the only moment that confuses and I want to solve this problem is that it gives error p0513 in the memory of the car. This happens when, after autostart, insert the key into the ignition switch, turn it to the &quot;on&quot; position and press the brake pedal. It turns out that when the control is transferred to the standard immobilizer in the key, the signal is lost and gives an error, but does not light the lamp.
The key is programmed.
After updating the firmware of the unit, I reset it to factory settings. It seems that I did everything according to the instructions.
What could it be?
Sorry for my english-gogl translation.&lt;/span&gt;&lt;/pre&gt;</description>
<category>Jeep</category>
<guid isPermaLink="true">/en/qa/100736/jeep-patriot-2008-2-4-4-4-fortin-evo-all-chrt5-error-p0513-in-memory</guid>
<pubDate>Tue, 15 Dec 2020 05:19:57 +0000</pubDate>
</item>
<item>
<title>P0513 code 2005 Chrysler 300c Evo All Stand Alone Connection F Everything Working.</title>
<link>/en/qa/99853/p0513-code-2005-chrysler-300c-evo-all-stand-alone-connection-f-everything-working</link>
<description>

&lt;p&gt;
	&lt;span style=&quot;font-size:18px;&quot;&gt;It&#039;s like a false/positive situation. I had someone overpress my rf remote and oem key was starting car on one lock. blah blah blah&lt;/span&gt;&lt;/p&gt;


&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;


&lt;p&gt;
	&lt;span style=&quot;font-size:18px;&quot;&gt;Reprogrammed both sets of keys (2 oem&#039;s and 2 RF RM411 long range one way remotes). Everything works fine again, but if I use the one button RF RM411 I get the code thrown and a little red security light stays on for a couple of seconds once my key is in on position in ignition.&lt;/span&gt;&lt;/p&gt;


&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;


&lt;p&gt;
	&lt;span style=&quot;font-size:18px;&quot;&gt;Now if I just use the OEM key, I don&#039;t get the red light. Also there is no engine light with code. The only reason I know it&#039;s there is I had the car seafoamed (should have done through break booster after MAF, used intake manifold. Had engine lights galore and ended up changing all 16 spark plugs myself (the good ones) and clearing misfire and crankshaft sensor codes.&lt;/span&gt;&lt;/p&gt;


&lt;p&gt;
	&lt;span style=&quot;font-size:18px;&quot;&gt;Anyways, all is working great now, except this code I can&#039;t seem to clear in any way. Is this an issue with my car or Chrysler products?&amp;nbsp;&lt;/span&gt;&lt;/p&gt;


&lt;p&gt;
	&lt;span style=&quot;font-size: 18px;&quot;&gt;Usually when you have this code, the car will start but quit soon after.&lt;/span&gt;&lt;/p&gt;


&lt;p&gt;
	&lt;span style=&quot;font-size: 18px;&quot;&gt;Just let me know and I will just leave it alone and not worry about it.&lt;/span&gt;&lt;/p&gt;</description>
<category>Chrysler</category>
<guid isPermaLink="true">/en/qa/99853/p0513-code-2005-chrysler-300c-evo-all-stand-alone-connection-f-everything-working</guid>
<pubDate>Tue, 17 Nov 2020 22:26:03 +0000</pubDate>
</item>
<item>
<title>p0513 stored</title>
<link>/en/qa/75231/p0513-stored</link>
<description>a chaque demarage a distance laise un code p0513 stored mais non actif et ne fait pas allumer le check engine</description>
<category>Jeep</category>
<guid isPermaLink="true">/en/qa/75231/p0513-stored</guid>
<pubDate>Sat, 24 Dec 2016 12:44:08 +0000</pubDate>
</item>
<item>
<title>2006 Dodge Ram red security light flashes on remote start</title>
<link>/en/qa/66408/2006-dodge-ram-red-security-light-flashes-on-remote-start</link>
<description>Hello there,&lt;br /&gt;
&lt;br /&gt;
I have an EVO-ALL (service # 001A06416265) with a Crimestopper LCPro-4. &amp;nbsp;It has been working just fine on my 2006 Ram 1500 up until recently. &amp;nbsp;I recently bought two Sentry Keys for my truck, which I programmed myself using the customer key programming described in the Dodge owner&amp;#039;s manual. &amp;nbsp;I have a total of 5 keys for the truck now, all of them work properly.&lt;br /&gt;
&lt;br /&gt;
The problem I am experiencing - whenever I remote start the truck, the red security light in the instrument cluster blinks. &amp;nbsp;It continues to blink even after I insert a key and take over from remote start. &amp;nbsp;The only way to get the light to shut off is to shut off the truck and restart with the key. &amp;nbsp;The odd thing is the truck starts and runs just fine when remote started...everything works the same as it did before, but now that security light blinks.&lt;br /&gt;
&lt;br /&gt;
I plugged my OTC Genisys scan tool into the truck and get a code: &amp;nbsp;P0513 &amp;quot;invalid SKIM key&amp;quot;. &amp;nbsp;I cleared the codes. &amp;nbsp;The same code comes back if I remote start the truck.&lt;br /&gt;
&lt;br /&gt;
I did a Master Reset on my EVO-ALL module, and went through the programming procedure on it again. &amp;nbsp;It completed programming successfully. &amp;nbsp;No change. &amp;nbsp;All functions still work, but the red light is still blinking when the truck is remote started.&lt;br /&gt;
&lt;br /&gt;
Thanks in advance for all your help!&lt;br /&gt;
&lt;br /&gt;
-Darren Asuncion</description>
<category>Dodge</category>
<guid isPermaLink="true">/en/qa/66408/2006-dodge-ram-red-security-light-flashes-on-remote-start</guid>
<pubDate>Sun, 20 Dec 2015 02:31:51 +0000</pubDate>
</item>
</channel>
</rss>