where to download

I've just put up new versions for all platforms to fix some minor bugs and it should hopefully provide better trigger / event detection, particularly for the ONavi sensors.

Hmmm. Is there a problem with 7.17? My WUs are being validated ("Completed and validated") but not receiving any credit. Not a big deal, just odd.

Oh, wait, all of my old tasks are now "Completed and validated" where before they were "inconclusive" or whatever.

Ah, perhaps we're still on the 3 day cycle. I'll see what happens tomorrow ...

Cheers,

Al.

I have noticed that the sensor is more sensitive, since the push, when I move something it goes off a little more frequently.

I also see after first boot up sensor not found.
Gary

interesting that you made changes about then. My HP computer stopped reporting about that time (sensor not found) and I have been trying to figure out why. Could it be the changes you made??? I look at the ping history and it started having troubles getting results on the 5th and then dropped out altogether on the 6th but I sure don't understand why = My problems did start right after my computer showed changing into version 7.11 from 7.6.

My WUs are being validated ("Completed and validated") but not receiving any credit.

Ah, perhaps we're still on the 3 day cycle.

I hope this version will be more stable and without bugs.
Thanks for the update
____________
jocuri

Thankyou, upgrading to 7.17 seems to have taken care of the problems - it seems to be running normally but I haven't seen the ping history yet - too soon, however the job is running like it should so I have no reason to expect that the rest won't follow thru too!

I don't know if this is connected with V7.11, but half an hour after each new WU starts, I get a small trigger. Happens every day without fail. Sample:

http://qcn.stanford.edu/sensor/result.php?resultid=1376222

"74405543 17 Sep 2012 | 19:54:03 UTC 17 Sep 2012 | 19:55:30 UTC 17 Sep 2012 | 19:51:43 UTC -12.433429 3.341025 0.048767 51.395946 -0.5067568 MagN 0.02 0 ONavi B 16-bit USB 7.17 N W32 0.2 1947.53 qcnn_027055_000001_1347911644.zip N/A"

Cheers,

Al.

No, nothing special happens then. The sensor is mounted on the concrete base of my garage, shed and workshop, about 40 feet long and 10 feet wide. Our property is detached, in a quiet cul de sac a mile away from the nearest railway line, so I can't see it being related to neighbours, traffic, or trains.

However, we are fairly close to a large amusement park, and I wonder if it might be something they do there at that time.

HOWEVER, looking at the last 4 WUs, the false triggers came 1814, 1811, 1812 and 1811 seconds after the start of the new WU. Look likes an unitialised variable to me, so the first report is incorrect :)

Is anyone else seeing the same? If not, I shall have to dig deeper!

Cheers,

Al.

So, of course, it didn't give the bogus trigger last night :)

Anyway I aborted the running WU and got a new one just to move the WU start time well away from the previous trigger time. Also gave the sensor a couple of prods a few hours later to check that it was working (it was).

See what happens. Perhaps it was a real periodic event. If so, I'm going to have to find out what was causing it!

Cheers,

Al.

Well, with the WU start time moved well away from the trigger time, it's triggered again at the same time, so it's looking to be a real event. I am totally at a loss as to what's causing it, but it'll be fun trying to find out :)

Cheers,

Al.

p.s. I'm also seeing the 'not found' report at the same time every day - Probably just never noticed it before.

WU's are been marked as validated and receiving no credit again - I guess you're fiddling with the server ;)

Cheers,

Al.

p.s. Still getting triggers at regular times, but suddenly shifted to a different time. I still have no idea why this is happening :/