If the Start/Stop modules you have are not sealed in Expoxy, then have someone change the time constant for you.
If the time interval is set into firmware, then you may not be able to alter it without the proper programmer interface. If it is as simple as external resistor/capacitor loop on a timer chip, then the values can be calculated, and changed to new calculation to extend the time.
Someone really sharp with programming an Arduino micro controller could easily set that up to have relay fed via optical isolation to provide contact closure at the amperage required unless you just need a pulse for x microseconds (or seconds or whatever). Depending on the milli, micro or amp requirement to connect too, there are interfaces for an Arduino that can handle that too. Programming code is fairly simple for an Arduino.
A Rasberry Pi is more of an actual computer and it runs on special version of Linux operating system. Because it is a computer with an actual OS versus an Arduino which is a controller running dedicated task based on simpler firmware coding. Given the single minded nature of the job to be done here, I should think almost any version of an Arduino would work. I am not an expert here; find someone that is well versed and perhaps for not very much money, you can coax them into writing the code if you buy the hardware for him or her to make this for you.
Using an Arduino solution will be simple enough. Powered on, it will await a trigger from low battery situation to do its thing. If it is powered off, then your present manual method of starting up the engine will be back in play.
The firmware needs to have a line in the code for setting the length of time. If the Arduino is powered off, the engine would stop right then if the output driver device is goes to an "open" state for a relay which will relax (disconnect. If the output driver device connects to electronics in the vehicle to start the engine, then an open state output device probably is not the correct choice; the zero-state output would have to be clamped to a high or low state (whatever the engine electronics requires) to insure engine absoluty shuts off when no power to the Arduino or Arduino is powered but firmware instrucs the output driver to change to the state that the engine electronics recognizes as off, kill, key off or whatever term is appropriate.
There might be a mini-market for this. Except MERCEDES, FORD and RAM likely handle ignition on/ignition off differently. Getting to the wiring in the dash or underhood to tap into likely to be a challenge on these newer vehicles. I am sure you can forget about vehicle warranty. Making a mistake, especially on a Sprinter could be costly if dealer help required to fix the van. And you know a dealer service company will disconnect or make you disconnect your circuitry before they do any work on the original equipment.
Just tossing some seeds out.
|