Richard Wesson

22 hours ago, alacant said:

Hi

Why not the SW Quattro monorail? No need to adapt anything then.

I have been searching online for this and does not appear anywhere as a sepearte irem - the results all give SW Quattro Scopes, SW crayford focusers and the TS Optics monorail. 

On 16/02/2023 at 19:46, PeterC65 said:

I bought the Player One version after much deliberation. I have mixed feelings as to whether it was the right decision, meaning there probably isn't much in it.

The passive cooling feature probably doesn't take more than a few degrees off the temperature. My camera temperature is usually not much above the ambient temperature, even when it's outside in the cold. I'm not sure what the situation would be for the ZWO version.

My main reason for choosing the Player One version was because it switches to High Conversion Gain mode at a gain of x180 rather than x250, and since Low Conversion Gain mode isn't much use I thought this would be an advantage. As it happens I mostly use a gain of x400. The gain of my camera will go up to x800, although x650 is the maximum practical gain. I've heard that the gain of the ZWO version doesn't go quite as high, so together with the higher LCG / HCG switching point, it may have a smaller usable gain range.

Another plus for the Player One model is the hexagonal shape which makes orientating the sensor very easy (not to be underestimated).

I've had need of support from Player One and they were great so I wouldn't worry about that. There are a lot more people using the ZWO version though and so you are more likely to be able to get advice.

The other thing to consider is whether you ever plan to add more of the ZWO infrastructure, as the ASIair computers will only work with ZWO cameras. I use my Player One version perfectly happily with SharpCap, but via USB.

 

Well, have gone for it and ordered the Player One Uranus which only took a week to arrive!

Coming from a DSLR, and being a newbie to asto cams (except for guiding) I am curious as to why you have chosen a gain of 400 as I thought lowest noise etc was at gain 180? Thanks. 

2 hours ago, PeterC65 said:

I bought the Player One version after much deliberation. I have mixed feelings as to whether it was the right decision, meaning there probably isn't much in it.

The passive cooling feature probably doesn't take more than a few degrees off the temperature. My camera temperature is usually not much above the ambient temperature, even when it's outside in the cold. I'm not sure what the situation would be for the ZWO version.

My main reason for choosing the Player One version was because it switches to High Conversion Gain mode at a gain of x180 rather than x250, and since Low Conversion Gain mode isn't much use I thought this would be an advantage. As it happens I mostly use a gain of x400. The gain of my camera will go up to x800, although x650 is the maximum practical gain. I've heard that the gain of the ZWO version doesn't go quite as high, so together with the higher LCG / HCG switching point, it may have a smaller usable gain range.

Another plus for the Player One model is the hexagonal shape which makes orientating the sensor very easy (not to be underestimated).

I've had need of support from Player One and they were great so I wouldn't worry about that. There are a lot more people using the ZWO version though and so you are more likely to be able to get advice.

The other thing to consider is whether you ever plan to add more of the ZWO infrastructure, as the ASIair computers will only work with ZWO cameras. I use my Player One version perfectly happily with SharpCap, but via USB.

 

Thanks for that. No plans whatsoever to use ASIAIR! Don't like the idea of being tied to one brand of hardware - find a mini pc run headless does the job well enough.

I am considering buying one of hese cameras. However, I am not sure whether to go for the ZWO offering or the Player One model. The latter boasts 'passive cooling', but I wondered if this really was a significant factor and offered better temeprature control than the ZWO offering. The pros for the ZWO are potentially lower price, and of course easier customer service as would be buying from a UK retailer!

Any thoughts would be appreciated. 

The problem with a DSLR with that scope (like many newtonians), is that there will not be sufficient inward focus for a DSLR. 

As suggested by StevieDVD here is a summary of my issue and the solution. 

The issue:

TP-link tl-wr802n portable router was used in access mode to create a wifi network without internet connection. This had previously been used with a mini-pc (ACE-PC AK2). I could then access the mini-pc in headless mode using RDP or Teamviewer, with the connection between portable router and mini pc using LAN. I purposely wanted access without innternet connectivity to be able to use it at remote sites. 

However, when I attempted this with a recently purchased second hand NUC (NUC513 MYHE), the NUC did not connect properly over LAN showing NO NETWORK. LAN was working as evidenced by ability to access log in page of router and ability to connect to home router which was connected to internet. 

My solution

• Ensure that Remote Desktop is enabled
• Connect wirelessly from the NUC to the portable router.
• Doing the latter now shows the NUC as connected to the portable router via LAN and it is possible to connect to the NUC using RDP via the network created by the poetable router without an internet connection necessary. 

