Duet pi GUI
-
ifconfig
(orsudo ifconfig
) will give you a more detailed list of network addresses.i suspect
iwconfig
will do the same for the wifi name(no idea where those things are in the gui unfortunately)
edit: 127.0.0.1 is a special addres for loopback testing, refered to localhost. it doesn't go anywhere; weird hostname -i outputs it if it has other addresses.
-
Thanks! I do the ipconfig, then arp -a, which gives a list of all ip addresses connected to each AP. Nothing new shows up.
-
@BearcatTD said in Duet pi GUI:
then arp -a, which gives a list of all ip addresses connected to each AP
that had me raise an eyebrow; for several reasons
- arp is only a mac to ip address mapping, and only populated and cached for 2-5 minutes for addresses the host has connected to
- it will not include the hosts own address under any circumstances i think where did you run
arp -a
?
edit: I'm thinking your pi is probably not connected to the internet or any network for that matter; but puzzled what would make you think it is. erase and rewind a little - how do you interface to the pi currently?
-
arp -a runs on mac after ifconfig and on Windows after ipconfig
-
ah, i assumed you'd run this on the Pi, as that is where it would have made sense to run
hostname -i
neither command would have done you any good outside of the Pi.also note ifconfig , not ipconfig for the Pi.
This is what I thought you'd be after, and wanted you to try:
pi@duet3:~ $ iwconfig eth0 no wireless extensions. lo no wireless extensions. wlan0 IEEE 802.11 ESSID:"bearlink" Mode:Managed Frequency:2.447 GHz Access Point: D4:5F:25:EC:B4:54 Bit Rate=72.2 Mb/s Tx-Power=31 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=54/70 Signal level=-56 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 pi@duet3:~ $ ifconfig eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether b8:27:eb:08:5c:88 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.10.0.237 netmask 255.255.255.0 broadcast 10.10.0.254 inet6 fe80::451b:b7f0:f1ab:e16d prefixlen 64 scopeid 0x20<link> ether b8:27:eb:5d:09:dd txqueuelen 1000 (Ethernet) RX packets 194 bytes 18456 (18.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 80 bytes 15217 (14.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
-
YES! I did this about 5 seconds before your post came through...LOL Thanks!
-
Did you resolve the issue?
-
@bearer It did! Now I just need to figure out where and how everything plugs in!
-
@BearcatTD
Can you tell me how you installed duetpi? I've been trying for 2 days. I downloaded duetpi.zip, used balena etcher. Put it into the raspberry pi model 3. And all I get is a black screen with some codes but it stops there. -
@tekstyle said in Duet pi GUI:
Put it into the raspberry pi model 3. And all I get is a black screen with some codes but it stops there.
You should probably create a new topic and include "some codes" to get help with your problem.
-
@tekstyle I downloaded the duetpi file with the full GUI. I connected the pi to the duet 3 with the ribbon cable. Did you edit the wpa_supplicant.conf? So you can connect to wifi. If you haven't done this yet, make sure you use a good text editing app (I swear by Atom), as Windows and Mac stock apps sometimes put weird line breaks and other funkyness in the files.