Cumulus Support

Hi,
Have spent the last few days playing with 1.91 beta.
Love all the new features especially the new humidity webtags.
Everything runs smoothly and no problems along side the Toolbox.

I do have 1 glitch alas and this is concerning the graphs. They upload fine but they are not processing (updated) at all.

I tried deleting all in local folder but then I just dont have any graphs at all. So I put them back manually.
I tried deleting them on my server but still graphs are not the latest conditions.

I have worked out though if I view the graphs from the Cumulus Toolbar: View - Graphs
this will update them. But then they do not update (process) again, unless I go back to Cumulus Toolbar and View - Graphs.
Then they will process (update)

They upload is fine, no problems there, but Cumulus is just uploading the same old graphs that have not been updated.

I have installed the new beta version on 2 computers and both are doing the same.

If anyone has any ideas concerning this I would appreciate any help.
I have reverted back to previous version but would love to use 1.91 with all the new great features.
Many thanks
Jen

It's probably getting an error while creating one of the images; but I don't know why viewing the graphs would fix that. If you zip up the diags folder and attach it, I'll see if there's anything relevant in there. Also turn on the debug log and attach that a few minutes after an upload should have occurred.

Many thanks for your help.
I have not viewed the Graphs from the Cumulus Panel since yesterday and now the Graphs showing online are a day out.

But no hurry as I am using 1.91 on a different computer for testing and then revert back to the nice stable 1.90

I attach files as requested.
Many thanks

Cheers
Jenny

It's as I suspected; Cumulus gets an error while trying to create the files:

0124.359 : Error creating graph files: Access violation at address 0040522F in module 'cumulus.exe'. Write of address 00000000

I don't understand why viewing the graphs fixes it for the next update, nor why no-one else apparently has the same problem. Have you used the new facility to hide any of the temperature lines? Do you have the 'freezing line' option set?

Looks similar to my problem

Error creating graph files: Access violation at address 0040522F in module 'cumulus.exe'. Write of address 00000000

tks

One thing you have in common is XP SP3. But I've tried it on that and can't reproduce it.

Hi Steve,
I have the freezing line off as do not need here.
I tried disabling the different temp valves after reading one of the other posts.
I set graphs same as version 1.90.
I tried enabling all features.
I ran out of ideas and hence my posting here.
I have windows 7 but Cam does not work on this windows version.
Vista I would not touch with a barge pole
Cheers

My XP test isn't a thorough as it could be - I'm using XP mode in Windows 7, and it doesn't support USB HID devices like the Fine Offset that's connected to this PC. So it won't actually have any data to plot. I'll try a better simulation when I get chance with a TCP/IP connection to my Davis station.

I suspect this will turn out to be another bug in the new version of the charting component; there seem to be a number...

Many thanks Steve, hope you sort it out.
I love the new features.
Keep up the good work, much appreciated

I've tried this 'for real' now, and still can't get it to fail. Could you let me have your 1.9.1 cumulus.ini file, and I'll see if that helps.

Can send my "ini" if required ?

Yes, yours will do fine

Best confirm which one exactly you know what I'm like

The cumulus.ini file from your Cumulus 1.9.1 installation folder.

The good news is that with your ini file I can reproduce the problem; it does seem to be a problem with the chart component. What I can't work out is which of your settings causes the problem and why.

As a work around, try setting the 'resize' options for 'web graphs' in the internet settings. You can leave the size at 700x350. It means you lose quality on the images (because of yet another bug in the chart component!), but it stops the original problem occurring.