2015 Elantra with dball2 goin to fortin

Ok so I have a 2015 Hyundai ELantra Key start currently using an avital 4103 LX and DBALL2 in the method 1 install using D2D. Both fortin and a local shop say that if I replace the DBALL2 with a EVO-ALL the annoying light cutout aka lightflash during unlock issue that DBALL2 does on this model car will not happen with the EVO-ALL. Has anyone here used the EVO products that can confirm I wont have this problem? I dont want to buy this to end up the same again. Im already upset to be throwing out my first setup. Please advise. Im willing to spend money for the right function. I will love to update to the EVO-ALL if I know this will solve the issue.

I appreciate the fact that you want this to work a certain way. Why not just use the module for immobilizer bypass only and hardwire the rest from the remote start to the car?

If I hard wire my avital and use dball2 as bypass only will it still unlock during remote start since the elantra disables unlocking with engine running? Would it cure light flash? If so I just might. hmm would this give me driver priority unlock from Avital remote? It would be easy to wire and I have xkloader to fix the settings in dball2 Im willing to do the work I already know where to tap. been debating this but dont know if Im sending unlock command direct rather than going through can if it will work with engine running. I also dont understand the whole light malfunction since the dball is working via can bus. it seems glitchy to me.

No driver's door priority with the Avital. Elantra disables unlocking with engine on? Never heard of that. If your door lock switch doesn't work, you should check with the dealer.

Sorry I meant to say disables unlocking with oem fob with car on, this is normal. Anyhow picked up and flashed a Fortin Evo-All tonight and Under D2D settings unlike the DBALL2 if actually had a setting for driver priority unlock over D2D unlock signal. Was telling the installer who doesnt use the DBALL modules about my issue and I showed it to him he said weird. I will post a video of all my issues with the dball2 and a video of if they are gone with the fortin when Im done. Considering the many firmware updates on this unit for my car on the fortin vs the DBALL2 using the same firmware for 2011-2013 and 2014 to 2016 with no updates since 2013 I think it will be positive. If this doesnt work out my next step will be pull it all out hardwire everything and try and use bypass for imob only.

hold the phones here, neither the dball2 guide or the fortin guide says anything about controlling parking lights via bypass solution. The r/s controls parking lights via ground trigger at the switch. Does the problem with not flashing the lights occur when the headlight switch is left in the on position and you use the avital remote? If so, then maybe use + parking lights from r/s to vehicle which may require 2 diodes to separate right and left side wires.Advanced

Exactly!!! Even with the parking lights on connected to the RS the DBALL2 cuts out the power to the "HEADLIGHTS" not just parking ligths. I have 4 cars I can show this on all proper installs. only occurs on 2014+ Had an installer check my car in case I did something wrong he opened up with the problem Im reporting is not a problem because he sees it all the time with the dball2 FYI I never even hooked up the parking lights. Thing is I want to use 1 fob for everything and unlocking via canbus on 2014+ Elantras with the DBALL2 causes this. Ive been told now by 2 local installers and by Fortin that the fortin uses OE code to unlock over can bus and this behaviour does not occur with Fortins module. Im not mocking the DBALL2 Im simply saying its not good on this car. They use the same firmware from 2011-2016. In 2014 the electrical on this car was revised drastically. The problem doesnt happen on 2011-2013 models but does on 2014-2016 models. The fortin has a seperate firmware for 2011-2013 and 2014 to 2016. Firmware for the 2014 to 2016 last updated 3 weeks ago. DBALLS last update was before the revision.... I will be posting a youtube video later of the DBALL2 in this car vs the FOrtin in this car. I will show the multiple reasons for my switch.

Is your vehicle a US car? If so you probably have no transponder so no need for a module. Also which model of Elantra do you have? You could use the Fortin EVO-ONE with the T-harness to make the install easier. The Dball nor the EVO-ALL should control anything with the parking lights.

if i didnt have an immobilizer i wouldnt buy a bypass..... my point exactly thats why i call it a bug the dball shouldnt do anything to the lights but on this pecific model there is a BUG which cuts out lighting when headlights on and unlock request is sent via can bus. bug and unwanted behavior. this is why im switching modules.

Well that took all day. And waste of time... The lightflash is still there when unlock over d2d. The biggest change I see is the lock/unlock over D2D was instant with the dball2 and delayed with the evo-all I am very picky with my stuff looking cleasn and oem so this took forever I dont feel like doing it again. Guess I have to live with it :( I dont understand how fortin thinks this doesnt happen and it does. Same with DEI.