So now trying to setup a Xenon to then be active with the Particle Featherwing. Loaded the App, scanned the code, found the mesh, put my Argon in blinking blue mode (3 s mode button). Could not connect.
Tried again, with the both in blinking blue. Could not find the mesh. Pulled the Argon plug and retry. Now it finds the mesh, scan the Argon and can’t pair with the Xenon… Since this was the Xenon that I setup with the Featherwing, perhaps I should try to work with a Xenon that is already setup.
Even without console confirmation for the Ethernet connection you can test it physically by just shutting down every mesh device except the Xenon in the Featherwing. If it breaths cyan without any other mesh devices nearby it must be using the Ethernet to reach the cloud Mesh.
The only negative with system thread enabled so far is that the LED’s do not flash at exactly the same time, small delay with multiple devices. The positive here is that many Xenons could have a stable Ethernet while testing other things. Once Setup I think the Ethernet Xenons will add a bit of stability, but that will take more testing.
Note: A repeater Xenon can not yet restore an endpoint xenon from either a soft reset or a complete unplug and replug. The Xenons must be completely taken back to where the Argon is. Even an Ethernet connected (non-gateway) Xenon can not presently restart an endpoint Xenon
The new (version 26) Android App trys to force your Xenon with the featherwing to be a gateway and only one gateway is allowed per mesh at the moment. The hack allows a Xenon to have the stability of the Ethernet without being a gateway. My Argon has always worked at home, but the Xenons rarely were stable for more than 30 seconds. With one stable Xenon and the Argon, my home mesh network is completely stable.
Note: No Xenons can as of yet help a flashing green (for more than a second) Xenon get back on the network, that Xenon must still be brought close to an Argon or other gateway. I hope a solution for this is coming soon as that makes the mesh network incredibly fragile and user intensive to restore connectivity.
Oh, too funny. The new found stability at home has little to do with my Xenon and the Featherwing. The new home stability is totally to do with the version 26 firmware that came out today.
WELL DONE PARTICLE. THE NEW VERSION 26 HAS MADE SOME HOME MESH NETWORKS MUCH BETTER.
Also at home getting much better range than at school. Less concrete and metal. Looks like about 80 to 100 meters, but because the breathing cyan is so stable, it is sometimes hard to tell when you have made 2 separate mesh networks or one network that communicates. I got 150 m from home with the Xenon stable but not talking to the Argon. That is why my Mesh Hello World program is so useful.
Hey @RWB looks like there is code to activate the Antenna. I will try some Antenna range measurements tomorrow
So today I tried an outside, flat, line of sight measurement , but could not get the mesh working with my cellular hotspot. See new topic.
So I had to do something at my house and got similar results to the above 230 m actually got 215 m (With the gateway Argon having both Antenna and the Xenon having the mesh antenna). About the distance of 12 residential homes in my area. (I was walking on my street, with the Argon near the road, up a slight hill.)
Found a line of sight location. Left my Antenna Xenon with battery pack on a pole Antenna Vertical and started walking with my Hotspot enabled Argon with both Antenna and of course carrying my cell phone. Got a whopping 520 m with good signal. At 550 m I lost the signal. Had to walk back to within about 150 m to reconnect. This was a beautiful, crisp cold sunny morning. Probably very different results on different days.
For my tests I have found the disconcerting issue that a repeater can not reconnect an Endpoint that has been fully rebooted (powered off) The xenon has to go back to the gateway. This is a bug, that should eventually get fixed.
thing is if it will not reconnect until you are within ~150 meter then getting transmission at any distant above that is somewhat hollow achievement even though interesting. i’m wondering if the reconnect sequence requires more current than those batteries could provide to either device or both. hopefully though it was just a fluke they would not reconnect at distance over ~150 meters.
Reconnecting is going to take time, it’s cold outside and I am quickly walking back to the Argon Gateway. Most likely the results are skewed in favor of the shorter distance. I really should walk back 20 meters then wait 2 minutes, then walk another 20 meters etc, until it connects, but as I said its cold.
If you see the maximum range as 100% and you consistently lose the connection at 120%, for an installation you are not going to put your Xenons at 100% probably more like at 75%. Note that I had reconnection at about 50% of the range, but a better number is probably 75% if I was willing to wait.
Unfortunately all these distances depend on your situation. Even in the same building the results may vary a fair bit. This might be a career for someone. A company that sets up-time as the highest priority may choose a 50% distance whereas someone who could fly a Boron equipped drone around the business once a day might go with a cheaper arrangement of the 100% distance. (You could also walk around the business with an Argon and a cell phone hotspot.)
So if a business that had a 100% distance at 33.3 m and had a lot that was 100 m x 100 m using the poor connection approach the lot could be covered with 4 Mesh devices as in the diagram. However it might need some method to reconnect devices that become unconnected.
The coverage decisions has a huge effect on the number of devices to purchase. And I am only researching a single connection between a Xenon and an Argon. The entire situation becomes much more complex with a true mesh.
Will be interesting to see what coverage is needed with actual businesses.