TXT 3: no ssh connection possible after reset

[hvn]

Hi,

I have a serious connection problem with a TXT 3 contoller running 4.6.6.

Normal situation is that I use ssh to login to the controller via Wifi using 2 ssh terminals. All worked fine, until there was an power problem. Power loss happened many times before, and the solution always was to start the controller again, wait for the ssh broken pipe message (only takes a few minutes) and login again.

Now, the broken pipe message appears after a very long time and only in 1 terminal. Not good. So I try to login and it does not connect all. After some error seeking, I find out that on the controller in Network, wlan0 and netmask are empty. Checking for my other TXT controller: not empty and I can login just fine.

So I decide to edit the IP address and find that all the correct data is still there. Nothing for me to do. But it doesn't show anymore in the wlan0 display.

I decide to re-enter all wlan0 data, but this doesn't solve the problem. Still no IP data in wlan0 display and no connection. Also not after several reboots of the controller.

Is there any way I can solve this? RoboPro only connects to the controller via Wifi. Since version 4.6.6 no more via USB.

Thanks for any help.

[vleeuwen]

What is a TXT 3?
I only know a TXT or a TXT4.0.

Did you try to reinstall the TXT firmware?

[hypnotoad]

With ssh -v, you can get more infos about when it is hanging. With nmap, you can see if ssh is listening at all and with ping, you can check if the txt is responding.

I would guess that the configuration is corrupted and should be reset (but don't know how this is done).

[hvn]

What is a TXT 3?
I only know a TXT or a TXT4.0.

Did you try to reinstall the TXT firmware?

In that case, it's a TXT.

No, I didn't think of that. No even sure 4.6.6 is still around, being the community firmware.

[hypnotoad]

If you usw the cimmunity fw, please try creating a new sd card. All settings are stored there and the original fw is basically irrelevant for the problem.

[hvn]

If you usw the cimmunity fw, please try creating a new sd card. All settings are stored there and the original fw is basically irrelevant for the problem.

After quite a bit of time, I have made another attempt to regain connection. Which failed. Upon the suggestion, I did not create a new sd card but upgraded the cfw version. Without result. However, since I have 2 TXT's, one of which is working, I made imagess of the network settings of both.

TXT-IP-addresses.png (1.95 MiB) 169 mal betrachtet

.

Both lower images are from the screen after pressing the Edit button.

You can see that at left, both IP addresses are shown: it's the correctly working TXT.
At right, the IP address is shown only at the bottom. That's the TXT that fails to connect.

Is there a reason that could explain the difference between the 2 network interfaces, other than that the TXT is broken?

[hypnotoad]

Of course, it could be that something is broken. But I think it is way too early to give up !

You should check if your txt is really connected to the network (e.g. by running `ping 10.0.0.134` or `nmap 10.0.0.134`). It could also be that the wifi password has been entered wrongly - I don't know how this looks like.

If both txt controllers run the CFW, you could try swapping the SD cards and see if the problem also swaps.