Peter A. Bigot

Thanks for the kudos. PyXB is a mature project with little refactoring likely to happen. I'll leave this open so others interested in your script can find it, but it's...

I also see that with Python 3.8.5. Presumably some internals have changed and PyXB's way of extending built-in types no longer works. https://github.com/renalreg/PyXB-X may be your way forward; it explains...

Odd. I don't use or test under windows, but AFAIK people have been using it there for quite a few years. In any case I can't do anything about this,...

This is almost certainly #32 and you're using an old version of PyXB. With the current `next` branch the generation for `not_correct.xml` includes the necessary tag to identify the content...

Updated with a couple more features, specifically more display of persisted configurations and most importantly timestamp of data sent over USB or bluetooth (critical in cases where the sample rate...

Further investigation confirms that accurate results for the first 30 minutes after startup are because the persisted BASELINE isn't installed until that interval has passed, and that the persisted values...

I have data from a subsequent 4 day run that shows the same extreme fluctuations. I suspect it's because the baseline calibration is completely wrong. I will try to the...

Thanks. I have a JLink Plus with the appropriate cable and will use that to just rewrite the 2.1.0 firmware with an intervening `--eraseall` which should clear the configuration.

Attached are overview and detail images from a second run with four units, all of which underwent `nrfjprog --eraseall` followed by a flash of `thingy_v2.1.0.HW_1.0.hex` downloaded from the product page....

Adding temperature compensation is certainly worth investigating, but I'm not convinced it's going to explain or solve everything: * The data in my comment from 2018-01-06 was collected with all...