dang, just realized, Trident's schedule config is the same old output configs with OSC. For example, in my apex, the did (device ID I guess) of trident tests (alk, ca, mg) is 3_3, and alk test is 3_4. So from the path http://apex.local/rest/config/oconf/3_4 I can see the config of it as
And there is our familiar OSC code
To modify the schedule, it's just a
Code:
{
ID: "16",
did: "3_4",
type: "selector",
ctype: "Advanced",
gid: "",
gtype: "0",
name: "Alk_3_4",
icon: "Up/Down Arrows",
prog: "OSC 360:00/001:00/359:00 Then ON ",
log: false,
extra: { }
}
OSC 360:00/001:00/359:00 Then ON
, which means run it for one minutes then stop for 359 minutes, which is every 6 hours. It's also offset by 6 hour to space out from the trident test. Also I found that if I try to start the test when a test is running, like I started the ALK test manually, then I want to start all test, the command is accepted but ignored. That's the behavior for this ALK schedule to work.To modify the schedule, it's just a
PUT
to that same path, using the same body with an updated OSC configuration. I verified that by changing from 4 tests a day to 6 tests a day and back, those were the exact calls the webapp was making.
Last edited: