X4M200 problem with detecting breath in XeTruExplorer Windows 10

Discussion in 'Respiration Sensor' started by sten, Apr 8, 2019.

  1. sten

    sten New Member

    Hi,

    I using XeThruExplorer(windows 10) connected to X4M200 over USB to laptop (i7-7700HW + GTX 1060). Device have actual firmware 1.6.8 (updated from older firmware). On PCB i found this numbers to help identify specific board (290056-010; STM-5 94V-0 3217;10000018805 000167-007).

    I use Respiration_2 (tried other with similar result) profile with default configuration(in same case i limit distance to 0.4-2m) and i have problem with respiration detection. Device is unable detect consistently respiration. In best case scenario i manage get about 60s "Breathing" other 60s "Movement *". It is really different result than expected from your product video.

    When initialization was in-progress, all moving object were removed from detection zone in-front of PCB (this is mentioned in video, but i didn't find any information about this in other document).

    I tried in multiple environment with same result, all without any object between test subject and PCB.
    PCB pointer on test subject with side with RX a TX antenna. I try room without other test subjects and room with multiple test subject, result are about same.
    Distance between PCB and test subject is about 1m, XeThruExplorer confirm this distance.
    Test subject awareness about measuring respiration didn't have any noticeable impact on result.
    Test were conducted with test subject sitting on chair and working with PC or lying on couch.

    I also notice high CPU a GPU usage when XeThruExplorer doing Initializing (CPU +-35%, GPU 60%), after completing initialization utilization to half. It still seem too high for me, it should be simple GUI application, displaying value from device or do you get raw data from device and doing data analyzing inside XeThruExplorer?

    Screenshot from XeThruExplorer (both screenshot were captured in independent test session with their own initialization):
    Best case:
    https://ibb.co/L1y9HbJ

    Worst case:
    https://ibb.co/zRR1WtG

    Do you have any advice how to get reliable respiration data, or how verify PCB isn't faulty (PCB isn't visibly damaged)?

    Thanks.
     
  2. BenChong

    BenChong New Member

    I have same issue on my X4M200 too. It was connected to Win10 through USB to my laptop and we tried many time on different people and different environment, the result is so poor that we think it is unusable and have huge different compared to video demo. In short, it's initialization process is too....long and it is very hard to detect continuous respiration pattern (pattern lose with some minor movement). so please let us know what can we do to improve this. Thanks!