{"id":97555,"date":"2024-06-28T11:00:34","date_gmt":"2024-06-28T11:00:34","guid":{"rendered":"https:\/\/www.seeedstudio.com\/blog\/?p=97555"},"modified":"2024-06-28T14:58:52","modified_gmt":"2024-06-28T14:58:52","slug":"behind-the-scenes-a-simple-wifi-transmission-test-on-sensecap-watcher","status":"publish","type":"post","link":"https:\/\/www.seeedstudio.com\/blog\/2024\/06\/28\/behind-the-scenes-a-simple-wifi-transmission-test-on-sensecap-watcher\/","title":{"rendered":"#behind-the-scenes A Simple WiFi Transmission Test on SenseCAP Watcher"},"content":{"rendered":"\n

For people who might not be familiar with SenseCAP Watcher<\/a>, it’s the world’s first AI watcher to help you monitor anomalies within a space and then take actions accordingly, for spacial intelligence.<\/p>\n\n\n\n

We will be launching the Sensecap Watcher on Kickstarter in early August. Subscribe to our newsletter<\/a> to get all the latest updates and news. Before that, we not only send them off to the lab for thorough testing, but also perform some fun little tests in our office. Just like the one I want to share with you today\u2014we evaluated the WiFi FPC antenna design of this version of the SenseCAP Watcher.<\/strong><\/p>\n\n\n\n

Since the SenseCAP Watcher uses WiFi for its backhaul, and images are usually the largest data packets that need to be transmitted, we conducted an image transmission test.<\/strong><\/p>\n\n\n\n

<\/div>\n\n\n\n

How We Conducted the Test?<\/strong><\/h2>\n\n\n\n

Test Method<\/strong><\/p>\n\n\n\n

The test was pretty simple and straightforward. The Watcher captures and uploads 10 photos per second to the server. To evaluate the Watcher\u2019s performance, we monitored the transmission success rate by measuring how many photos the server and the device successfully received per second. We then moved the Watcher from a distance of less than 1 meter from the router to farther locations to observe any changes in the transmission success rate.<\/p>\n\n\n\n

Test Environment<\/strong><\/p>\n\n\n\n

Indoor:<\/strong><\/p>\n\n\n\n

Our office is a complex environment with multiple routers set up throughout the space. There are around 60 people, each with their own WiFi and BLE devices and so on, and the office has many walls and glass partitions. We conducted the test within our office<\/strong>, moving the Watcher from a location near the router (Point A) to two other meeting rooms farther away (Points B and C) to monitor changes in incoming and outgoing rates:<\/p>\n\n\n\n

<\/div>\n\n\n\n

Point B: Approximately 25 meters from the router, separated by 3 walls and 2 glass layers<\/p>\n\n\n\n

Point C: Approximately 30 meters from the router, separated by 4 walls and 3 glass layers<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

(Image 1: Layout diagram)<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

(Image 2: Our portable router)<\/p>\n\n\n\n

Outdoor:<\/strong><\/p>\n\n\n\n

For the outdoor test, we did a line-of-sight test downstairs<\/strong> to see the changes in incoming and outgoing rates when the Watcher was at different spots (Points D, E, and F):<\/p>\n\n\n\n

<\/div>\n\n\n\n

Point D: 0.6meters from the router<\/p>\n\n\n\n

Point E: 25 meters away from the router in a straight line<\/p>\n\n\n\n

Point F: 60 meters away from the router in a straight line<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

(Image 3: Layout diagram)<\/p>\n\n\n\n

The metrics we tracked:<\/strong><\/p>\n\n\n\n

Incoming Rate: The number of photos the server receives from the Watcher per second.<\/p>\n\n\n\n

Outgoing Rate: The number of photos the end device receives from the server per second.<\/p>\n\n\n\n

Transmission Path: Watcher -> Server -> End Device (e.g., phone)<\/p>\n\n\n\n

Test Result<\/strong><\/h2>\n\n\n\n

Indoor Test:<\/strong><\/p>\n\n\n\n

When placed close to Router A, the transfer rate averaged 10 fps. As we moved it farther to Point B, it maintained around 7 fps. Even at the farthest Point C, with more walls and glass, it stayed at 6 fps. Some fluctuations were observed, which is quite normal given the many other “roles” in the office.<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

(Image 4: Near the router – A)<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

(Image 5: Meeting room B)<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

(Image 6: Meeting room C)<\/p>\n\n\n\n

<\/div>\n\n\n\n

Outdoor Test:<\/strong><\/p>\n\n\n\n

The transfer rates close to the router at points D, E, and F were pretty much the same, nearly maintaining around 8fps to 9fps. As the distance increased, there were minor fluctuations likely caused by nearby cars and network variances or something else. Overall, the performance was still very satisfactory, right?<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

(Image 7: Near the router – D)<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

(Image 8: 25m away E)<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

(Image 9: 60m away F)<\/p>\n\n\n\n

Due to unexpected rain, we were unable to complete the maximum distance test. We will keep you updated on any future tests.<\/p>\n\n\n\n

How do you guys conduct WiFi tests for your product? Leave a comment\u2014we’re eager to hear your anecdotes!<\/p>\n\n\n\n

<\/div>\n\n\n\n

Easter Egg<\/strong><\/h2>\n\n\n\n

Check out how we conducted the test.<\/p>\n\n\n\n

P.S. The Watcher\u2019s screen is black because the test firmware didn\u2019t include display functions, but it was still working fine, just ignore it.<\/p>\n\n\n\n

\n