Archive by Author

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 35 total)
  • Author
    Posts
  • in reply to: Extra log header in the log – what do they mean? #19244

    GregS
    Participant

    Thanks Richard – yes – that other thread is indeed pertinent. James has been helping me off line with this (because I contacted him off line), but he had not yet explained what the 460 field means – I see that this is answered in that other thread – thanks.

  • in reply to: How to get new features in the app / Bounty #19243

    GregS
    Participant

    @richard: There is a post from James somewhere here explaining that there is essentially no memory left, and any change at all is a huge task for him, because often, he has to make changes in areas of code that are unrelated to the actual change being made, simply to fit the code in. @james: can you provide a link to this post?

    Regarding being “specific” – I’m talking in general – sorry about that.

  • in reply to: How to get new features in the app / Bounty #19223

    GregS
    Participant

    Far more important is a V2 of the hardware, with more memory so that there is room to add features and fix bugs, IMHO.

  • in reply to: Initialization failed:status 1 #19221

    GregS
    Participant

    I’ve just had the same error (“initialization failed”). I tried connecting lots of times, and also tried rebooting my phone, to no avail. When I pulled a battery out of the meter and re-inserted it, it then worked the very first time. I’ll try that beta version of the app.
    I’m on Android 7.0

    • This reply was modified 1 year, 9 months ago by  GregS.
    • in reply to: Initialization failed:status 1 #19238

      GregS
      Participant

      The problem happened again, but this time removing and replacing a battery didn’t work. The beta app is working – thanks. Note that sometimes the app takes quite a long time to connect, but it always connects.

  • in reply to: Logging rate much slower than configured #15428

    GregS
    Participant

    You’re welcome. Btw, regarding logging single samples, maybe a mid-way solution would be to allow us to save a single buffer’s worth of samples to the SD card, as part of the graphing functionality? I.e – you allow us to access single samples in graphing mode, so consider going one step further and allowing just 1 raw buffer to be saved to the log. (apologies in advance if it can already do this – I haven’t used graphing mode much yet so am unfamiliar with all the options, but I can’t *seem* to see a way to do this)

  • in reply to: Trouble connecting (Android) #15427

    GregS
    Participant

    Ok thanks. It’s not so bad that it’s unusable – I’ll live with it, and it’s good that things are improving over time.

  • in reply to: Logging rate much slower than configured #15422

    GregS
    Participant

    Thanks James.
    @2000Hz/32: Actual: ~20 records/s Theoretical max: 62.5
    @1000Hz/32: Actual: ~14 records/s Theoretical max: 31.25

  • in reply to: Logging rate much slower than configured #15415

    GregS
    Participant

    Ville: It’s really very simple. I asked what the maximum log rate was, and I got an answer from James himself:
    moosh.im/f/topic/measuring-watt-hours/#post-15307 (including the entire link causes an ugly big graphic to cover up the rest of the message – trying a truncated link instead….)
    If you set the buffer depth to 32 and sample rate to 4000Hz, then leave it to log, you’ll see a sample rate of just under 125Hz in the log. Is that what you’re looking for?

    I’ve tested it, and so far, I am unable to reproduce that rate, so I am reporting this discrepancy. I am only trying to reproduce HALF that rate, by the way, so I’m even being nice. ;^)

    • This reply was modified 2 years, 7 months ago by  GregS.
    • This reply was modified 2 years, 7 months ago by  GregS.
    • This reply was modified 2 years, 7 months ago by  GregS.
  • in reply to: Logging rate much slower than configured #15412

    GregS
    Participant

    Tried again with Class 10 – no improvement whatsoever.

  • in reply to: Logging rate much slower than configured #15406

    GregS
    Participant

    I notice that the logging rate increases when I disconnect the phone from the meter – down to about 66ms now, which is a big improvement, but still nowhere near what it should be at 4000/64 – 16ms. Still using Class 4.

    Is this the expected behaviour – the logging rate improves when the phone is disconnected?

    In any case, it proves that the SD card is not the only bottleneck when the phone is connected.

  • in reply to: Logging rate much slower than configured #15405

    GregS
    Participant

    Ok I guess I’ll try a faster card. How fast does it need to be in order to sustain a rate of one worse-case (longest) record every 8ms? (I’m using 125Hz/8ms here because that’s the fastest rate you seemed to say the meter should be able to keep up with – actually you seemed to imply it could go even faster) Suggestion: this seems to be fundamental information and should be added to the Wiki.

  • in reply to: How to close a log and start a new log file? #15403

    GregS
    Participant

    Thanks James. Yes, that’s what I do – only remove the bottom half. That still causes the PCB to flex, IMHO.

  • in reply to: Trouble connecting (Android) #15398

    GregS
    Participant

    I’ve noticed a behaviour which seems questionable. It’s not causing any obvious problems (and I’m still able to connect every time), but I’m reporting just to be thorough:
    Steps to reproduce:

    1. Place the meter close to the phone.
    2. Ensure BT is enabled.
    3. Stop the app completely by going into the Application Manager and doing a “Force Stop”.
    4. Start the app, and wait for the meter to appear. Do NOT connect to the meter.
    5. Tap “Scan”, and observe the RSSI value, which is probably moving around a bit.
    6. After a few seconds, the scan should complete, and the RSSI value should be steady.
    7. Holding the phone, move a bit further away from the meter.
    8. Tap “Scan” again. The RSSI value should be lower, and again, will probably be changing values a bit during the scan. The scan should complete again after a few seconds, and the RSSI value should again be steady.
    9. Connect to the meter.
    10. Tap the “back” button in the app (top left hand corner) to display the list of meters again.
    11. Just after tapping “back”, observe that the “Scan” button is greyed out, and the word “Scanning” appears just above the button, also greyed out.
    12. After a few seconds, the “Scan” button is enabled (suggesting that the scan has completed), BUT, the word “Scanning” persists, although it is no longer greyed out. Is this behaviour normal/expected?
    13. Now, still on the scan screen, and still with the meter connected, tap the “Scan” button. The RSSI value should change values a bit, and stabilise after a few seconds, at which point the “Scan” button is re-enabled. Move around a bit, and repeat, to observe that the RSSI value changes depending on your position relative to the meter.
    14. Now disconnect the meter, by tapping the “disconnect” icon to the right of the meter information. (the two plugs).
    15. Tap “Scan” again. This time, you should observe that the RSSI value does NOT change at all. It doesn’t matter how close or far away from the meter you are – the value does not change. Repeat as many times as you like – it never changes. This behaviour does not match the behaviour when the app is first started. When the app is first started, with the meter disconnected, the RSSI value DOES update each time the “Scan” button is tapped. Also observe that the word “Scanning…” persists throughout this last step, as if some process has locke
      d up.

    Now, despite the above, when I again tap on the meter, it does actually connect successfully.

  • in reply to: How to close a log and start a new log file? #15397

    GregS
    Participant

    Apologies – I am mistaken – it’s working properly. The reason I have multiple headers in my log is simply that I changed the log settings without stopping & restarting logging, so this behaviour is exactly how I would want it to work! :) I have done some more testing and it’s all working fine.

Viewing 15 posts - 1 through 15 (of 35 total)