set_ has joined #beagle
Guest22 has joined #beagle
Guest22 has quit [Client Quit]
ball has joined #beagle
akaWolf has quit [Read error: Connection reset by peer]
vagrantc has quit [Quit: leaving]
akaWolf has joined #beagle
<set_> GenTooMan: Things are on hold for now. The Cape has no components to be placed on it. Boo!
<set_> They need to dig into the sand more. Sheesh.
<set_> I found a mfg. but their PCB and assembly mfg. is held up by their lack of components. They are outsourcing to me for components. Blah.
<set_> I have to look around...
<set_> I contacted DigiKey and I will have to reach out to other stock merchandisers.
<set_> Argh...
<set_> You know something, if it is not one is two, three, four things * infinity. Blah.
<set_> I feel like that child that could not get his candy on trick or treat day.
<set_> Deme el ducle!
<set_> switch the c w/ the l and that is give me my sweets in Spanish.
<set_> I am so close. Seriously. I can smell the etching and placements!
zjason` is now known as zjason
starblue has quit [Ping timeout: 260 seconds]
Guest82 has joined #beagle
<Guest82> Hello,
starblue has joined #beagle
<Guest82> Can anyone please guide me how to acquire data from a sensor through USB Host in Beaglebone black?
<set_> Um, what data are you trying to acquire and what sensor are you using? How are you trying to acquire it? UART? GPIO? Um, SPI?
<set_> I used a python script once to get data from a sensor...I put it in .csv format for later! Is this what you are describing? If not, there are many ways, methods, and different ideas to gather before answering so quickly.
<set_> ...
<set_> All I can do is try to help.
<Guest82> I have to acquire data from this sensor. It has USB output so it would be better if I can acquire through USB
<set_> oh.
<set_> Okay.
<set_> Please hold. Let me look up ideas...
<Guest82> Sure. Thanks
<set_> I think you can just use a SD Card on this thing to track environmental measurements and then put it in the 'puter.
<set_> What USB type does it have on it?
<set_> I see. USB 2.0 and RS232!
<set_> Are you going to use the BBB w/ it?
<set_> Plug it in and see if they have an open source lib. in their ranks!
<set_> I will keep checking.
<Guest82> I will use industrial BBB and cellular modem cap
<set_> Oh. Hey, I see they have a user manual but it needs one to sign in and deal w/ these people.
<set_> I am not going to sign in. Maybe someone else can help, i.e. one that deals w/ these people. I am sorry.
<set_> But...if they have a SDK to use, show it. I can maybe help then!
<Guest82> I have that document
<Guest82> How can I share with you?
<set_> Google
<set_> do a share w/ google
<set_> or pastebin
<Guest82> It's a pdf.
<set_> google
<set_> Do you have the SDK or the manual?
<Guest82> I have a manual.
<set_> oh.
<set_> So, once we figure out how the thing understands things, we can then use Linux and the BBB to procure the data?
<set_> I are using your BBB for the procurement right?
<Guest82> Yes that's right
<set_> Okay, skip the manual for now. Once you plug in the device to your bbb and look for what is available on USB devices on the BBB, what do you see?
<set_> it should be in /dev/
<set_> USB0 or USB1 or whatever...
<set_> or...does it come across as something completely different?
<Guest82> Bus 001 Device 004: ID 0403:d920 Future Technology Devices International, Ltd
<Guest82> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
<set_> Hmm. Is it plugged in?
<Guest82> Yes
<Guest82> when I plugged in Bus 001 Device 004 appear
<set_> Okay...let me see. try this when it is not plugged in: ls -la /dev/tty* && ls -la /dev/*
<set_> Then, when it is plugged in, type the same thing to figure out what device shows up.
<set_> There should be a difference in available ports on the /dev/ dir.
<set_> That thing looks nifty but I do not think they are Open Source. Are they Open Source? Do they offer open schematics and open source SDKs?
<Guest82> I don't think they are open source
<set_> Okay. Hmm. So, w/ that in mind...
<Guest82> They gave a document that has set of commands to interact with device
<set_> 1. I think that gathering data outside of their normal way is impossible. 2. There is no way for the BBB to access the data in SD Card format unless you build something, i.e. SD Card port on the Linux bound BBB.
<set_> Or...RS-232 port?
<Guest82> I agree with you. It seem that it is bit tricky
<Guest82> *seems
<set_> Well...
<set_> I was going to ask someone else who is more inclined to know how things work on the BBB, e.g. does the SD Card holder have access to be read/write from and so on?
<set_> Now, I think if you have a SD Card to USB dongle...
<set_> Then, you can read and write to the card.
<set_> But...I do not know of such a dongle outside of one person. Some guy from NY builds them.
<set_> can build it.
<set_> Nope. Never mind me. It seems we are at odds w/ building something. You need a RS-232 to SD Card reader or a SD Card to USB reader.
<set_> Hmm. That sounds neat.
<Guest82> Do you mean from the sensor SD card to USB or RS232 reader?
<set_> So, the USB on the BBB. That USB needs a dongle to read/write to SD Cards. I think this is the only way to get your SD Card data from the Nor-139 and parse it or whatever you plan on doing w/ it.
ikarso has joined #beagle
<set_> The person from NY stopped producing the USB-to-SD dongles. Odd.
<set_> Oh well.
<set_> His might have been backwards in this form of operation anyway.
<set_> Hmm. This brings up an interesting question. Is there such a dongle for use in Linux outside of popular brands?
<Guest82> In that can I will have to remove the SD card from Nor-139 and connect to SD cards to USB converter?
<set_> Right.
<set_> The SD Card connector on the BBB does not allow for use outside of pushing an image from it, right? Let me double check.
<Guest82> The Nor-139 will be away from the lab so it is not feasible to do that. I need to acquire data remotely
<set_> Yep. So, the SD Card connector on the BBB is only for a secondary boot source.
<set_> Oh.
<set_> Do you use AT Commands?
<set_> So, the BBB and Nor-139 are attached already and remote.
<set_> Okay.
<set_> And...can you connect to the BBB remotely?
<Guest82> Yes I use AT Commands.
<Guest82> The plan is to attach BBB and Nor-139 and operate remotely
<Guest82> I am planning to get a cellular cape for BBB
<Guest82> For remote communication
<set_> Oh.
<set_> Hmm.
<set_> So, what language do they say you can use w/ the AT Commands?
<set_> Their SDK or language, from scratch, needs you to have access to all available datasheets, connections, and to know the language of use.
<set_> ls -la /dev/tty*
<set_> If you are remote, ssh in and type that idea out.
<set_> If you cannot turn off the module from a remote location, can you reboot it?
<set_> You can probably have access to the BBB and data but the location of the tty device needs to be known.
<set_> On the BBB used, you definitely need your /dev/ttyS* or /dev/ttyUSB* locations known.
<set_> For instance, just try this out. You have a XBee for instance, use the AT commands to set up your connection, pair them, and then have those modules/modems chat w/ each other either by way of AT or python for instance.
<set_> So, then, even in that circumstance, you will need to have the device location on your BBB system.
<set_> Even if it is by USB connections...
ball has left #beagle [Oh.]
<set_> find your device list and list them, know them, and use them.
<set_> ssh username@ip_address
<set_> or ssh name@location
<set_> then... ls -la /dev/tty*
<set_> Oh. I see the issue.
<set_> Time to use all our TTY devices to find it.
<set_> Dang.
<set_> Let me test real quickly.
<set_> I am going to type ls -la /dev/* when nothing is plugged in via the USB connector on the BBB. Then, I will plug something into the USB connector after it is shutdown. I will start it again and type ls -la /dev/*
<set_> Then, I can find what is going on during the process.
<Guest82> You want me to shutdown the sensor>
<set_> No.
<set_> Do not worry about it.
<set_> I am setting up a system right now. I will show you what is available during on and w/ nothing in the USB Port.
<set_> Then, I will boot w/ a USB dongle connected. I will find something to stick in the USB Port and then run ls in the /dev dir.
<set_> 5 minutes.
<Guest82> Sure. Take your time, I will wait.
<set_> Okay. It is just two photos I am setting up. ls in the /dev dir.
<set_> So, this is the /dev dir. w/out anything attached to the USB on the BBB:
<set_> Hmm.
<set_> This is odd.
<set_> My board is not showing ssh'ing is available when USB gadgets are attached.
<set_> scratch that. I am in.
<set_> try /dev/ttyUSB0
<zmatt> Guest82: that lsusb output looks like it shows up like an ftdi serial device, presumably an integrated usb-serial converter in the device connecting to a serial interface
<zmatt> do have documentation of that serial protocol?
<zmatt> *do you
<Guest82> I have a user manual of the device
<zmatt> can you share it?
<zmatt> annoying that the manufacturer doesn't simply put it online :/
<zmatt> hmm, and they have software for doing this but it's Windows-only
<Guest82> set_ /dev/ttyUSB0 is not working
<zmatt> what are you trying to do with it?
<set_> Hmm. Did you ssh in and then write a script to read your data?
<set_> Guest82: @zmatt is by far more experienced in this field if you need technical typing. Seriously.
<set_> but...I can try to see what they have posted in the .pdf files.
<Guest82> zmatt I need to acquire data to BBB from this sensor (Nor-139) and push it to the sever remotely
<zmatt> yes I meant, what did you try just now that's "not working" ?
<Guest82> set_ Thanks for that
<Guest82> I am trying to connect sensor to BBB
<set_> no issue. I usually beat around the bush for years. @zmatt is a pro at technical chats.
<Guest82> I am in very early phase of this task
<set_> He even has a nice way to configure things quickly!
<zmatt> Guest82: what did you mean by "/dev/ttyUSB0 is not working" ?
<Guest82> I mean I couldn't see USB device
<zmatt> on the BBB?
<Guest82> Yes
<Guest82> but when I do lsusb I get this
<zmatt> yes you already showed the lsusb output
<Guest82> When I remove the sensor from BBB FTDI  disappears
<zmatt> based on which I would definitely expect it to show up as /dev/ttyUSB0
<set_> Right...the BBB has only USB device, i.e. /dev/ttyUSB0.
<zmatt> ehh, no
<set_> No?
<set_> Well, it can support more but the BBB has one USB Port.
<zmatt> non-acm usb serial devices (such as FTDI serial devices) are simply numbered sequentially as they are discovered
<set_> Sorry.
<set_> Oh.
<zmatt> (and you can have multiple when using a usb hub)
<set_> Right. That is what I was thinking.
<zmatt> but since this is the only usb-serial device connected, it would normally be /dev/ttyUSB0 yes
<set_> Right. That was my thought.
<zmatt> Guest82: after plugging it in, can you grab the last bit of kernel log using: dmesg | tail -n 20
<zmatt> and then share it using or some other paste service
<zmatt> (don't paste it directly into chat)
<zmatt> the documentation seems very sparse about the serial communication
<zmatt> they mostly seem to expet you to use their software, which only runs on Windows
<zmatt> *expect
<zmatt> hmm, no driver seems to be leading for it
<zmatt> *loading
<Guest82> They have got windows USB driver software
<zmatt> well yes because windows sucks and doesn't really have class drivers, but any ftdi device would normally just work on linux... lemme look up that vid/pid
<set_> w/out the driver, how is one supposed to use it at all?
<zmatt> hmm, 0403 is FTDI alright, but 0403:d920 isn't in the usb IDs database
<zmatt> set_: linux has a driver for ftdi devices (ftdi_sio)
<set_> I know but I figured this one was a special case.
<zmatt> it's just not in the list, presumably because it's a really obscure device and noone has bothered to add it
<set_> It even seems like a weird link outside of http/https.
<zmatt> ??
<set_> I looked up their website.
<set_> it stated ww3 or wwd or something first and then their site.
<set_> Let me go and check again.
<zmatt> Guest82: there's probably a way to force the ftdi_sio driver to be used for this device
<zmatt> (and if that works, to request it to be added to the list)
<set_> Yes!
<Guest82> True.Its weird.  It's a Japanese firm.
<set_> Oh. It is https://web2. and then the site.
<set_> Oh well.
<set_> How can one force the FTDI driver so it can be used in Linux?
<Guest82> zmatt How can we do that? Can you please elaborate on that?
<zmatt> I am checking
<Guest82> Sure. Thanks
<set_> Hmm.
<set_> So, it may be a COM port.
<zmatt> Guest82: try removing the device, then executing the following two commands on the beaglebone: and then plug it back in
<set_> Right-o!
<set_> Nice.
<set_> I looked at the commands. That is neat.
<set_> so, echo'ing and then piping the rest handles this issue?
<Guest82> I will try that now
<set_> So, linux can overwrite, w/ tee, your driver for your module? I never knew.
<set_> I looked up tee w/ examples. I have not used that command in some time. Hmm. It sounds neat.
<zmatt> I'm just using it as a way to write something with root privileges
<set_> Usually, one would just use it to produce stdout to file(s).
<set_> Oh.
<zmatt> since you can't do 'sudo echo blah >file' since that applies sudo to "echo blah" (which doesn't need it) rather than to the redirection to file
<set_> Right. I did learn you can sudo sh "echo blah > /file"
<set_> A short bit ago, that is exactly what i was looking to do. I never once thought of tee.
<zmatt> that works too yes
<zmatt> well there ya go
<Guest82> Seems it's working
<set_> Damn!
<set_> Sorry. Dang!
<set_> That is near awesome.
<zmatt> this chat is not PG-rated :P
<set_> I try though. It is hard not to hold back but I try anyways.
<set_> I cannot believe Linux is that powerful w/ a two-line command.
<set_> I wonder now. Guest82: Be careful! Who knows who would want to find out about your hearing tests.
<set_> Sound acquisition or however you are using this device.
<Guest82> Will it be too much if I ask you some more help to understand how to acquire data to BBB from this sensor
<Guest82> ?
<set_> No. It is not too much to ask. I say, use an easy scripting lanuage where you can install /dev/ttyUSB0 into it as a device to use.
<zmatt> it kinda is since it's just too poorly documented. however, there's nothing BBB-specific about this task
<Guest82> Thank you very much for help me fix zmatt
<Guest82> *helping me fix it
<zmatt> from this point on you can do serial communication with the device, the details of doing so are however device-specific
<set_> Oh. I thought you were thanking me for fixing @zmatt. Ha.
<zmatt> note that you'll need to execute these two steps each time after boot, unfortunately
<set_> Write a script!
<set_> Can one write a script even if modprobe is used?
<set_> I did not even know modprobe worked on the BBB.
<zmatt> uhh, why wouldn't it? it's part of every linux system
<set_> I was unaware. I must have been using it incorrectly.
<zmatt> the main problem is that the usb device needs to be plugged in *after* performing these steps... there's probably a way to force linux to rescan/reprobe the device, but I don't know off the top of my head how to do that
<Guest82> If you could share any example code for serial communication that would be great?
<zmatt> that's just way too generic a question
<Guest82> If you have any
<set_> I can try but do not laugh.
<zmatt> like, what programming language?
<zmatt> set_: please don't try
<set_> Fine.
<set_> That saves me a headache.
<Guest82> Python would be great
<zmatt> Guest82: I'm pretty sure pyserial is installed by default
<zmatt> on the BBB
<Guest82> But I don't mind if you have it in other programming language
<set_> I can check on my side. What kernel and image are you using, Guest82?
<zmatt> kernel is irrelevant
<set_> Oh.
<set_> Okay.
<zmatt> you can confirm it's installed by doing e.g. python3 -c 'import serial'
<set_> I say kernel b/c of what is available in the languages used in each, different kernel. For instance, in Python3.7 to Python3.9, some has changed.
<zmatt> (which will print nothing if it's installed, or something like "ImportError: No module named serial" if it's not installed)
<zmatt> set_: that still has nothing to do with kernel
<set_> Okay. Okay.
<zmatt> and current debian buster images ship with python 3.7, not 3.9
<set_> Right.
<set_> You are right about that idea. I was using the Bullseye and noticed that by default, 3.9 is used.
<set_> So, I figured there was some reason for this upgrade.
<Guest82> @zmatt It is not installed. I get an ImprtError message
<zmatt> Guest82: just checking, you're using "python3" and not "python" ?
<zmatt> ("python" in debian buster still refers to the (obsolete) python2 for backwards compatibility reasons)
<Guest82> Yes I am using python3
<zmatt> okay then just install it using "pip3 install pyserial"
<set_> Like w/ C/C++ and their standards. When you stdout to file in Linux, you can see all the warnings from the different versions of C/C++ from a SDK install, e.g. C++ 11 may want it this way while C++ 17 uses this difference in source and those warnings are dedicated these different syntaxes used in each different verioning.
<zmatt> set_: what on earth are you rambling about now?
<set_> ...
<set_> Never mind me. I almost made sense.
<set_> C++ 11 wants their syntax this way while C++ 17 wants their syntax this way. When I have used and esp. while installing SDKs, the warnings from gnu C or C++ has these warnings from when building the SDKs.
<set_> Those warnings are what should be updated in source.
<set_> Sometimes.
<set_> that is all.
<zmatt> generally getting warnings has more to do with the compiler version than with the C++ standard version
<zmatt> but also, what does this have to do with anything?
<set_> Both actually, right?
<set_> Oh...
<set_> Nothing. Just chatting about how to update a SDK in general.
<set_> Like librobotcontrol for instance.
<Guest82> Is there a way to save this chat? I will be useful if I have to go back and check
<set_> In Bullseye, GNU-10 is around now.
<set_> So, that compiler needs specificities on the language to compile correctly.
<set_> I get why it is a compiler issue but I may never get to compiler quarks in time.
<set_> quirks. Sorry.
<Guest82> Many thanks @zmatt
<set_> Both C/C++ is long enough w/ their rules and that is outside of the compilers they use.
<mewt> guess now thta people are around I'll repost my question really quick
<set_> No!
<set_> Just kiddin'.
<mewt> When trying to boot one beaglebone, I see this in the logs:
<mewt> The other one boots fine off the same card
<mewt> Is the NIC dead? Can I do anything else to find out or mitigate without a USB UART
<zmatt> mewt: you mentioned arch linux, have you tried an official debian image?
<mewt> (I have one coming)
<Guest82> I recently started using BBB. So recommendation to get good information?
<mewt> I can do that tomorrow
<mewt> I'll report back with results I guess
<set_> Anyway...I tried to boot into a Bullseye image w/ librobotcontrol under GNU-10 and got past the warnings (luckily) but the usage is busted for now.
<set_> I cannot test all drivers while passing.
<set_> So, I will look into my stdout to file and see if i can update it.
<set_> The reason I say this is this...I got a cheap DSM2 controller. I want to use to finally get this BBBlue of the damn ground.
<set_> I started this sucka and it is not finished until the BBBlue flies!
<set_> Sorry.
Guest11 has joined #beagle
Guest11 has quit [Client Quit]
<set_> Guest82: BeagleBone Black * anything * in google
<zmatt> (and discard any results from before 2019 or so)
<set_> for instance, * anything * can be networking, there is a, and the site It has some ideas.
<set_> Yea. that cape_mgr and slots is not good any longer.
<set_> and now, sysfs is trying to go away b/c people say it is more complicated than sysfs entries. I think it will be around but that is a bit different now w/ that gpiod and character devices in Linux.
<set_> now, GPIO is like its own microcontroller.
<zmatt> ???
<Guest82> Oh okay. Make sense
<zmatt> sysfs gpio ain't going anywhere
<zmatt> sysfs in general definitely ain't going anywhere
<set_> is a form of what may work if you use python3 instead of a lib. or you can find a lib. in Python3 for the BBB.
<set_> Okay, okay.
<set_> Sheesh.
<set_> I found that years ago...and just found it again somehow.
<zmatt> why are you showing an example that involves gpio, which is not relveant for Guest82 ?
<zmatt> (and worse yet, an example for RPi rather than BBB)
<set_> Well, he can kick out the Rpi stuff.
<Guest82> I will I try to write a script to read from a sensor and definitely get back to you with questions.
<zmatt> set_: nothing in that script is relevant except "import serial"
<set_> and the GPIO is if he needs it I guess. Right!
<zmatt> he doesn't since this is a usb device
<set_> Oh.
<set_> Right.
<set_> No I/O.
<set_> Argh. But... Serial = "/dev/ttyUSB0" can be used.
<set_> Let me get the site so if he needs to direct the attention of the Rpi to the BBB, he can. This can be ported to the BBB easily and what can be erased is easy to see in his need.
<set_> This guy has a neat site for porting to the BBB but it is in Rpi stuff. Use the Serial stuff and change it to suit Python3 needs: .
<set_> ...
<set_> You can port that to using Linux serial or Python serial and the BBB.
<set_> some is relevant but you may be caught using some of it in specific instances.
<zmatt> pyserial works the same on every linux system, it doesn't matter if you're using a BBB or an RPi or a desktop linux system
<zmatt> it works exactly the same
<set_> Right. I get that...but Linux has other serial libs, i.e. not just pyserial.
<zmatt> same for any other serial lib
<set_> Okay.
<zmatt> using a usb serial device works exactly the same on any linux system
<set_> Oh.
<set_> Now I get you.
<set_> Now, you are 100% right!
<set_> so. in python3 w/ pyserial, using ser.Serial("/dev/ttyUSB0", baudrate=9600, timeout=1) is a good idea if necessary from whatever the docs. state?
<set_> And then, you can use all of the ser. functions.
<zmatt> the correct baudrate to use will depend on the device
<zmatt> whether to use a timeout (and what timeout to use) depends on how you're writing your code
<set_> Right. I barely understand time as it is now. That was just an example.
<set_> Why would I need different timeout==(n) or whatever?
<set_> sorry. timeout=(n)
<set_> for a timeout of different times?
Shadyman has joined #beagle
Guest82 has quit [Ping timeout: 256 seconds]
ketas has quit [*.net *.split]
shodan45 has quit [*.net *.split]
shodan45 has joined #beagle
ketas has joined #beagle
rob_w has joined #beagle
florian has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
Joseph has quit [Quit: Client closed]
vd has quit [Quit: Client closed]
vd has joined #beagle
Guest25 has joined #beagle
<Guest25> hi
Guest25 has left #beagle [#beagle]
vd has quit [Quit: Client closed]
vd has joined #beagle
GenTooMan has quit [Read error: No route to host]
Shadyman has quit [Remote host closed the connection]
vigneshr has joined #beagle
GenTooMan has joined #beagle
xet7 has quit [Remote host closed the connection]
xet7 has joined #beagle
rob_w has quit [Remote host closed the connection]
ikarso has joined #beagle
mattb0ne has joined #beagle
<mattb0ne> remind me again to ssh into the beagle you do not need to do anything special on PC side?
<mattb0ne> i just moved to debian 11
<mattb0ne> need to setup my connection again
<zmatt> no, normally not
<mattb0ne> do you think it is weird that the PC's network manager would not show a connection however I still have access to the internet
<mattb0ne> what is throwing me off is on debian buster (really LMDE4) it gave me that ethernet icon and said I was connected to the beaglebone or internet, I could never connect to both at the same time
<zmatt> how are you connecting the beaglebone?
<mattb0ne> i have trouble shooting these things
<mattb0ne> ethernet cable like before
<zmatt> and how are you connecting to the internet?
<mattb0ne> ethernet cable so I have a small powered router
<zmatt> why a router? did a switch not work?
<mattb0ne> so i have my modem cable into the router and one cable going to the PC and beaglbone
<mattb0ne> I can see one device on the network manager and I can browse the internet as normal
<zmatt> oh never mind I'm confusing your setup with someone else I think
<mattb0ne> I cannot ping the beaglebone at all
<zmatt> you're trying to ping beaglebone.local ?
<mattb0ne> yes
<mattb0ne> i get a time out
<zmatt> and you didn't, like, change the beaglebone's hostname from "beaglebone" to something else?
<zmatt> since you have a router, just plain "ping beaglebone" (or whatever the hostname of your beaglebone is) without ".local" should also work
<zmatt> typically
<mattb0ne> when you say hostname, this is a brand new install of an OS
<zmatt> on the beaglebone?
<mattb0ne> so I lost any setup i may have performed previously
<mattb0ne> nothing was touched on the beaglebone
<mattb0ne> just the PC
<zmatt> I'm talking about the beaglebone
<mattb0ne> yeah that has not changed
<zmatt> no setup should be needed on the PC normally
<mattb0ne> i can connect on my lap top
<mattb0ne> just this PC after putting debian 11 on it
<zmatt> did you do some minimal install that doesn't include libnss-mdns ?
florian has quit [Quit: Ex-Chat]
<mattb0ne> possibly I can check are there any other packages I would need. What is throwing me off is the internet works fine so it can communicate with stuff
<mattb0ne> just not the beagle
<zmatt> libnss-mdns is all that's needed for .local name resolution
<mattb0ne> ok
<mattb0ne> i will check that
<mattb0ne> i also tried the
<mattb0ne> and it gave me a port 22 error
<mattb0ne> debian@
<zmatt> there's absolutely no reason for that to ever work except when the beaglebone is connected _via usb_ to the pc
<rcn-ee> mattb0ne, 7.2 is only on usb... if your plugged into ethernet, it'll be what ever your dhcp gave it out..
<mattb0ne> i see
<zmatt> (beaglebone.local should work regardless of how the beaglebone is connected)
<rcn-ee> ps, another way to find it, if mnds doesn't work, install avahi-discover and then run that app on your x86 host..
<mattb0ne> ok I will try these out
<mattb0ne> can a computer see the beagle on the ethernet cable like you can when it is connected usb
<zmatt> all devices on a single ethernet network can see each other
buzzmarshall has joined #beagle
<mattb0ne> that network is formed right after you plug in or do you need to "create" the network
<zmatt> the former
<zmatt> an ethernet exists implicitly... if a computer has an ethernet port, it's on an ethernet network, albeit it might be the only device on that network (if nothing is plugged in)
<zmatt> *an ethernet network
<mattb0ne> got ya
<zmatt> two devices can form a network by connecting directly, larger networks are formed using ethernet switches. the various LAN ports on a router are typically all on an internal ethernet switch
<zmatt> an ethernet can also be extended to include wireless clients using a wifi access point
troth has quit [Ping timeout: 264 seconds]
vagrantc has joined #beagle
troth has joined #beagle
waldo323 has joined #beagle
nevets has joined #beagle
nevets has quit [Quit: leaving]
buckket has quit [Read error: Connection reset by peer]
buckket has joined #beagle
vagrantc has quit [Ping timeout: 265 seconds]
sjhill has joined #beagle
sjhill has quit [Client Quit]
Guest97 has joined #beagle
Guest97 has quit [Client Quit]
mattb0ne has quit [Ping timeout: 265 seconds]
sjhill has joined #beagle
sjhill has quit [Client Quit]
sjhill has joined #beagle
sjhill has quit [Client Quit]
sjhill has joined #beagle
sjhill has left #beagle [#beagle]
sjhill has joined #beagle
sjhill has quit [Client Quit]
sjhill has joined #beagle
sjhill has quit [Client Quit]
sjhill has joined #beagle
sjhill has quit [Client Quit]
sjhill has joined #beagle
sjhill has quit [Client Quit]
nevets has joined #beagle
nevets has quit [Client Quit]
otisolsen70 has joined #beagle
nevets has joined #beagle
nevets has quit [Client Quit]
vd has quit [Quit: Client closed]
vd has joined #beagle
mattb0ne has joined #beagle
mattb0ne has quit [Read error: Connection reset by peer]
mattb0ne has joined #beagle
<mattb0ne> zmatt: I should be able to ping the beaglebone even if I have not ssh'ed into it correct?
<mattb0ne> i get 100% packet loss with mtr
vd has quit [Quit: Client closed]
vd has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
mattb0ne has quit [Remote host closed the connection]
ikarso has joined #beagle
mattb0ne has joined #beagle
vd has quit [Quit: Client closed]
vd has joined #beagle
<zmatt> wait, so you can resolve beaglebone.local but you can't reach it?
mattb0ne has quit [Ping timeout: 250 seconds]
Guest82 has joined #beagle
russ has quit [Ping timeout: 265 seconds]
russ has joined #beagle
vagrantc has joined #beagle
russ has quit [Ping timeout: 256 seconds]
mattb0ne has joined #beagle
russ has joined #beagle
mattb0ne has quit [Ping timeout: 265 seconds]
ikarso has quit [Quit: Connection closed for inactivity]