X-Git-Url: http://www.average.org/gitweb/?p=pulsecounter.git;a=blobdiff_plain;f=NOTES;h=f7448374c6b0e4b96f37559e08f29ca74aa3f272;hp=ad96bac52cba921a2734e1044a638a4d543e0f21;hb=HEAD;hpb=f9f0f4d6f30df1f07ebd9f164102ca93bea13179 diff --git a/NOTES b/NOTES index ad96bac..f744837 100644 --- a/NOTES +++ b/NOTES @@ -199,3 +199,57 @@ Hypothesis about a match between Em messagas and wire messages was wrong ============================================= +Other hardware that looks more promising: + +NUCLEO-L053R8 (STM32L053R8T6) +http://www.st.com/web/en/catalog/tools/FM116/SC959/SS1532/LN1847/PF260001 +X-NUCLEO-IDB05A1 (SPBTLE-RF) +http://www.st.com/web/catalog/tools/FM146/CL2167/SC2006/LN1988/PF262191 + +=================== +Apparent hardware glitch: + +| 2015-12-28 05:48:47 | 95 | +| 2015-12-28 06:19:15 | 96 | +| 2015-12-28 06:22:01 | 97 | +| 2015-12-28 06:24:48 | 98 | +| 2015-12-28 06:27:35 | 99 | +| 2015-12-28 06:30:23 | 100 | +| 2015-12-28 06:33:10 | 101 | +| 2015-12-28 06:35:57 | 102 | +>> +| 2015-12-28 06:56:49 | 103 | +| 2015-12-28 06:56:52 | 104 | +| 2015-12-28 06:56:54 | 105 | +| 2015-12-28 06:56:56 | 106 | +| 2015-12-28 06:56:57 | 107 | +| 2015-12-28 06:56:59 | 108 | +| 2015-12-28 06:57:01 | 109 | +| 2015-12-28 06:57:02 | 110 | +<< +| 2015-12-28 09:34:24 | 111 | +| 2015-12-28 09:35:11 | 112 | +| 2015-12-28 18:53:29 | 113 | + +selected eight lines are bogus. Mechanical counter reading is less by +eight than counted by the software. Apparently triggered by high flow +of hot water (still definitely not 500 l/min high!). + +2016-02-05: +Created a binary that counts interrupts (and sometimes misses real events) +in the branch 'countjitter'. There is no jitter, actually. Bogus events +where apparently caused by conductive moist on the PCB. They stopped after +the device was enclosed in a plastic box. Before that, they coninsided +with strong flow of hot water that caused high humidity in the room. +Switched back to 'master' branch. + +Considering fully autonomous sensor based on cc3200. I want to put the +device in 'hybernation' mode but that requires saving of the state in +the SPI flash. That is only possible by writing a whole file every time +(i.e. up to ~100 times a day). Ugly. But apparently there is no other +way, as long as I want to keep real time clock running. I think that I +have to, for the thing to work properly. Alternative is keeping the +device in LPDS mode, but that consumes almost 300 uA just in standby, +leaving me with no budget for active operations. Their filesystem has +no wear levelling, and no way to append to a preexisting file, I'll have +to rewrite the whole of it every time I go to hybernate.