Following on my my problems of last week, I now have them resolved, thanks to the help received from knowledgeable people on here. So I now have another ssue that I would appreciate help on. I’ve put together a new PiAware rig to replace my current 3B one, this time using a Pi Zero W. I’ve got PiAware 8.2 installed and running with wifi access, and have put the empty file “SSH” onto the card. The reason I did this is because the rig is going to be mounted some distance from the router, and not readily accessible, so I wanted to be able to do some remote examination of the wifi signal quality on the main desktop Windows machine that I have on the same network before installig it where its going… I’ve no idea yet quite how you persuade it to give you this info, but I have read that it will if given the right commands (any help with that would be appreciated as well ) But the main question is about logins and passwords. I have the IP address of the Pi, and if put that into Putty with SSH set, I appear to get connection to the Pi. It comes back with 'login as: ’ followed by a request for a password. And there I am stuck. Is there a default login and password or if not, where / how do I find them ?
Thanks in advance for any help
Geoff
If you are using the piaware image, make sure you are using username “pi”. There shouldn’t be a password in this situation.
If you installed Raspberry Pi OS (or Debian) and installed piaware as packages, then you would use whatever username & password for the account that you set up when you installed.
If you are using puTTY from Windows to connect there will be a field for user and password. If you are connecting from the command line on a Mac or from Linux, your connection string should be “ssh user@”.
To use my system as an example, I would use “ssh pi@192.168.0.xxx”
Thanks for that ! It’s a standard FlightAware v8.2 image. I was only using Putty because I happened to have it on the desktop and have used it in the past (a long time ago, and not for anything Pi related) and knew that it could do SSH comms. I’m a hardware engineer really, and not too clever with software,so any help is appreciated. So are you saying that Putty is not a good choice for doing any direct comms with a Pi ?
When using Windows it is one of the easiest and most used programs. Putty uses a Graphical User Interface (GUI) and you can use it to store connections as well by using the save option. I have 23 systems in my list and. I’m glad I don’t have to memorize the different IP addresses of them
When using Linux or a Mac you can use the method @jafrank mentioned and that saves you from installing a separate program for SSH connections.
Thanks. I have now established contact with the Zero using ‘pi’ and ‘flightaware’ through Putty. I then tried to use 'iwlist wlan0 scan, but that returns
so I’m lost again now. Is that something that’s readily resolvable or not ? Its not desperately important. Its just that the unit is going to be sited some distance from the router, so I thought it would be an interesting exercise if the Pi was capable of reporting the quality / signal strength of the network it’s connected to. I’m surprised actually that the router itself does not report similar data as it’s an expensive sophisticated TP Link one, but I can’t find anything in the user interface that shows this info…
I’ve always found signal quality/strength confusing. Which is more important, quality or strength? Plus some give readings out of 70 (not sure why but guess it must relate to some scale) and sometimes it is out of 100.
-30dBm is probably sitting right beside to router, up to -70dBm would be OK
Useful link to give you an idea of signal strengths.
Ha ! Yes ! Sorted ! the ‘ww’ was wrong, spotted by my son who’s an IT bod who just turned up. This is a wireless keyboard, and when the batteries get a bit low, it sometimes misses characters or doubles them.
In terms of which is most important, as a hardware engineer, I would say slightly in favour of the quality figure, as this should be derived in terms of analyzing things like dropped packets, which can occur because of reflections of the signal, as well as interference. That said, the signal strength is a ‘raw’ figure supplied by the software within the third party wifi module. If everything is good, improving the signal strength should in theory give a corresponding improvement in signal quality as few dropped packets, and greater immunity to interference - ‘thicker armour’ if you like …
I’d be interested in anyone else who might be better qualified in this field’s opinions on this topic.
Just a thought. When it scans, it finds every network in the neighbourhood. Is there anything that can be added to the command line to restrict it to just a specified network name ?
Wow, thanks. The depth of knowledge on here and the level of help freely given is excellent.So much better than on many forums now where everyone treats you like a moron…
That one looks a bit complicated. The first one is doing what I need in broad terms. Is there any combination of parameters in the command line that will cause it to report just my network ? I’ve tried various ‘guesses’ but they either don’t work at all or produce unexpected results. Am I right in thinking that the command line interface is a bit ‘fussy’ over things like spaces ? Also, can the command line be just repeated without having to type it all in every time ? Thanks
) But the main question is about logins and passwords. I have the IP address of the Pi, and if put that into Putty with SSH set, I appear to get connection to the Pi. It comes back with 'login as: ’ followed by a request for a password. And there I am stuck. Is there a default login and password or if not, where / how do I find them ?
