Support Forums
Schedule Trigger Problem

Hi

I have written this program using the dex interface:
CODE: SELECT ALL
BEGIN"config"
' Generated by dEX Configuration Builder Version 1.84.030 (Firmware Version 9.20.8973)

' Target device: DT80LM3-4

password=""

S1=30,130,590,2565

RS1S

RA"BMW Running"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)1035-CV

LOGONA

1TK("T1~degC",=1001CV,LM,NA)

1*TK("T2~degC",=1004CV,LM,NA)

2TK("T3~degC",=1007CV,LM,NA)

2*TK("T4~degC",=1010CV,LM,NA)

4*V("PT1Scaled~bar",=1033CV,LM,S1,NA,GL3V)

4V("PT2Scaled~bar",=1034CV,LM,S1,NA)

4*V("PT1~mV",=1013CV,W,NA,GL3V)

4V("PT2~mV",=1014CV,W,NA)

' User defined

RA1S 1HSC(=1CV,R,RS,W);


CALC("Speed~kph",=1032CV,LM)=1CV/25

1DS("ReadASwitch_7~",=1035CV,LM)

1C("LowSpeedCounter_8~",=1036CV,LM,1000)

END

The schedule should start when the "1DS" channel switch changes from 1 to 0, however the schedule starts as soon as it is loaded into the DT80M or whenever the DT80M is booted. I must be missing something but I am not sure what.

Regards
Andrew

Hi I have written this program using the dex interface: CODE: SELECT ALL BEGIN"config" ' Generated by dEX Configuration Builder Version 1.84.030 (Firmware Version 9.20.8973) ' Target device: DT80LM3-4 password="" S1=30,130,590,2565 RS1S RA"BMW Running"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)1035-CV LOGONA 1TK("T1~degC",=1001CV,LM,NA) 1*TK("T2~degC",=1004CV,LM,NA) 2TK("T3~degC",=1007CV,LM,NA) 2*TK("T4~degC",=1010CV,LM,NA) 4*V("PT1Scaled~bar",=1033CV,LM,S1,NA,GL3V) 4V("PT2Scaled~bar",=1034CV,LM,S1,NA) 4*V("PT1~mV",=1013CV,W,NA,GL3V) 4V("PT2~mV",=1014CV,W,NA) ' User defined RA1S 1HSC(=1CV,R,RS,W); CALC("Speed~kph",=1032CV,LM)=1CV/25 1DS("ReadASwitch_7~",=1035CV,LM) 1C("LowSpeedCounter_8~",=1036CV,LM,1000) END The schedule should start when the "1DS" channel switch changes from 1 to 0, however the schedule starts as soon as it is loaded into the DT80M or whenever the DT80M is booted. I must be missing something but I am not sure what. Regards Andrew

Good afternoon Andrew
First thing you should do is remove the schedule definition in your user channel.
The code RA1S in the user code will redefine the schedule definition

Cheers

Roger

Good afternoon Andrew First thing you should do is remove the schedule definition in your user channel. The code RA1S in the user code will redefine the schedule definition Cheers Roger

Hi Roger

Thank you, I'll take your suggestion and give it a try.

I have another question you might be able to help with, is it possible to stop the "click" every time data is logged? It's very irritating.

Regards
Andrew

Hi Roger Thank you, I'll take your suggestion and give it a try. I have another question you might be able to help with, is it possible to stop the "click" every time data is logged? It's very irritating. Regards Andrew

Hi

Roger's suggestion works but not how I want it to work. The 1D channel is pulled down when the brake pedal in a test vehicle is activated and the schedule is initiated. However only one row of data is recorded. I want to log data for the whole time that the braked pedal is pressed. Unfortunately I cannot see how to do this, has anyone got a suggestion?

Regards
Andrew

Hi Roger's suggestion works but not how I want it to work. The 1D channel is pulled down when the brake pedal in a test vehicle is activated and the schedule is initiated. However only one row of data is recorded. I want to log data for the whole time that the braked pedal is pressed. Unfortunately I cannot see how to do this, has anyone got a suggestion? Regards Andrew

Hi Andrew,

You have several inconsistency in the program.
The first one is about schedule A duplication (which Roger has pointed that out).

RA"BMW Running"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)1035-CV
....
' User defined
RA1S 1HSC(=1CV,R,RS,W);

The second one is related to trigger condition, your code will allow one trigger only.
You must have 2 setting: one is trigger time and the other is trigger condition.
Trigger condition will enable trigger time to run.
You want to use digital state 1 to trigger schedule A, in which schedule A also has reading interval (i.e.: 1s)
So it must be a while schedule:
RA"BMW Running"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)1S:1035-CV

The third one is related to digital state itself, it is more to suggestion :D
Your method can work
RA"BMW Running"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)1S:1035-CV
....
1DS("ReadASwitch_7~",=1035CV,LM)

But you may also use the following method (in case you do not need to log 1DS).
RA"BMW Running"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)1S1-W

Best regards,
Rudy Gunawan

Hi Andrew, You have several inconsistency in the program. The first one is about schedule A duplication (which Roger has pointed that out). RA"BMW Running"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)1035-CV .... ' User defined RA1S 1HSC(=1CV,R,RS,W); The second one is related to trigger condition, your code will allow one trigger only. You must have 2 setting: one is trigger time and the other is trigger condition. Trigger condition will enable trigger time to run. You want to use digital state 1 to trigger schedule A, in which schedule A also has reading interval (i.e.: 1s) So it must be a while schedule: RA"BMW Running"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)1S:1035-CV The third one is related to digital state itself, it is more to suggestion :D Your method can work RA"BMW Running"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)1S:1035-CV .... 1DS("ReadASwitch_7~",=1035CV,LM) But you may also use the following method (in case you do not need to log 1DS). RA"BMW Running"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)1S1-W Best regards, Rudy Gunawan
23
4
3
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft