×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Weather radio don't want connect

  • Posts: 50
  • Thank you received: 2
Do you can to try the NAT. if Ok you will know ;)
In my tinker, same local, I had must to open port!
3 years 8 months ago #57167

Please Log in or Create an account to join the conversation.

  • Posts: 50
  • Thank you received: 2
Explication for my tinker: Apache2 is on the port 80.
if you go on the web and put RL:
http://ip_local
you must to see the apache2 webpage.
if you test from another PC what do you see?
3 years 8 months ago #57168

Please Log in or Create an account to join the conversation.

  • Posts: 294
  • Thank you received: 54
On the weather radio machine, if I put http://localhost in the browser, I get the apache2 webpage, as you mention. On another local machine, http://ipaddress gives me the Stellar Mate Dashboard. I thus assume that Stellar Mate redirects port 80 to another port if accessed from outside. If I can figure out how to disable Dashboard this may solve the issue.

I will try to figure it out.

Merci.
3 years 8 months ago #57173

Please Log in or Create an account to join the conversation.

  • Posts: 50
  • Thank you received: 2
OK.... I had have the same pb with the nafabox project!
So, I had must to uninstall ngnix & apache2, then I had reinstalled apache2 and after it was ok!
3 years 8 months ago #57175

Please Log in or Create an account to join the conversation.

  • Posts: 294
  • Thank you received: 54
Uninstalled and re-installed apache2 but no change. I will ask the Stellar Mate forum if there may be conflicts between the Dashboard and apache2.
3 years 8 months ago #57177

Please Log in or Create an account to join the conversation.

  • Posts: 50
  • Thank you received: 2
do you have ngnix installed?
3 years 8 months ago #57178

Please Log in or Create an account to join the conversation.

  • Posts: 294
  • Thank you received: 54
No ngnix on Stellarmate, so it is not part of the problem.
3 years 8 months ago #57182

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
Just a thought: is a StellarMate device really the right place running the weather radio web server? Or do you have your StellarMate running 24x7 - which should be the typical mode for a web server of a meteo station?
3 years 8 months ago #57271

Please Log in or Create an account to join the conversation.

  • Posts: 183
  • Thank you received: 23
so glad you asked the question, it's not clear from the install docs that I should be adding an additional RPi *just* for the web server to not?

to your earlier discussion with @knro in another thread, I feel like the Observatory control systems should be independent from the Telescope/imaging control system, much like Viking and Voyager do - which implies, ideally, two RPis, one of which could host WeatherRadio, Indiunio/relay control, sensors, etc and the other that manages image acquisition.

sorry - this is a thread hi-jack topic, - if worth talking about we should move to another thread. Speaking of which, I will suggest to the web admin team that we should have a section for DIY/Open-source hardware that's INDI compatible as some of these topics are really not INDI per se but related.
3 years 8 months ago #57272

Please Log in or Create an account to join the conversation.

  • Posts: 294
  • Thank you received: 54
I had the StellarMate already available so I configured it to control my observatory. But you are right, I will re-install everything on a non-StellarMate machine and see where it gets me.
3 years 8 months ago #57286

Please Log in or Create an account to join the conversation.

  • Posts: 294
  • Thank you received: 54
The way I am configuring/controling my setup is to have an RPi or similar (Odroid XU4) to control the observatory (roof/dome, weather, watchdog, flip flat), and an Odroid on the telescope, to control the mount and instrumentation. Everything being controlled remotely from a laptop or PC. I am far from being ready but I am getting there slowly, indiserver scripts are working, everything connects, had some issues between roof and dome parking but scheduler and watchdog should sort all that up, etc... Will keep you posted.
3 years 8 months ago #57287

Please Log in or Create an account to join the conversation.

  • Posts: 183
  • Thank you received: 23
Started work on the RG-11 implementation after my device arrived today - starting with the firmware before moving onto the drivers. It seems that for our purposes we don't really need a rain bucket - we simply need to know if it's raining and a monostable output once rain is detected to stop the switch bouncing which the RG-11 does nicely - the only catch is that it like to see 12V.

Now I am *NOT* a programmer and literally learned all I know about Arduino in the last 5 days so bear with me - I've implemented most of the changes in rg11.h which is now producing JSON output which is a start - BUT I am not having a lot fo luck reading gate pins on the HUZZAH Feather I am using.

The problem is that it's not detecting me pulling the pin to ground OR me pulling it high - the few times is has changed state I can't work out why. Wondering if anyone can shed some light.

---- rg11.h ----
// RG11 state (closed = raining, open = dry)
struct {
bool status;
bool isRain;
} RainData;

volatile int current = 0;
volatile int last = 0;

void reset(unsigned long time) {
current = 0;
}

void initRG11() {
pinMode(RG11_PIN, INPUT_PULLUP);
RainData.status = true;
reset(millis());
}

void readRain() {
// grab the current state of the button.
// we have to flip the logic because we are
// using INPUT_PULLUP.
RainData.status = true;

current=0;

if(digitalRead(RG11_PIN) != HIGH)
current = 0;
else
current = 1;

RainData.isRain = current;

reset(millis());
}

void serializeRain(JsonDocument &doc) {

JsonObject data = doc.createNestedObject("RG-11");
data["init"] = RainData.status;

if (RainData.status) {
data["Rain"] = RainData.isRain;
}
}
"
3 years 7 months ago #57436

Please Log in or Create an account to join the conversation.

Time to create page: 0.867 seconds