6 hours ago, StevieDvd said:

Sorry if my post seemed to imply anything unintended. It was just to emphasise that permissions were needed on the NUC and you may have been helped by another astro friend last time and missed a step out on the NUC.

Reading the AC750 leaflet it says the network port is set for a WAN connection to another router when set in Access Point mode (switch set to AP/Rng Ext/Client).

So does having both NUC/Laptop connected via wifi to the min router now work? If you want the NUC connected via ethernet cable the mode may need to be changed.

No problem at all. I have reinstalled windows as their seem to be an issue with credentials singing in via RDP - it kept telling me password not recognised and showing login as  'other user'. I am now pleased to say that I can now control the NUC from laptop via the mini-router with no internet connectivity required. 

Thank you everybody for your help!

13 minutes ago, StevieDvd said:

I think you need to install a TeamViewer app on the Nuc to let TeamViewer connections. That's why I was suggesting using RDC, as the client is on basic Window OS but the Remote Desktop is only on Pro version and has to be enabled.  If you set up the old mini pc did you or someone else add TeamViewer to it? It's one of the things scammers get victims to install so they can get access😮

 

 

 

The NUC has the teamviewer app install - that is why I cam connect via teamviwer over my home WiFi as stated before. I installed teamviewer myself on all machines. I do not let other people install software for me, especially not somebody who has contacted me online....

3 minutes ago, Kev M said:

Did the NUCs IP address change from 192.168.0.2 ?

I thought this worked before when you had it connected to your wifi router ?

I was connecting using teamviewer not rdp. Have not been able to get teamviewer to connect via the mini-router to the NUC, although it will to the old minipc. I suspecct something is borked in the iniitial set up so am going to star afresh. 

2 minutes ago, malc-c said:

I think this may need to either be the admin account, or set up a guess account on the NUC and try using the same credentials when RDC from the laptop.

Yes - have reset the password on the NUC, but still dont seem to be able to log-in. I am thinking I am going to completely reinstall windows and set up the machine again. I may go back to using my old mini-pc. I had this idea that the NUC may be more efficient/faster etc but that does not seem to be the case. 

13 minutes ago, malc-c said:

Can you see either computer from each other?  ie open "This PC" and under Network is the NUC listed on the Laptop and vice versa ?

 

The laptop can see the NUC yes. 

I think I may be close to solving this. As suggested by Steviedvd, I connected the NUC aand the laptop to the wifi of the mini router. Suddently, the LAN connection on the NUC showed the mini-router was connected! I  retstarted and without wifi, the mini router is still connected. 

Following mac-c's suggestion going into the network listing on the laptop I clicked on the NUC and initiated remote connection. This appears to connect. The only issue I now have, is that when signing in, I get as far as the sign in page and the user states 'other user' and does not recognise the password... 

Sorry about the late reply - work gets in the way of things I would rather be doing. To clarify:

'I'd be inclined to factory reset the router .. might be something stuck in the DHCP reservations'

But the mini-router works with the old mini-pc'.

Also, can the NUCopen the router admin page or even ping it's IP address ?

As stated initially the NUC can open the router admin page, hence network adapter is working. 

Also as stated, remote desktop is working. 

Not sure but if the laptop is connected via wi-fi, to the ini-router, would the arp -a command show the NUC mac address/ip no allocated (the mac-address is hopefully on the NUC box label).  Then he can try a ping and see if it gets a proper reply - to test the network card/cable.

running arp-a gives me the following when run from the laptop connnected by wifi to the mini-router (arp -a.png)

We need the details of the NUC and what network settings/adapters it has configured.  Also, the NUC has to allow external remote connections either by activating Remote Desktop or for example adding a TeamViewer client (that also needs activating).

Details of the NUC and network settings were given earlier. Adapter is given as Intel (R) Ethernet connection (3) I218-V

I don't think we have asked about the NUC being new or pre-used.

Pre-used

The other thing to try is to connect both (the NUC and the laptop) on the home network and see if the NUC can be remote accessed. If that does not work it rules out the mini router.

I have done this as stated previously - I can connect to the NUC over the home networkif it is connected by LAN to the network or wifi .
The NUC can be accessed from the laptop if:

NUC connected via Lan to wifi router---Laptop connected wirelessly to wifi router

NUC connected via wireless to wifi router---Laptop connected wirelessly to wifi router

------------------------------------------

The NUC cannot be accessed from the laptop if:

