Cumulus Support

Posted: **Mon 15 Jan 2018 1:13 am**

I have a Maplin Fine offset clone running for the last 6 years.

End of last year upgraded to 10, and Cumulus MX no problems.

Been running happy ever since.

Until 5th Jan (Approx) when it stopped updating the web / twitter feeds.

Checked the MXDiag log, and it seems to be a problem reading the pressure offset.

Played about with the USB socket it was in and got it going again. (PnP picked up the USB input device)
Machine rebooted and now no matter what I do it wouldn't read.

Installed MX on a laptop and it works fine, so hardware/cables ok.

Only difference I can find is on the laptop the hidclass/hidparse/hidusb.sys files have a different version number.
10.0.1503.0 rather than 10.0.16299.15 on the none working pc.

Is it possible that the driver has changed due to an update (there were 2 at that time, which I've uninstalled) and now it doesn't read the console correctly.

extract from MXdiag file

2018-01-15 01:05:25.540 Stream opened
2018-01-15 01:05:25.540 Reading pressure offset
2018-01-15 01:05:25.703 Rel pressure = 2648.4
2018-01-15 01:05:25.703 Abs pressure = 978.8
2018-01-15 01:05:25.703 Offset = 1669.6
2018-01-15 01:05:48.073 Ignoring bad data: pressure = 2648.5
2018-01-15 01:05:48.073 offset = 0
2018-01-15 01:05:58.075 Ignoring bad data: pressure = 2648.5
2018-01-15 01:05:58.075 offset = 0
2018-01-15 01:06:08.077 Ignoring bad data: pressure = 2648.5
2018-01-15 01:06:08.077 offset = 0
2018-01-15 01:06:28.092 Ignoring bad data: pressure = 2648.4
2018-01-15 01:06:28.092 offset = 0
2018-01-15 01:06:38.109 Ignoring bad data: pressure = 2648.4
2018-01-15 01:06:38.109 offset = 0
2018-01-15 01:06:48.105 Ignoring bad data: pressure = 2648.4
2018-01-15 01:06:48.107 offset = 0
2018-01-15 01:06:58.123 Ignoring bad data: pressure = 2648.4
2018-01-15 01:06:58.123 offset = 0
2018-01-15 01:07:00.100 *** Data input appears to have stopped
2018-01-15 01:07:18.130 Ignoring bad data: pressure = 2648.3
2018-01-15 01:07:18.130 offset = 0
2018-01-15 01:07:28.127 Ignoring bad data: pressure = 2648.3
2018-01-15 01:07:28.127 offset = 0
2018-01-15 01:07:38.134 Ignoring bad data: pressure = 2648.3
2018-01-15 01:07:38.134 offset = 0
2018-01-15 01:07:48.151 Ignoring bad data: pressure = 2648.3
2018-01-15 01:07:48.151 offset = 0
2018-01-15 01:07:58.159 Ignoring bad data: pressure = 2648.3

Posted: **Mon 15 Jan 2018 7:41 am**

have you tried a different USB socket, or resetting your console?

or rollback the update if you really think this is the issue.

Posted: **Mon 15 Jan 2018 8:55 am**

Tried all the sockets, and also a usb hub.

Reset the console, but it works on another machine, using the different version of the driver files.

Uninstall the updates, but this did nothing.
Tried a systems restore, but this failed because of an AV issue.

Posted: **Mon 15 Jan 2018 10:31 am**

ken555 wrote:Tried all the sockets, and also a usb hub.

Reset the console, but it works on another machine, using the different version of the driver files.

Uninstall the updates, but this did nothing.
Tried a systems restore, but this failed because of an AV issue.

the only other thing I can suggest is when you see the driver being installed in device manager try to rollback if it gives you the option..

https://www.lifewire.com/how-to-roll-ba ... ws-2619217

Posted: **Mon 15 Jan 2018 11:17 am**

No rollback available.

The Laptop has just done an update, so I will check if it still works when I get home tonight.

But plan is to turn off Driver signing and use the files from the laptop along with the .inf file to install that as a driver.

If that doesn't work, I may boot it off a Linux disk and try replacing the three files that way.

Posted: **Mon 15 Jan 2018 10:32 pm**

Sorry to be pessimistic, but you will find quite a few threads where Fine Offset consoles suddenly get massive pressure offsets after a restart. Try changing drivers but I don't think it will make any difference.

Once they get in that state there doesn't seem to be any going back. When mine did it I had to put the offset correction into the cumulus.ini file, Cumulus then worked ok. The required offset was too big for the console to accept though, so the pressure never showed correctly on the console thereafter.

My assumption is that a calibration setting stored in the console gets corrupted.

Posted: **Tue 16 Jan 2018 8:50 am**

But that wouldn't explain why it works on another PC.

Anyway replacing the driver seems to have worked, I'm switched off driver updates and we will see how long that stays.
But at least I have a solution if it happens again.

Posted: **Tue 16 Jan 2018 9:43 am**

ken555 wrote:But that wouldn't explain why it works on another PC.

Ah, sorry, I missed that bit of info.

Posted: **Sun 13 Jan 2019 8:52 pm**

I had the same issue with ignoring bad data caused by a very high Rel Pressure value over months. And today I found the reason for it. And I fixed it by adjusting one line in the source code of the project. I will posting an issue for it at github.
It seems that a unused bit is set by the Fine Offset. And this bit is never cleared, even not after resetting the console. So this is absolutely no driver issue.

Posted: **Mon 14 Jan 2019 9:29 am**

Would it be possible to send me a copy of your modified edition so I can try it.

The problem shows now and then, and it's normally fixed by replacing the files as above.

Posted: **Mon 14 Jan 2019 5:16 pm**

ken555 wrote: ↑Mon 14 Jan 2019 9:29 am Would it be possible to send me a copy of your modified edition so I can try it.

The problem shows now and then, and it's normally fixed by replacing the files as above.

Sure. I sent it to you as PM.

Cumulus Support

Windows 10 Drivers Problems

Windows 10 Drivers Problems

Re: Windows 10 Drivers Problems

Re: Windows 10 Drivers Problems

Re: Windows 10 Drivers Problems

Re: Windows 10 Drivers Problems

Re: Windows 10 Drivers Problems

Re: Windows 10 Drivers Problems

Re: Windows 10 Drivers Problems

Re: Windows 10 Drivers Problems

Re: Windows 10 Drivers Problems

Re: Windows 10 Drivers Problems