DEF Status Lamps
- vchauhan
- Posts: 4
- Joined: Thu Mar 06, 2014 9:21 am
DEF Status Lamps
1. DEF level <=10% DEF - Inducement and DEF Level Lamp solid --> ACM-DM1 (SPN 3517/FMI 17)
2. 7.5 >=DEF Level<5% - DEF Inducement Lamp flashing, LIM and DEF Level Lamp solid --> ACM-DM1 (SPN 3517/FMI 14)
3. 5%>=DEF level >2.5% - DEF Inducement and LIM Lamp flashing, DEF Level Lamp solid --> ACM-DM1 (SPN 3517/FMI 18)
4. 2.5%>=DEF level >0% - DEF Inducement and LIM Lamp flashing, DEF Level Lamp and Stop Lamp solid --> ACM-DM1 (SPN 3517/FMI 1)
5. DEF level=0% - DEF Inducement, LIM DEF Level Lamp and Stop Lamp flashing --> ACM-DM1 (SPN 3517/FMI 31)
For every stage buzzer should be activated only for 5 sec. for inducement override it should be continuously active.
Buzzer is hardwired.
I have not hardwired these lamp. I am showing it on display. I have created J1939 parameters in database, variables & state machines for flashing the Lamps in programming and graphics on main display page. I have shown these parameter in "Transmit Device-Engine Device"--> "connections" tab.
I am struggling with how to make above sequence happen (1 to 5 steps).
Thanks in advance for your suggestions.
2. 7.5 >=DEF Level<5% - DEF Inducement Lamp flashing, LIM and DEF Level Lamp solid --> ACM-DM1 (SPN 3517/FMI 14)
3. 5%>=DEF level >2.5% - DEF Inducement and LIM Lamp flashing, DEF Level Lamp solid --> ACM-DM1 (SPN 3517/FMI 18)
4. 2.5%>=DEF level >0% - DEF Inducement and LIM Lamp flashing, DEF Level Lamp and Stop Lamp solid --> ACM-DM1 (SPN 3517/FMI 1)
5. DEF level=0% - DEF Inducement, LIM DEF Level Lamp and Stop Lamp flashing --> ACM-DM1 (SPN 3517/FMI 31)
For every stage buzzer should be activated only for 5 sec. for inducement override it should be continuously active.
Buzzer is hardwired.
I have not hardwired these lamp. I am showing it on display. I have created J1939 parameters in database, variables & state machines for flashing the Lamps in programming and graphics on main display page. I have shown these parameter in "Transmit Device-Engine Device"--> "connections" tab.
I am struggling with how to make above sequence happen (1 to 5 steps).
Thanks in advance for your suggestions.
- jpratt
- Enovation Controls Development
- Posts: 222
- Joined: Mon Jun 21, 2010 11:18 am
Re: DEF Status Lamps
I'm not sure you have enough detail here to describe what your trying to do. Could you narrow it down a bit and possibly describe it in terms of PowerVison variables events etc and the response your trying to achieve.
It seems like you have some variables that you are wanting to watch and then initiate a DM? Buzzer IO? This could probably be accomplished with a state machine that transitions based on some event conditions but not sure i follow enough to know for sure.
Maybe someone else can chime in and have some suggestions as well.
It seems like you have some variables that you are wanting to watch and then initiate a DM? Buzzer IO? This could probably be accomplished with a state machine that transitions based on some event conditions but not sure i follow enough to know for sure.
Maybe someone else can chime in and have some suggestions as well.
Jake Pratt
Software Development Manager
Software Development Manager
- vchauhan
- Posts: 4
- Joined: Thu Mar 06, 2014 9:21 am
Re: DEF Status Lamps
you are right. I have few variables to flash all these lights eg. VAR DEF Level Lamp Flash, VAR Tier4 DEF Inducement Lamp Flash, VAR LIM Lamp Flash, VAR Stop Engine Lamp Flash and corresponding state machines to flash lamp. I have J1939 parameters too.
I want to accomplish "DEF Inducement and LIM Lamp flashing, DEF Level Lamp and Stop Lamp solid" when DEF Level condition is 2.5%>=DEF level >0% & buzzer should be active for 5 Sec.
I know that I can accomplished with a state machine that transitions based on some event conditions but I am struggling with how I should create it & where I should use particular conditions. I am not good at state machines.
Thanks for prompt reply.
I want to accomplish "DEF Inducement and LIM Lamp flashing, DEF Level Lamp and Stop Lamp solid" when DEF Level condition is 2.5%>=DEF level >0% & buzzer should be active for 5 Sec.
I know that I can accomplished with a state machine that transitions based on some event conditions but I am struggling with how I should create it & where I should use particular conditions. I am not good at state machines.
Thanks for prompt reply.
- jpratt
- Enovation Controls Development
- Posts: 222
- Joined: Mon Jun 21, 2010 11:18 am
Re: DEF Status Lamps
Well...lets see. I can't create a whole demo for you as this is somewhat complex but i think it would work like this.
In a state machine you are going to have 5-6 states. One state will be the system in normal operation. Then you will have one more state for each of your scenarios above. Each time your DEF level (or other variables) change you will want to fire an event that runs a series of "Event Conditions" in your state machine. Each condition should be tied to an event which takes you to one of your condition states. On the entry of these states, set your values (Use Calulated Variables for lamps etc). Then on entering the state you will set a 5 second timer that takes you back to your resting condition.
As an alternative to state machines you could try out using an Activity Program tied to the variables change (Fire On Change). Before diving into Activity Programming take a look at the read the Programming Manual for 2.7. This will let you visually check the variables using a Multi-Decision shape then set the appropriate variables. You will still have to fire a 5 second timer (using an action shape) to reset your buzzers, etc. when the time out is complete.
If this doesn't get you going, you might contact our Tech Services group. They can get you in contact with someone that can quote doing some work for you to assist with getting a more advanced
In a state machine you are going to have 5-6 states. One state will be the system in normal operation. Then you will have one more state for each of your scenarios above. Each time your DEF level (or other variables) change you will want to fire an event that runs a series of "Event Conditions" in your state machine. Each condition should be tied to an event which takes you to one of your condition states. On the entry of these states, set your values (Use Calulated Variables for lamps etc). Then on entering the state you will set a 5 second timer that takes you back to your resting condition.
As an alternative to state machines you could try out using an Activity Program tied to the variables change (Fire On Change). Before diving into Activity Programming take a look at the read the Programming Manual for 2.7. This will let you visually check the variables using a Multi-Decision shape then set the appropriate variables. You will still have to fire a 5 second timer (using an action shape) to reset your buzzers, etc. when the time out is complete.
If this doesn't get you going, you might contact our Tech Services group. They can get you in contact with someone that can quote doing some work for you to assist with getting a more advanced
Jake Pratt
Software Development Manager
Software Development Manager
- vchauhan
- Posts: 4
- Joined: Thu Mar 06, 2014 9:21 am
Re: DEF Status Lamps
Thanks for suggestion.
where I can get "Programming Manual for 2.7"?
where I can get "Programming Manual for 2.7"?
- jpratt
- Enovation Controls Development
- Posts: 222
- Joined: Mon Jun 21, 2010 11:18 am
Re: DEF Status Lamps
Manuals are always linked from the software download post in the Software and Documentation Forum. Look at the Post for PowerVision 2.7 and you will find it linked there.
Jake Pratt
Software Development Manager
Software Development Manager
- vchauhan
- Posts: 4
- Joined: Thu Mar 06, 2014 9:21 am
Re: DEF Status Lamps
I am getting 404 error when I am trying to upload program in PV450. Any Suggestions...
Thanks
Thanks
- jpratt
- Enovation Controls Development
- Posts: 222
- Joined: Mon Jun 21, 2010 11:18 am
Re: DEF Status Lamps
A 404 Error indicates that you tried to load a pre ECC load. But it can also be caused by other things.
This means that you used an older version of the tool to load a configuration. Make sure you are....
1. Working on a display that's had the upgrade performed (new pretty bootloader)
2. Using a version of PowerVision that is made after July 13. 2.3.2XXX, 2.6.20000, 2.7.
3. Make sure you did an "Full Install".
If in doubt, you can upload a picture of your boot loader (showing part number) or give Tech Services a call and they can probably go through a few options to see whats happening.
This means that you used an older version of the tool to load a configuration. Make sure you are....
1. Working on a display that's had the upgrade performed (new pretty bootloader)
2. Using a version of PowerVision that is made after July 13. 2.3.2XXX, 2.6.20000, 2.7.
3. Make sure you did an "Full Install".
If in doubt, you can upload a picture of your boot loader (showing part number) or give Tech Services a call and they can probably go through a few options to see whats happening.
Jake Pratt
Software Development Manager
Software Development Manager