+- Blitzortung.org Forum (https://forum.blitzortung.org/mybb)
+-- Forum: Public Forums (https://forum.blitzortung.org/mybb/forumdisplay.php?fid=29)
+--- Forum: Hardware, Software, Lightning Physics (https://forum.blitzortung.org/mybb/forumdisplay.php?fid=30)
+--- Thread: Lost controller (/showthread.php?tid=2546)
RE: Lost controller - tassyjim - 2018-03-22
(2018-03-22, 20:05)Alanpenwith Wrote: Hi
Sorry if it's confusing. The set up is a main pc and two netbooks (which each run only one programme which uploads to a website) Everything running windows 7.. Previously they were all wired (with a tooway satellite connection to the internet) but a new wifi system over the phone network has proved much faster so I changed the networks over to all wifi. (That in itself was not simple as windows and avg like making their own adjustments).
Regards
Alan
You might have more luck using a stand-alone wifi bridge.
I have used this on with reasonable success:
Vonets VAP11G
That gets you away from the pain of Windows
Jim
RE: Lost controller - dupreezd - 2018-03-22
Quote:You might have more luck using a stand-alone wifi bridge.
I have used this on with reasonable success:
Vonets VAP11G
+1
Or one of the TPlink ones, MR3020, N300,
RE: Lost controller - mwaters - 2018-03-22
(2018-03-22, 16:06)Alanpenwith Wrote: I have been trying to set up a shared network having changed from a wired to wireless network for the pc's.
What is the source of the wired network? Your ISP? If so, where is the router/firewall? The latter is where it is customary to configure the IPs and NAT.
RE: Lost controller - tassyjim - 2018-03-22
(2018-03-22, 22:49)mwaters Wrote: What is the source of the wired network? Your ISP? If so, where is the router/firewall? The latter is where it is customary to configure the IPs and NAT.His original Internet was through a satellite connection. They are typically slow and suffer from very high latency. Been there - done that.
For the satellite connection he would have used a standard router connected to the satellite 'modem'.
He has changed to a 'mobile' Internet which is much faster and better all round if you have good mobile reception. The new internet uses a WiFi only modem/router hence the need to change.
He is having difficulties using the Windows network bridge which should allow a device connect to the Ethernet on the PC to use the PC's WiFi for Internet access.
Jim
RE: Lost controller - Alanpenwith - 2018-03-23
Hi
Jim is quite right and sorry about the typos with ip addresses. The settings are correct - I just got in the habit of WRITING the wrong thing.
The first thing I need is a way to communicate with the controller. I pressed the reset and boot0 and let go in the right order so the controller should be at factory default so any ideas of what next to do would be gratefully received.
Regards
Alan
RE: Lost controller - gerbold - 2018-03-23
(2018-03-23, 07:52)Alanpenwith Wrote: The first thing I need is a way to communicate with the controller. I pressed the reset and boot0 and let go in the right order so the controller should be at factory default so any ideas of what next to do would be gratefully received.Hi Alan,
in case your router would have an ethernet port, may you connect it to this?
The router should assign an IP address to the controller. Check your routers status page for IP addresses off connected devices.
If this is not possible, this may be another solution.
Your WLAN network has the address range 198.162.100.1 to 198.162.254, correct? If so and you want to have the following setup wher the router and the Win7 PC are in the Wifi network and you want to connect System Blue via ethernet to the Win7 PC, both networks have to have different IP address range.
ISP <=any IP=> router (e.g. 192.168.100.1) <= Wifi 192.168.100.X => (DHCP e.g. 192.168.100.123) Win7 (static 192.1681.1) <=192.168.1.X => (static 192.168.1.235) SystemBlue
Regarding the default address of System Blue 192.168.1.235 I'm not quite sure. I changed mine to a different one. This address I read in the documentation of System Red.
In the CMD window type "ping 192.168.1.235" - without the quotes. You should get a reply.
In the browser type "http://192.168.1.235" - without the quotes. You should get the web page of System Blue.
Cheers
Klaus
RE: Lost controller - Alanpenwith - 2018-03-23
(2018-03-23, 08:35)gerbold Wrote:(2018-03-23, 07:52)Alanpenwith Wrote: The first thing I need is a way to communicate with the controller. I pressed the reset and boot0 and let go in the right order so the controller should be at factory default so any ideas of what next to do would be gratefully received.Hi Alan,
in case your router would have an ethernet port, may you connect it to this?
The router should assign an IP address to the controller. Check your routers status page for IP addresses off connected devices.
If this is not possible, this may be another solution.
Your WLAN network has the address range 198.162.100.1 to 198.162.254, correct? If so and you want to have the following setup wher the router and the Win7 PC are in the Wifi network and you want to connect System Blue via ethernet to the Win7 PC, both networks have to have different IP address range.
ISP <=any IP=> router (e.g. 192.168.100.1) <= Wifi 192.168.100.X => (DHCP e.g. 192.168.100.123) Win7 (static 192.1681.1) <=192.168.1.X => (static 192.168.1.235) SystemBlue
Regarding the default address of System Blue 192.168.1.235 I'm not quite sure. I changed mine to a different one. This address I read in the documentation of System Red.
In the CMD window type "ping 192.168.1.235" - without the quotes. You should get a reply.
In the browser type "http://192.168.1.235" - without the quotes. You should get the web page of System Blue.
Cheers
Klaus
RE: Lost controller - Alanpenwith - 2018-03-23
Thanks
I tried the ping on 192.168.1.235 but got no reply. The wifi ip range is 192.168.0.1-255 and bridging to the lan sets an ip of 192.168.100.1 to the lan card. I'm trying an ip scan of the whole range of 192.168.0.1 to 192.168.255.255 - it's taking a while.
Regards
Alan
RE: Lost controller - Jorgeminator - 2018-03-23
(2018-03-23, 09:07)Alanpenwith Wrote: Thanks
I tried the ping on 192.168.1.235 but got no reply. The wifi ip range is 192.168.0.1-255 and bridging to the lan sets an ip of 192.168.100.1 to the lan card. I'm trying an ip scan of the whole range of 192.168.0.1 to 192.168.255.255 - it's taking a while.
Regards
Alan
Sorry, but now I'm confused.
Initially you said you were SHARING the connection. Now you are suddenly BRIDGING it. Which one is it?I'm pretty sure you are bridging the connections. You shouldn't do that. If you were sharing the connection correctly, the LAN card would be assigned a static IP address 192.168.137.1.
Quote:"After enabling Windows 7 Internet connection sharing feature, the network card connected to the home network (wired or wireless) would be assigned a static IP address 192.168.137.1 with netmask 255.255.255.0. This ICS host will act as a DHCP server and assign other IP addresses in the 192.168.137.x/24 range to other client computers."
RE: Lost controller - Alanpenwith - 2018-03-23
Hi
Yes I have tried both bridging and sharing and so far neither has worked. I also tried disabling the wireless connection so I had to be communicating through the LAN (which I was able to do until I played around with the controller settings). Sorry - this is all really windows 7 problems and not the controller.
So back to square one. Can someone confirm that to reset to factory settings the procedure is - reset and boot0 buttons together -release reset then release boot0. Do I then power off and then on? If that is correct I should be able to find 192.168.1.235 - yes ?
Or is there another procedure ?
Thanks for all the comments so far
Regards
Alan