Troubleshooting help please: NaN errors and others

[nikkipugh]

Hi, I'm helping a friend out by soldering up a couple of kits ahead of an event next week. This is my first time working with bGeigie Nano, but I'm familiar with Arduino and some of the daughter boards used in the kit. I've not got much programming experience.

One of the kits I've assembled seems to be working okay, but the other is behaving oddly and I'd appreciate some help identifying what's going on please.

Start-up screen: bGeigie Nano 1.4.4 Battery=100%#-001 Mode = 25[unidentifiable]larm=-1CPM

Then in surface mode I get:

NAN uS/h Mx=NANuS/h Ds=NANuS alternating with 45CPM NANBq/m2 21/10 08:10:28 60s [battery indicator]

In logging mode CPM and GPS seems to be working okay (I'm getting blips and the blue LED pulses too), but also getting NAN uS/h. (Also "60s" just to the left of the graphic battery indicator, which I've yet to find a reference to in the docs and isn't present on the reference unit I've got that's running v1.3.6)

On the micro SD card, file names are being prepended with a -, eg "-0011020.log"

The content of the log files mostly looks okay except for the negative device id. header:

NEW LOG format=1.4.4nano deadtime=on

$BNRDD,-001,2021-10-20T09:01:06Z,29,3,2143,A,5403.2776,N,00246.1078,W,77.70,A,11,79*7A

Can anyone suggest what's going on? Does this seem like a software issue rather than a duff solder joint or similar?

I've been looking at what would be involved with reinstalling the firmware. There's a chance I might have a FTDI Friend around somewhere, but I'm getting a bit confused with GitHub and there not looking like there's a 1.4.4 uploader (mac)

[nikkipugh]

I've just noticed that neither of the two Nanos I have seem to be picking up the device id from SAFECAST.TXT - either displaying on the splash screens at start up or in the log files.

[hinner]

nikkipugh,

after reading your first message my thought was there is a problem with the .txt file.

Maybe you can check if this file is correctly written (ascii text editor).

All the best, Kajetan

Am 21.10.21 um 11:46 schrieb nikkipugh:

I've just noticed that neither of the two Nanos I have seem to be picking up the device id from SAFECAST.TXT - either displaying on the splash screens at start up or in the log files.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Safecast/bGeigieNanoKit/issues/64#issuecomment-948440658, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG2RNTF7FK4TWEMIGUF2MV3UH7OPLANCNFSM5GNRB7DA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[nikkipugh]

Thanks Kajetan, both the new units have config.txt like this: 9600,26,3,2,1,1,0 baud,escape,esc#,mode,verb,echo,ignoreRX

So a few extra settings compared to the docs here, but matching the older reference unit I have.

With the exception of device id, all three units have SAFECAST.TXT like this:

nm=SAFECAST did=3500 gt=0 gm=0 cpmf=334 cpmn=Cs137 bqmf=37 bqmn=Cs137 al=100 tz=9 cn=JPN st=0 ss=0 sh=100 sm=0 cw=60

[robouden]

Hi Nikki,

It seems the issue is that the safecast.txt is edited in windows and contains not visual LR/CR characters. Is it possible to post your safecast.txt?

Regards, rob

[nikkipugh]

Here you go:

3500 is the one with the more pronounced errors SAFECAST.TXT

3501 less bad SAFECAST.TXT