Cumulus Support

Looking further up your file, I see you have still had the USB problem with 954. I had a quick look at the problem log for the USB component, and someone else reported an exception, caused by a particular USB device being connected, so I guess this is the same problem. I don't know whether a solution will be forthcoming, it's an open source project with lots of components, and a common response is "find out what the problem is and submit a patch". And now I really must get back to work...

Steve,

Just letting you know that I have not opened Weather Station Data Logger while Cumulus is opened since I reported this error and I have not had any issues with spikes of data.

I can only assume that this is a usb data conflict between the Cumulus and Weather Station Data Logger when both applications are opened at the same time - as mentioned before, this wasn't a issue before the latest beta release.

Glen

Oh I just noticed that there has been a couple of new betas released - I'll give these a go and see what happens.

glen.day wrote:I have not opened Weather Station Data Logger while Cumulus is opened since I reported this error and I have not had any issues with spikes of data.

Do you still have the WMR200 connected, just the software not running?

Damn it, still an error when I open Cumulus when Weather Station Data Logger is open - I get the error "Invalid pointer operation.".

Yeah I have not disconnected the WMR200 I only just closed the application.

I know what will fix it - If Cumulus supported the WMR200 and was able to handle two weather stations at the one time, lol.

glen.day wrote:Damn it, still an error when I open Cumulus when Weather Station Data Logger is open - I get the error "Invalid pointer operation.".

Can you attach the cumulus.elf file, please?

Yeah I have not disconnected the WMR200 I only just closed the application.

That's strange; I can understand certain USB devices being present causing problems to the USB component, but if it's just software, then the logical assumption is that it's a problem with the other software.

I know what will fix it - If Cumulus supported the WMR200

This will happen, eventually.

and was able to handle two weather stations at the one time, lol.

This will never happen, it's just too much complication when you could just as well run two copies of Cumulus.

Yeah please find attached my .elf file.

I don't mean to sound like I'm arguing with you about the software but I have never had issues running both of these applications together for the past six months until I updated Cumulus - I haven't updated WSDL in some time.

Thank you for the letting me know that WMR200 will be supported one day and yes it would make sense to have two cumulus open at the same time.

glen.day wrote:I don't mean to sound like I'm arguing with you about the software but I have never had issues running both of these applications together for the past six months until I updated Cumulus - I haven't updated WSDL in some time.

Yes, I understand. The fact that Cumulus runs OK without the other software running isn't necessarily proof that the problem is in the other software.

But similarly, the fact that it hasn't been a problem before and only Cumulus has changed, isn't necessarily proof that the problem is in Cumulus.

According to the crash log, it's crashing at the point where it attaches the event handler for the USB 'device changed' event - none of this code has changed. I attach event handlers for all of the USB event handlers, even though for some of them I don't do anything other than log a message. I'll try removing the unnecessary event handlers in the next build, and you see if that helps. It's hard to see how this would do anything for your original data problem, though.

Thanks Steve,

Might be reading you wrong but you seem a little annoyed with my replies, please let me know if you think that I'm wasting your time. I don't mean to sound like I'm having a go at Cumulus I really enjoy using the application, as you may be aware I was one of the first users of this application and have seen it grow as well as the user base - I have also recommended your application to my friends.

All I know is that Cumulus doesn't run when WSDL is running (I'm sure this could possibly be replicated if you downloaded the application then ran Cumulus), I suppose it doesn't really worry me knowing that one day the WMR200 will be supported by Cumulus and that my main weather station is running with Cumulus at the moment.

I don't know this this issue originally caused the spikes which I initially reported I just know that I haven't had any spikes since I closed WSDL and only kept Cumulus running - I simply just wanted to report my issues to you.

I have no idea where any of that came from! I was simply conceding out that my 'assertion' (which wasn't entirely serious) that it had to be the other software wasn't valid. But similarly the fact that it was OK before doesn't necessarily mean that the problem is in Cumulus. We simply don't know where the problem is.

It seems that I can't remove the 'device changed' event handler; the USB component doesn't find the station without it...

glen.day wrote:when WSDL is running (I'm sure this could possibly be replicated if you downloaded the application then ran Cumulus),

I'm not sure that would work as I don't have a WMR200. If you disconnect the WMR200 station and run WSDL, do you still get the problem?

Thanks for the reply.

1. Started off with Cumulus and WSDL closed
2. I disconnected the WMR200
3. Ran WSDL
4. Then opened Cumulus

Cumulus opened without any issues after following the above steps, I had both applications opened at the same time.

I thought that would be the case; the problem requires WSDL to be using the USB when Cumulus starts.