Hi edie,
Naturally there is no header for free format, thus you have to recreate header.
If you have a single schedule, an extra schedule can be used as header.
For example:
BEGIN
RA(ALARMS:1R)X LOGONA
DO1'"Date","Time","Volt1","Volt2","Volt3"'
RB1M LOGONB
D
T
1V
2V
3V
RC1H
DO{XB;COPYD dest=ftp://user:pass@address/ format=free sched=AB data=Y alarms=Y}
END
As you can see schedule A will run only when schedule C is due, and when it run it will get and save a single reading as alarms data. Thus within schedule C you have to define schedule A and B as data output as well as data and alarms mode for output.
In doing so you will put schedule A data (actually alarms) in front of schedule B data and act as a header. It is recommended to have header schedule before measurement schedule as the output will be easier to define.
Since you have several schedule, you can always create a conditional statement for each schedule within schedule A but you have to make sure the sequence will go flawlessly between the first FTP trigger and the next otherwise the header data will be jumbled and may appear within different schedule data.
Best regards,
Rudy Gunawan
Hi edie,
Naturally there is no header for free format, thus you have to recreate header.
If you have a single schedule, an extra schedule can be used as header.
For example:
BEGIN
RA(ALARMS:1R)X LOGONA
DO1'"Date","Time","Volt1","Volt2","Volt3"'
RB1M LOGONB
D
T
1V
2V
3V
RC1H
DO{XB;COPYD dest=ftp://user:pass@address/ format=free sched=AB data=Y alarms=Y}
END
As you can see schedule A will run only when schedule C is due, and when it run it will get and save a single reading as alarms data. Thus within schedule C you have to define schedule A and B as data output as well as data and alarms mode for output.
In doing so you will put schedule A data (actually alarms) in front of schedule B data and act as a header. It is recommended to have header schedule before measurement schedule as the output will be easier to define.
Since you have several schedule, you can always create a conditional statement for each schedule within schedule A but you have to make sure the sequence will go flawlessly between the first FTP trigger and the next otherwise the header data will be jumbled and may appear within different schedule data.
Best regards,
Rudy Gunawan