www.brultech.com

It is an access point connected through Ethernet. Maybe the "mesh" technology / protocol is causing interference.

Connect the GEM directly to the router and let us know the outcome.


=========================

The highest calling in life is to serve ones country faithfully - Teach others what can be. Do what is right and not what is popular.

Hi Taken - it is an access point but I'm sure it's compatibility issue with the open-mesh system OR I have very bad luck and tried 2 bad power supplies... My access to the GEM via the web interface is very intermittent. I did take screen prints of every GEM menu if you think they would be of value.

However I did upgrade my DashBox and was able to connect to the GEM using port 8001. I updated my packet send to Bin48-NET-Time on the GEM and the DashBox now identifies the GEM.

That's perfect glad your connected now. But to be clear you have streaming data coming into the DB now right?

Also for informational purposes only. When you try to connect to the GEM's setup web page you will notice it can take 3-5 times before the page actually loads.

I don't recall what the problem is exactly but it's not a user issue so much as a system issue in how the GEM renders the page initially.

If you use google chrome browser you will see one of several rendering issues:

Web page shows it's downloading some kind of file / link.

Web page shows jibberish streaming across.

Web page shows only half the page.

My personal experience is to make sure 115200 baud is set up. Be patient and let the page load which can take 5-30 seconds. Lastly keep clicking the refresh page while waiting 20-30 seconds between.

Now what's going on with that 1 wire?


=========================

The highest calling in life is to serve ones country faithfully - Teach others what can be. Do what is right and not what is popular.

cvachon79 wrote:Hi Taken - it is an access point but I'm sure it's compatibility issue with the open-mesh system OR I have very bad luck and tried 2 bad power supplies... My access to the GEM via the web interface is very intermittent. I did take screen prints of every GEM menu if you think they would be of value.

However I did upgrade my DashBox and was able to connect to the GEM using port 8001. I updated my packet send to Bin48-NET-Time on the GEM and the DashBox now identifies the GEM.

Are you using the WiFi-only or WiFi/Ethernet GEM?

If WiFi/Ethernet, what encryption type is it set to? We've had instances where we had to use AES but it detected it as TKIP.

Ben - I have the WiFi-only GEM. I'm using WPA2.

cvachon79 wrote:Ben - I have the WiFi-only GEM. I'm using WPA2.

Looks like the WiFi module supports up to G. Does the AP support Wireless G?