I've been working on this DT80m we got from a third party for a while now. It's been a massive headache already and has had to go back numerous times for hardware issues & the suppliers have been somewhat less than helpful; but I'm just about at the stage where we can get the thing programmed and running.
To that end, could someone please explain to me the function of the code the unit has shipped to us with? Thanks.
1SERIAL(",%f[1CV],%2f[2CV]%f[3CV],%1s['N','S',51CV=-1],%3f[4CV]%f[5CV],%1s['E','W',52CV=-1],%f[6CV],%f[7CV],%f[8CV],%f[9CV],M,%f[10CV],M,%f[11CV]",W)
'1SERIAL("$GPVTG,%f[12CV],T,%f[13CV],M,%f[14CV],N,%f[15CV],K",W)
In other news, the datalogger will need to run autonomously at high speed for extended periods of time, however we'd also like to get some feedback either
A) Once every (X hours)
or
B) When an alarm triggers (temperature > Y, for example).
Naturally, whilst logging data the unit has no spare CPU to utilize the modem and so commands simply do not go through.
I've looked at some examples on these forums regarding running schedules for set periods of time & then switching to a second schedule, sending data and then switching back. For some peculiar reason I cannot seem to get the original schedule (logging data) to begin running again.
I've also found with schedules which appear to be set to trigger "Only if channel variable is in specified state" seem to just be triggering constantly, rendering this route unusable. Anyone got any bright ideas how to go about this? I'm setting up the whole thing using dEX.
I've been working on this DT80m we got from a third party for a while now. It's been a massive headache already and has had to go back numerous times for hardware issues & the suppliers have been somewhat less than helpful; but I'm just about at the stage where we can get the thing programmed and running.
To that end, could someone please explain to me the function of the code the unit has shipped to us with? Thanks.
1SERIAL(",%f[1CV],%2f[2CV]%f[3CV],%1s['N','S',51CV=-1],%3f[4CV]%f[5CV],%1s['E','W',52CV=-1],%f[6CV],%f[7CV],%f[8CV],%f[9CV],M,%f[10CV],M,%f[11CV]*",W)
'1SERIAL("$GPVTG,%f[12CV],T,%f[13CV],M,%f[14CV],N,%f[15CV],K*",W)
In other news, the datalogger will need to run autonomously at high speed for extended periods of time, however we'd also like to get some feedback either
A) Once every (X hours)
or
B) When an alarm triggers (temperature > Y, for example).
Naturally, whilst logging data the unit has no spare CPU to utilize the modem and so commands simply do not go through.
I've looked at some examples on these forums regarding running schedules for set periods of time & then switching to a second schedule, sending data and then switching back. For some peculiar reason I cannot seem to get the original schedule (logging data) to begin running again.
I've also found with schedules which appear to be set to trigger "Only if channel variable is in specified state" seem to just be triggering constantly, rendering this route unusable. Anyone got any bright ideas how to go about this? I'm setting up the whole thing using dEX.