NUC connected via Lan to portable router---laptop connected wirelessly to portable router

----------------------------------------

IP address for Laptop when connected to portable router needs to be checked to make sure it is not the same as the NUC ip address

The above summary is correct. I shall confirm IP address for laptop to portable router later. 

We've also asked the OP to confirm what version of Windows is running on both machines and there is no option for RDC on Windows 10/ 11 Home editions. 

Windows 10 pro as stated previously. 

You had a warning 'Network - no connection'  - it may be that your NUC Lan is set to use an ip in the 192.168.1.x  range as it works on your home PC - but would not get an ip assigned when connected to the mini router (192.168.0.x range).

The NUC wifi did get a proper IP so try connecting both the Laptop and the NUC to the wireless TP-Link hotspot and try the remote connect then.  Leave the LAN cable connected between the NUC/mini router so we can get the ipconfig details from it, if needed.

To do this do I need to change the routers operation mode from access point wireless router?

4 minutes ago, StevieDvd said:

Not sure but if the laptop is connected via wi-fi, to the ini-router, would the arp -a command show the NUC mac address/ip no allocated (the mac-address is hopefully on the NUC box label).  Then he can try a ping and see if it gets a proper reply - to test the network card/cable.

 

Given the mini router connects to other mini computer via the same cable we can rule that out. Also, the NUC connects via lan to my home router - I did this to rule out the network card. 

17 minutes ago, malc-c said:

I assume that both the NUC / mini-router and the laptop will be within range of the wi-fi provided by the mini-router ?

Yes of course. As stated before - it is not an issue with the previous mini pc. 

3 hours ago, StevieDvd said:

From the details posted your laptop has connected to the mini router and been assigned an IP address for that network. 

As the NUC is running Win Pro then enable the Remote Desktop option, that sorted another SGL member yesterday with a similar problem.

Did the older mini pc hae Win Pro and Remote Desktop enabled?

Edited as I read above you do have Win Pro on the NUC

To confirm, I do have win 10 pro. 

Remote desktop was not enabled and I have now enabled it:

However, LAN to the minirouter still shows  network - no internet and does not state that the network is present to the TP link. 

3 hours ago, StevieDvd said:

 

 

 

 

26 minutes ago, malc-c said:

So If I follow that correctly, you have a NUC PC connected to a TPLInk router which is wireless enabled and a laptop connected to your main router that has normal internet access via its fibre / ADSL connection.  The NUC PC has connected to the TPLink  and as it has DCHP enabled has been issued with its own IP.  As the TPLink router is not on the same network as your home network the  NUC can not be accessed from the laptop, but as it has wi-fi you will see the SSID being broadcast.  You should be able to create a new network on the laptop to connect to the TPLink, but this will then drop the connection to the internet as the TPLink router is not physically connected to the fibre / ADSL. Windows RDC needs to have both the Laptop and the NUC on the same network, it can't RD into a PC on a different VLan.

What is the reason you don't want the NUC to have internet access?  It would be far simpler to remove the TP link router and just connect the NUC to the existing home network and thus have everything singing from the same hymn sheet

No - that is not correct - the home router is not relevant and I only connect via this because I cannot connect via the mini router! 

As per my OP, and the link I shared, the NUC is connected to the mini-router via a network cable. The mini router should create a wireless network that I can connect to via my laptop, thus accessing the NUC via the laptop. This is what I did with my older mini-pc. The laptop connects to the wifi on the mini router - this is not the issue. The NUC for whatever reason does not  show the network connection to the mini router. 

The reason I did nt want to connect via my home (wifi) router is because I want to set this up so I can access the nuc headless at a remote site. 

1 hour ago, malc-c said:

I've not fully read the thread, and I'm a but rusty on my IT skills, but the two devices above are on different Vlans  (networks).  The "AstroLAN" is on what most routers default to, 192.168.0.xxx  but the "Home" network is on 192.168.1.xxx  with its's default gateway being port 254 of that LAN.  Now I could be wrong  but for both routers / hubs to communicate together I would have thought that they either need to be on the same network (ie 192.168.0.xxx) or possibly you need to set up some sort of port forwarding to allow the two devices to communicate.  You may need to turn off DHCP on one device and allocate IP addresses manually on anything connected to that router

Malc, I am not trying to get the 2 routers to communicate with each other, but rather use the mini router (TPlink) to create a network not connected to the inetrnet but accessible via my laptop. As stated in the OP, I can do this weith my old mini-pc, but not with the NUC.

23 minutes ago, skybadger said:

