scotty38

yep that's fine.

Just to add it shows as dynamic as you have basically fudged a static but the dhcp server doesn't really know it's a static.

As I mentioned the downside to doing it this way is that the DHCP server in your router "could" assign that same address to a different device and then you'd have a conflict. On a small home network and the address "out of the way" it's a good shout that it'll all be fine.

I used a pet heater pad on mine when it was left outdoors too, worked a treat

18 minutes ago, newbie alert said:

I've never used it, but I can't get my head around why there's so many stupid names, is it to make it sound technical , to make a simple task sound complicated... 

Come on  please, there's enough unnecessary jumping on the "let's bash pixinsight" train as it is without admitting it's never been used but it's still rubbish 😀

Each to their own whether they like PI or not but I've never quite understood the resistance to its cost. Given processing could be argued to be 50% of the game it's not a lot compared with the acquisition side 🙂

Yes I know you can get cheaper/free but you get my point

no worries

I know a typo but 194.168 for both

yes and yes

yep

Different addresses for eth and wireless.

From what I've seen your router is 192.168.0.1 and subnet mask is 255.255.255.0

That's the "network" essentially, don't worry about that one.

mac address won't change, unless you change it on purpose but generally that's not done

yes configure your mele to use a static address similar to what I mentioned plus you will then also need to set up the DNS entries.

Right click the network icon in the system tray and go into settings. This might look different depending on win 10/win 11 but then pick the adapter and click Edit and go from there. Should be self explanatory....

arp -a will just give you a list of addresses in use basically

Yes adapter is referring to your network "card" in the mele

Go into the network settings for your adapter (I'm assuming wireless) and you'll see the options in there. It's nothing to do with Virgin so they may not be able to help you unless you get someone keen on the end of the phone as it were. Even if they configure a static on the router you'll still need to do the pc side anyway

And set up DNS somethign similar to below, check yours now with ipconfig/all

You can ignore all the non 192 addresses. Configure your mele with 192.168.0.200 and see how you get one

Just make it static on the mele. If you're using 192.168.1.x addresses call it 192.168.1.200 and you'll be fine unless you have hundreds of devices on your network

6 minutes ago, StuartT said:

don't worry. I didn't understand any of it anyway, so I've not done anything. I'll just have to cross my fingers and hope my mini-PC connects each time (thus preventing me from having to enroll in a degree in computer engineering! 🤣)

hahaha... To be fair I just set my mele with a static address and rdp to that each time. Never had an issue......

Nice image but what do you mean about NINA and the limits? Are you saying it’s not flipping or something?

Have you plugged the 533 into a USB2 port as it may need to see USB2 before it initialises?

I'll throw a spanner in the works and suggest you look at the 533 instead although that still leaves you deciding OSC versus colour but glad I could help.

16 hours ago, Rallemikken said:

By name I recon you mean hostname. Routers don't care about hostnames, they only relate to mac-adresses or IP-adresses. Most operating systems has hostname-files, where they assign hostnames of other computers on your local network to certain IP or mac adresses. If the other computer on your LAN has the same IP as yesterday, well, then the assigned hostname will resolve. Otherwise you must provide the IP and this might (or might not) update the hostname-file on the computer you are currently sitting on.  Not all routers let you assign static IP-adresses. If not, look for a setting called "keep-alive" or something like that. Some routers put aside IP's that has disconnected, and keep them on wait until that device try to connect again. In this way you can keep a consistent IP over  time without beeing powered on al the time.

I still maintain you're making this too complcated and on a basic home network there's no need to worry about a hosts file or DNS name resolution. netBIOS should take care of it. It's a long, long time since I did this stuff and even then it was mainly Cisco networking rather than Microsoft. Ping the machine by name that you're trying to get to and then run nbtstat -c and it should be in the cache.

If my memory has been taken over by new developments then feel free to just ignore me and I'll carry on dribbling in the corner......

1 hour ago, bottletopburly said:

Probably these ones there is three , worth watching even if not a PI user .

 

 

Yes they are the ones I recall, the issue was the flats and flat darks did not match not that there was/is an inherent problem with flat darks.

I'd go for a size that will last you some time.

I have 36mm filters with my 294m but I bought at that size for when/if I buy an APS-C sized sensor. I don't think I'll be going full frame any time soon so 36mm is future proofed enough for me.