The ignition on the PV750 has a significant bug in it for one of my applications. If the ignition is controlling on/off of the display (my switched power supply cannot handle full display's power requirements), it is possible to remove ignition without the unit powering down (or sleeping depending on the configuration). What I have found is that if the ignition signal is removed while the unit is booting up (anytime before the first user page is shown), the PV750 will contiue to boot and function as normal, only without ang ignition signal. To shut down, the ignition signal must be restored and then removed.

This is an issue in my system where we have multiple displays (up to 8) in remote locations with common ignition. Some of the displays have switched power, but several of the remote ones only have switched ignitions. It is quite common for a system to be powered on for times shorter than it takes to boot the display. The displays with switched power work as expected, but those with only switched ignitions stay on.

Thanks for the information - obviously a test that was missed on our end. I will make sure we get a resolution to this one in 2.3.

If you need a fix sooner, please let me know via PM so we can work out how that might be resolved in the interim.

Or ... we may determine this requires a patch prior to 2.3.

jpurdum

I too have an issue with the ignition switch on the PV750. If the unit is powered up and the ignition is then switched off, but BATT+ is held constant on on pin 1, port A, after an hour or two, the unit lights back up and will remain on. This is without the ignition wire connected (see picture). The only way to turn the display off again is to cycle the ignition contact.

I am using Windows 7 OS and the PowerVision Configuration Studio (Release Build) 2.2.10525 (2/14/2011).

I have a customer who is using the ignition switch to turn the display on/off. He is not breaking power to the PV750. What is the fix for this? I assume that this will require a firmware update, but if there is something I can do on the configuration side, please let me know.

Thank you!

How are you switching it off? Are you just removing ignition? Just removing ignition just kills the backlight.

With Bootloader 2.1.1 installed (previous version reboot the display), you can set a state machine to fire CCM-Shutdown upon the event Sys.IgnitionOff. This will actually power down the display. I have not tested it for long term (I will tomorrow), but my customers are also just using the ignition.

I am switching the ignition off by just removing the ignition. It does kill the backlight, but eventually, the backlight turns back on. What would cause the backlight to come back on without B+ to the ignition?

I'm not doubting that the backlight coming on is indeed a bug. I'm just pointing out that the display is not turning off just be removing the ignition. This can be importanmt if you need default values to load or state machines to run at startup.

Anyway, a work around for you may be to fully shut down the display as described in my earlier post.

Another issue I have come accross with the ignition is its sesitivity. I have found that with the ignition disconnected (floating) and the display shutdown (ccm-shutdown after sys.ignitionoff with 2.1.1), I can turn the unit back on by touching the the ignition lead with my hand (not connecting it to B+). It is intermittant just touching it, but if I am also touching B+ with my hand, then it triggers the display to turn on every time. Keep in mind, I am not actually touching B+ to the ignition input; the current is flowing through my hand.