Hmm struggling to read .rtf files on my phone.

Is pdf easier?

Lan to mini router.pdf LAN to wifi router.pdf

To aid diagnostics further:

I an connect via LAN from the NUC to my home router which has interne connectivity. The settings etc are shown in the attached document 'LAN to wifi router'.

I do not have a LAN network connection to the mini-router. Settings are shown in the document 'Lan to mini router'.

LAN to wifi router.rtf Lan to mini router.rtf

Remote desktop is enabled, but this should not be relevantshould it as I am connecting via teamviewer. 

There is no built in wifi. This is shown in device manager:

'You state "the NUC can obviously see the mini-router, yet the is no ethernet connection. " - It must have a wired or wireless connection to be able to 'see' the router. Was this done via a browser on the NUC?'

The mini-router is connected via LAN (wired). I can get into the control panel of the router via a browser, which is what I mean by 'the NUC can see the mini-router'. 

Running ipconfig gives me where 'wireless LAN adapter wifi 2' is the usb wifi adapter :

Wireless LAN adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Local Area Connection* 12:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : AstroLAN
   Link-local IPv6 Address . . . . . : fe80::16a:8604:d8a7:2554%7
   IPv4 Address. . . . . . . . . . . : 192.168.0.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1

Wireless LAN adapter WiFi 2:

   Connection-specific DNS Suffix  . : home
   Link-local IPv6 Address . . . . . : fe80::b8e0:8b5d:ca2c:8340%16
   IPv4 Address. . . . . . . . . . . : 192.168.1.157
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254

4 hours ago, skybadger said:

I have several thoughts. 

Does enabling the wireless on the nuc disable the wired connection and vice versa? 

Does the router prevent client to client network traffic. There's typically a tick box on the router for this 

If the nuc can't see the 'internet', for a given definition of internet, windows can report no connection and work anyway. I have that when using a corporate vpn. Is there a DHCP, DNS and gateway identified for both the WiFi and wired connection properties ? 

If there isn't a DHCP, DNS or gateway, define the nic as being its own gateway, with its own DNS and set to static IP. 

Is the IP address of the nuc on the same network as the router ?

I think we need more info on the current setup to diagnose this further. 

 

 

 

 

 

 

Enabling the wireless makes no difference - the NUC does not have a wireless card so I use an external USB dongle. 

'Does the router prevent client to client network traffic. There's typically a tick box on the router for this'

This was ruled out in my original post - plugging the router into my old mini-pc works without any problem and I can connect in this case using Teamviewer/RDP/VNC. Consequently, we can rule out issues with the router settings. 

DNS and DHCP I will check when back home. From memory the IP address on the NUC indicates on same network as router - again on the old mini-pc there are no issues with connection, with it showing LAN as the TP-Link.

What further info do you need?

2 hours ago, Peter Reader said:

Have you sett up team viewer for LAN?

https://metabust.com/blog/how-to-use-teamviewer-remote-control-over-lan

Static IP?

Nope. The problem is not team viewer - it works perfectly well on the older mini-pc. I did run through the webpage you shared and switch to 'accept' local connections just to check. This make no difference. 

The issue is not with the specific access software, but getting the NUC to see the mini--router as a network. Have tried static IP - no difference and again not needed on old mini-pc. 

2 hours ago, Viktiste said:

What version of windows is on the NUC? Home edition does not support Windows Remote Desktop.

Windows 10 Pro. I am not using RDP in any case, but team viewer. This should not be relevant as the mini router creates a local WiFi network the laptop can connect into. 

As per the embedded Post, the router is connected to the NUC/mii-pc over LAN. The router is set to access mode. This creates a local WiFi network which laptop can connect into.

I use a mini PC at my mount which I remote into in a similar manner to this:

This has worked well with my previous mini-pc (ACE PC Mini OC with Apllollo Lake J3455 CPU). I use the same TP-LINK mini router as in the post above. 

However, at the end of last year I picked upp a used Intel NUC (513myhe) with intel i3. This is where the probelms began. Connecting the mini-router as above I tried to remote in to the NUC. No joy - despite the laptop being able to see the WIFI network created by the rouer. The issue appears to be with the NUC. On the previous mini-pic, on examining the conections, the ethernet reported I was indeed connected to the TP link mini router. However, in the case of the NUC it states 'Network - no connection'. Consequently, I decieded to check if the router was set up correctly. I can access the router control panel, so the NUC can obviously see the mini-router, yet the is no ethernet connection. 

Does anybody have any ideas?

Hoever,