**** BEGIN LOGGING AT Thu Nov 15 03:00:00 2018 Nov 15 03:02:04 yeah Nov 15 03:02:34 Does pwm stand for 'pulse width modulation'? Nov 15 03:02:34 it's selecting manual io timing, but not actually configuring those manual iodelay values Nov 15 03:02:39 yep Nov 15 03:02:53 Do I still have to enable that if I'm not using pulse width modulation? Nov 15 03:02:59 what? Nov 15 03:03:33 are you referring to the first example I showed? it was just an example for pinmux setup in general, it has nothing to do with pru Nov 15 03:03:40 yes Nov 15 03:04:19 it works the same for every device Nov 15 03:05:40 So if I am not using pwm, do I still have to include that first part? Nov 15 03:06:03 which part? Nov 15 03:07:05 the block that has 'epwmss0 status = "okay"' Nov 15 03:07:28 uhh, no, as the comment above it says that enables a subsystem Nov 15 03:08:26 Are epwmss and ecap related? Nov 15 03:08:34 ecap is a submodule of epwmss Nov 15 03:09:19 since this is an example on setting up an ecap instance (as pwm output), both it and its parent subsystem need to be enabled Nov 15 03:10:57 Does setting up a gpio pin require any subsystems? Nov 15 03:11:26 do you actually want it configured as gpio, or as pru pin? Nov 15 03:11:32 pru pin Nov 15 03:11:48 then the subsystem it requires is (surprise!) pru :P Nov 15 03:12:49 but in general, no, most peripherals don't have a parent subsystem that needs to be separately enabled. the peripherals contained in pwmss instances are a rare exception Nov 15 03:13:54 Since the PRU are enabled by default, does that mean I just have to create a child node of the pinmux controller? Nov 15 03:17:17 I keep having IRC client annoyances Nov 15 03:17:38 and link to it using pinctrl properties on the pruss node Nov 15 03:17:54 Maybe I didn't get the part before what you just sent Nov 15 03:17:55 like my second example showed (except without using MODE_SELECT) Nov 15 03:18:21 there was no part before it, it was a reply on your "does that mean I just have to create a child node of the pinmux controller?" Nov 15 03:19:03 I lost my window, which one was the second example? Nov 15 03:20:50 That was my other session. Still here Nov 15 03:21:10 https://github.com/mvduin/py-uio/blob/master/dts/bbx15-spi-test.dtsi Nov 15 03:21:45 ahh I get why I used MODE_SELECT there but didn't set up iodelay... the desired iodelay values in this case are actually all-zero, which is the reset default Nov 15 03:21:54 jeez I should at least have added a comment about that Nov 15 03:24:56 This is exactly what I was looking for. I'll study it for a bit. Nov 15 03:25:01 Thanks again Nov 15 03:25:13 I'm about to push a cleanup patch for that file Nov 15 03:26:54 pushed Nov 15 03:28:30 (erratum i933 is another reason to configure pins in u-boot rather than DT, although it's possible the kernel uses a workaround for it... haven't checked) Nov 15 03:31:10 I misunderstood you when you mentioned configuring the pins in uboot. I thought that meant referring to the .dtb file. Are you referring to a line in uEnv.txt ? Nov 15 03:31:41 no I'm referring to board/ti/am57xx/mux_data.h in the u-boot source code Nov 15 03:32:36 So its better to do it there? Nov 15 03:33:15 see also https://github.com/dutchanddutch/u-boot/commit/3e515ed6ef4e where I disable the expansion header pinmux u-boot does by default (intended for the LCD board of the AM572x EVM) Nov 15 03:35:02 doing it there is the official recommendation because it prevents glitches (erratum i869), and iodelay can be configured without worrying about erratum i933. Nov 15 03:36:03 Is it better to configure the pins in uboot in all cases? Nov 15 03:38:01 the only downside is that it's rather inconvenient, since it requires recompiling u-boot Nov 15 03:39:57 but configuring pinmux in DT is basically only an option if your use of the pins can tolerate potential glitches during reconfiguration, and isn't timing-sensitive enough to require iodelay config Nov 15 03:40:31 if you do choose to use DT, at the very least use my patched u-boot branch to get rid of the default pinmux for the expansion header pins Nov 15 03:41:26 I'm trying to get absolute control over every clock cycle with regards to pru gpio. Does that means I should be using iodelay? Nov 15 03:42:55 the purpose of iodelay is to ensure correct timings between pins belonging to an ioset, e.g. lines that are supposed to switch simultaneously Nov 15 03:43:52 (iodelay consists of 3 programmable delay lines (one for input, one for output, one for output-enable) for every reconfigurable processor I/O pin) Nov 15 03:44:37 iirc timing adjustments done using iodelay are a few nanoseconds at most Nov 15 03:45:13 whether it matters for you depends on the application Nov 15 03:48:23 Thanks again Nov 15 03:53:22 np. pinmux can generally already be a bit of a headache, but on the am57xx it's definitely a far more complex issue than I've ever seen before Nov 15 03:55:09 (it's also pretty crazy that it has three programmable delay lines for every IO to allow software to adjust their signal timing with a resolution of a tiny fraction of a nanosecond) Nov 15 07:57:37 Hey Guys just got a few questions about BB Hardware. I hope, I'm at the correct spot to do this Nov 15 07:58:45 just ask, someone may or may not answer Nov 15 07:58:54 just ask your questions and have patience. plenty of knowledgeable people here, but usually people will only glance occasionally at irc Nov 15 08:01:25 Alright. So I try to build up an audio system using multiple channels. I should be based on the I2S protocoll. Sadly i already bought a DSP board (Hifiberry Beocreate) and I'm trying to fix the problem from Raspberry Pi. Nov 15 08:02:05 First question: Can I use multiple Channel on 1 I2s Dataline? (TDM) Nov 15 08:02:33 "from Raspberry Pi", did you mean "from BeagleBone" ? Nov 15 08:04:14 I2S has two channels, no more and no less. the protocol the DSP uses will be a similar but different audio serial protocol Nov 15 08:05:10 Noo I started with Rasp. Cause it was the recommend hardware device. But after some hours of testing and further reading, I was able to find out that the "4 Channel Amp" is only 2x2 channel (crossover). Nov 15 08:05:41 ah it uses an ADAU1451 Nov 15 08:05:51 we actually use an ADAU1452 ourselves Nov 15 08:06:21 and I can't help you with raspberry pi problems, this is obviously the wrong channel for that Nov 15 08:07:10 @zmat no I'm trying to switch to BB, because I read that it is possible to use Multiple channel with BB Nov 15 08:07:20 sure, lots Nov 15 08:07:45 so before I'm buying new stuff I just wanted to ask if this is possible ;) Nov 15 08:08:34 ugh, why is it so hard to find substantial information about this beocreate thing, instead of just marketing or quickstart stuff Nov 15 08:09:04 ah, finally something Nov 15 08:10:51 zmatt: what information do you need? its got all the funky buzzwords! Nov 15 08:10:59 @zmatt when you used the ADAU1452, how many channels did you use? And did you use BB as Slave or Master for I2S Nov 15 08:13:07 stagpa: right now only 2 channels because we don't need more at the moment, but I've had lots of variations working. I think I've tested 8 channels per data line Nov 15 08:13:24 beaglebone in slave mode (dsp provides the clock) Nov 15 08:15:09 btw I get the impression that they're not using i2s from the rpi at all Nov 15 08:15:17 Awesome :). Very good news for me. Did you use more than one Dataline or just Multiplexed the signal. Nov 15 08:15:17 it's spdif Nov 15 08:15:42 oh nm Nov 15 08:15:52 didn't look closely enough Nov 15 08:16:06 no I guess it is i2s Nov 15 08:16:26 Nop the use I2S from RPI, and use SPDIF as second input. Nov 15 08:17:14 But actually when I bought this stuff, I thought well let's connect it configure it the right way and just use 4 independet channels. Nov 15 08:18:19 so the rpi only supports i2s master mode? (since hifiberry claims they have to run the rpi through an asrc in the dsp) Nov 15 08:18:42 Yes RPI only Mastermode Nov 15 08:18:55 well that sucks Nov 15 08:19:52 ehhhh Nov 15 08:20:53 pff, okay I'm done trying to find out what interfaces they actually expose... I really wish they simply had a link to the schematic Nov 15 08:21:13 https://www.hifiberry.com/beocreate/beocreate-doc/beocreate-gpios/ is so far the best info I've found, but it's still kinda weird Nov 15 08:22:14 it does seem they have two additional input pins Nov 15 08:22:15 So happy to hear a guy/girl sharing my thoughts. Anyway... I can use the MCLK and LRCLK from the DSP and I can use the 2 Data in Lines. Yeah Nov 15 08:22:25 BCLK and LRCK Nov 15 08:22:44 Exactly. That's why I thought about using BB Nov 15 08:22:44 and yes, the BBB supports multiple data lines Nov 15 08:22:49 :) Nov 15 08:23:07 iirc the kernel limited the number of channels to 16 for some unknown reason Nov 15 08:23:42 Since I can only plug in 4 amplified channels on this board that will not be critical for me Nov 15 08:24:33 lots of channels is potentially tricky anyway, since high bitrates also means that you're more likely to run into signal integrity issues Nov 15 08:27:06 Well since I have 2 Data In Lines. I could use both, if the BB supports more than one Data Line. Nov 15 08:28:14 Since you already implemented almost the same thing I'm looking for, is it possible to get in contact with you outside of this chat? Nov 15 08:28:30 it does, up to 4 for McASP 0 (up to 2 for McASP 1) Nov 15 08:29:43 here are some notes on how the interfaces can be wired/configured: https://pastebin.com/raw/37Vr51Wr Nov 15 08:30:02 note that this describes the hardware capabilities. the linux driver does not currently support all of this flexibility Nov 15 08:30:46 (in particular, independent transmit and receive sections are not supported at the moment, although I do have a hacky patch for it) Nov 15 08:32:08 How much time did you spend to get it working? I'm new to the linux world, but there are some experienced guys I could ask Nov 15 08:32:20 get what working? Nov 15 08:33:10 and dunno anyway, I've been working with these things for a long time already Nov 15 08:34:02 Well you talked about hardware level. I don't know what the capability of the linux driver is right now. Nov 15 08:34:10 sufficient for most purposes Nov 15 08:37:14 Great. Last question is there any way to stay in touch with you? If you are already that experienced, I would love to talk about this stuff and how we maybe can help each other Nov 15 08:37:53 I'm usually here Nov 15 08:40:54 ok nice. thanks for your support. I'm going to read your notes right now and will buy my BBB right away. Nov 15 10:20:36 hi folks ... can anyone recommend a supplier for BBblue accessories in australia ? I've ordered an eduMIP from the us which has taken 3 weeks to arrive (+ exchange rate + gst are hideous :) ) Nov 15 15:02:53 can i ask something here? Nov 15 15:55:26 you already asked something, just not a very useful question ;) Nov 15 15:57:39 tip: don't ask to ask or wait for people to be active, just ask your question and have patience... usually people only occasionally glance at irc, so it can take time to get a response. if you had asked your actual question to begin with, you might have had an answer by now. :) Nov 16 01:12:36 Hi I am working with the CAN-CAPE board on the beaglebone black. And I want to send can message between two beaglebones. My question is how can I find the CAN-BUS device id? Nov 16 01:13:10 i know the command is cansend can0 xxx#xxxxxxxxx Nov 16 01:16:49 I found some help for the LoadCape. Yea! Nov 16 01:17:02 CanCape? Where did you pick that up? Nov 16 01:17:32 The CAN-CAPE is waveshare Nov 16 01:17:37 Oh. Nov 16 01:17:55 Let me look up something. Did you check the man pages? Nov 16 01:18:02 yes but i don't know how to find the device id Nov 16 01:18:15 what is the man pages? Nov 16 01:18:41 Oh...try man pages linux cansend! Nov 16 01:18:48 That may surprise you. Nov 16 01:18:51 I am in /sys/class/net/can0 but I can't find the device id Nov 16 01:18:54 The man pages are the linux manual pages. Nov 16 01:19:13 You may have to use one of linux' cmds. Nov 16 01:19:28 Let me look it up. Hold please. Nov 16 01:19:45 I am using the cmd but I need to find the can device id inorder to issue cansend command Nov 16 01:20:33 Oh! Nov 16 01:20:46 First, we need to find it! Nov 16 01:21:05 yes I am trying on the man page now Nov 16 01:21:17 Gotcha. Let me look up some cmds on the can devices. Nov 16 01:23:23 https://github.com/linux-can/can-utils may show you something valuable. I need to read more. Give me some time. Nov 16 01:23:44 ok thanks for helping Nov 16 01:24:59 https://packages.debian.org/sid/can-utils Nov 16 01:25:01 Okay! Nov 16 01:25:18 No issue. Enjoy! Nov 16 01:25:31 how do you find the can-id? Nov 16 01:25:34 Maybe some other person will come along w/ more ideas. Nov 16 01:26:05 Oh! Nov 16 01:26:19 this is not showing whereto find the can-id Nov 16 01:26:23 kar: Do you mind me helping or do you want another person to assist you? Nov 16 01:26:57 @ set_ I appreciate you helping Nov 16 01:27:11 Okay! Let me keep researching the idea. Nov 16 01:27:21 ok sure please do Nov 16 01:27:33 I do not mess w/ can all that much but I am sure I can scrounge up something. Nov 16 01:27:44 Please hold. Nov 16 01:28:59 ok Nov 16 01:29:44 try getpid Nov 16 01:29:55 Please hold. That may print out too much. Nov 16 01:30:08 bash: getpid: command not found Nov 16 01:30:15 Hmm. Okay. Nov 16 01:30:31 kar: Are you using a Debian Distro from the bbb.io people? Nov 16 01:30:47 Or Ubuntu or something? Nov 16 01:30:53 root@beaglebone:/home/debian# uname -a Linux beaglebone 4.14.49-ti-r54 #1 SMP PREEMPT Fri Jun 15 22:14:13 UTC 2018 armv7l GNU/Linux Nov 16 01:31:06 Ooh yea! Okay. Let me try on my board. Nov 16 01:31:26 Thank you very much Nov 16 01:31:39 I am going to apt install getpid and try it. Nov 16 01:32:45 sudo apt-get install getpid Nov 16 01:32:57 E: Unable to locate package getpid Nov 16 01:37:48 Okay. Nov 16 01:37:54 Back to the old ideas. Nov 16 01:38:18 I am trying this right now http://www.thomas-wedemeyer.de/beaglebone-canbus-python.html Nov 16 01:38:37 i2cset should get you some ideas. But read about it here: https://linux.die.net/man/8/i2cset. I will have to test it on my bbb first. Nov 16 01:39:10 why you are reading about I2C? Nov 16 01:40:27 I am reading about all ideas around reading devices on the BBB w/ Linux. Nov 16 01:40:46 i2c attaches your cape, right? Nov 16 01:41:06 kar: set_ is just confused as usual Nov 16 01:41:19 kar: zmatt knows more. Nov 16 01:41:28 Enjoy! Nov 16 01:41:32 I cannot wait to see the answer. Nov 16 01:42:33 I don't actually know much about can Nov 16 01:43:02 @zmat do you have an answer? Nov 16 01:43:12 have you used can-bus on BBB? Nov 16 01:43:25 Me neither! This is what makes this attempt so much fun. Nov 16 01:43:50 IDK what is wrong with my internet now Nov 16 01:44:01 with "device id" you just mean the can id? Nov 16 01:44:09 you can use anything you want Nov 16 01:44:16 yes can-id how do you find it? Nov 16 01:44:26 lsusb? Nov 16 01:44:27 no you can't Nov 16 01:44:51 the recipient can filter which id(s) it wants to receive, but afaict it defaults to receive all Nov 16 01:44:56 root@beaglebone:/sys/class/net/can0# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Nov 16 01:45:03 lsusb is irrelevant, ignore set_ Nov 16 01:45:15 I thought that might interesting. Nov 16 01:45:22 it isn't Nov 16 01:45:26 sorry, kar__. Nov 16 01:45:34 Its ok man Nov 16 01:45:53 so now @zmatt what should I try? I have both BBB connected Nov 16 01:46:04 I have candump any at one BBB Nov 16 01:46:13 how can I sent any message to it Nov 16 01:46:13 ? Nov 16 01:46:17 kar_: yeah, I'm looking at the docs, but CAN id is just something you can filter on *if you want*. by default candump should receive everything Nov 16 01:46:50 I've fiddled with CAN once, but it was quite a while ago Nov 16 01:46:58 root@beaglebone:/sys/class/net/can0# cansend can0 0x11111111 Wrong CAN-frame format! Usage: cansend - simple command line tool to send CAN-frames via CAN_RAW sockets. Usage: cansend . : #{R|data} for CAN 2.0 frames ##{data} for CAN FD frames : can have 3 (SFF) or 8 (EFF) hex chars {data}: has 0..8 (0..64 CAN FD) ASCII hex-values (optionally separated by '.') Hhahahaha! Nov 16 01:47:13 don't paste multiline output into IRC, use a paste service like pastebin.com Nov 16 01:47:37 how do I paste service link? Nov 16 01:47:43 candump [options] ! Nov 16 01:48:27 kar_: go to pastebin.com, paste your text there, click the "Create New Paste" button below the text field, paste the url of the resulting webpage here Nov 16 01:49:13 but cansend just seems to be saying what you're specified is a syntax error Nov 16 01:49:58 https://pastebin.com/2q3kFFzP Nov 16 01:50:19 ok so what is the correct syntax? Nov 16 01:50:43 ehm, it tells you, along with examples Nov 16 01:51:08 alright kar_, now we can work again. zmatt: You already know too much. Nov 16 01:51:22 ok type an example and I will try it because I tried everything I can Nov 16 01:51:32 kar_, try ' Nov 16 01:51:36 try 'em all! Nov 16 01:51:37 cansend can0 123#DEADBEEF Nov 16 01:51:44 Ha! Nov 16 01:51:49 or any other of the examples it gives Nov 16 01:53:14 so, try: candump -an option and then your interface. In that dialog, it tells what is the interface. So, you just need to pick the option(s). Nov 16 01:54:18 for interface, use the word 'any'. Nov 16 01:54:53 I sent cansend can0 123#DEADBEEF but I got nothing on the other candump Nov 16 01:55:32 Hahahah! kar_, try any instead of 123#DEADBEEF. Nov 16 01:55:34 please give me another command Nov 16 01:55:39 set_: that's not valid Nov 16 01:55:43 kar_: it works for me on a vcan interface Nov 16 01:56:08 zmatt: it says that you can use 'any' as a catch-all. Nov 16 01:56:56 so you can receive from all CAN interfaces. Nov 16 01:57:13 oh you're talking about candump Nov 16 01:57:19 I am running candump any on one device Nov 16 01:57:26 yeah, either 'any' or explicitly the interface name Nov 16 01:57:34 and I am sending cansend on another but nothing showing up on the terminal Nov 16 01:57:57 or how about: candump can_id any Nov 16 01:58:03 I am using cansend on one device and cansend on another device Nov 16 01:58:12 Okay. Nov 16 01:58:20 kar_: so probably there's a problem with the connection Nov 16 01:58:30 also be sure to double-check pinmux Nov 16 01:58:35 sorry you two. brb Nov 16 01:58:36 no there is no connection issue Nov 16 01:59:00 and you know this because...? Nov 16 01:59:02 I can show a picture if you have a website to post pictures Nov 16 01:59:41 I doubt it would be helpful Nov 16 02:00:00 I used candump and cansend on another device platform but I found the can-device ID by an accident so I used it to transfer data between the two devices Nov 16 02:00:24 sorry that makes no sense. can ids can be used freely, there's no such thing as a "device" can id on linux Nov 16 02:00:26 So if I don't have the device ID I wont be able to send any information. Nov 16 02:00:45 by default candump will show messages for all can ids Nov 16 02:02:00 @zmatt its up to you. I am telling you I used it before on another device platform Nov 16 02:02:08 only BBB don't work Nov 16 02:02:12 "it" ? Nov 16 02:02:32 I used the device id on another linux machine Nov 16 02:03:17 I'm sorry but you're confused about how CAN works on linux Nov 16 02:03:42 see https://www.kernel.org/doc/html/v4.17/networking/can.html#socketcan-concept Nov 16 02:04:14 Ok find I will keep researching. Try can communication on your BBB and if it works with the command you just send let me know Nov 16 02:04:23 I don't have a CAN transceiver Nov 16 02:05:08 which transceiver are you using, to which pins did you connect it, have you configured those pins to CAN function? Nov 16 02:05:33 I am using this https://www.waveshare.com/rs485-can-cape.htm Nov 16 02:06:09 oh god that mess Nov 16 02:06:21 at least, if it's the cape I think it is Nov 16 02:08:33 yeah this thing is awful... lemme stare at this schematic for a bit again Nov 16 02:09:13 Schematic is ok I already checked it Nov 16 02:09:34 note that this thing is not even a real CAPE, in the sense that it has no identification eeprom and therefore the pins on the beaglebone will not get configured automatically, you'll need to configure them manually Nov 16 02:10:26 https://www.waveshare.com/wiki/RS485_CAN_CAPE is something you can try. Nov 16 02:10:40 which pins? Nov 16 02:12:26 ehh, how can this thing even work? they've connected the CAN transceiver and the rs485 transceiver in parallel Nov 16 02:13:31 you'll need to ensure RSE is high (jumper between pins 2 and 3 of the RSE1 header) to disable the max485 receiver, since its RO output would interfere with CAN TX Nov 16 02:14:16 this is such a awful cape, who the hell designs something like this /o\ Nov 16 02:15:20 by you saying "which pins?" I'm assuming you haven't configured any? Nov 16 02:16:46 let me check which pins you need Nov 16 02:17:22 hey zmatt: I got some ideas from the GHI forum on the LoadCape. yea boy! Nov 16 02:17:49 Ok am I suppose to install any jumpers on the CAPE? Nov 16 02:18:09 I found this comment "Set jumper to enable UART1(RXD1, TXD1)" from https://www.waveshare.com/wiki/RS485_CAN_CAPE Nov 16 02:18:30 kar_: yeah, that is correct Nov 16 02:19:05 ok those jusmpers are pre-installed Nov 16 02:19:26 You could use sudo config-pin p9.24/26 uart! Nov 16 02:19:30 and the jumper between pins 2 and 3 of the RSE1 header? Nov 16 02:19:34 set_: shut up please Nov 16 02:19:38 Sorry. Nov 16 02:19:55 <<<< shutting up for "now!" Nov 16 02:20:36 kar_: if the jumpers are in place you need to execute the commands: config-pin p9.24 can && config-pin p9.26 can Nov 16 02:20:53 and then bring up the can1 interface (not can0) Nov 16 02:21:35 on both boards correct? Nov 16 02:21:41 yes Nov 16 02:25:24 (don't forget to configure the bitrate when bringing up the interface) Nov 16 02:26:03 okI did but sane thing Nov 16 02:26:09 nothing showing up Nov 16 02:26:20 check kernel log for errors (dmesg | tail) Nov 16 02:27:19 also, to verify the pin configuration, my show-pins utility may be useful: https://github.com/mvduin/bbb-pin-utils/#show-pins Nov 16 02:27:48 https://pastebin.com/uvuvYE5P Nov 16 02:27:56 if you install that, you can check the configuration of the P9.24/26 pins by doing e.g. sudo show-pins | grep 'P9.2[46]' Nov 16 02:28:28 k Nov 16 02:28:29 root@beaglebone:/home/debian# sudo show-pins | grep 'P9.2[46]' sudo: show-pins: command not found Nov 16 02:28:39 if you install that Nov 16 02:28:46 ^^^^^^^^^^^^^^^^^^^ Nov 16 02:29:18 (also, you can omit the sudo if you're already logged in as root) Nov 16 02:29:34 why are you doing 'cansend can0' ? Nov 16 02:29:58 @zmatt I got disconnected Nov 16 02:30:06 the cape connects to the can1 interface, the can0 interface is not used Nov 16 02:30:29 ok Nov 16 02:30:32 https://pastebin.com/raw/yT4cuKPG Nov 16 02:30:41 but even can1 don't show anything Nov 16 02:31:53 then check everything carefully. make sure all three jumpers are in place, double-check pin configuration (e.g. using my show-pins utility), make sure you configure the can interface correctly, etc Nov 16 02:32:19 how do I check the pins again? Nov 16 02:32:21 also you may want to connect a scope to the can bus to see if there's any activity happening Nov 16 02:32:35 see the chat log I just linked => https://pastebin.com/raw/yT4cuKPG Nov 16 02:33:14 sudo: show-pins: command not found Nov 16 02:33:31 I'm very very rapidly losing patience with you Nov 16 02:33:53 try actually reading Nov 16 02:33:57 what I said Nov 16 02:39:31 kar: go to that mvduin/bbb-pin-utils/#show-pins on github.com like zmatt had said. It will help him better understand the layout of your current config. Nov 16 02:39:54 You may have high when you need low or vice versa. Nov 16 02:40:07 set_: ... Nov 16 02:40:13 Oops. Sorry. Nov 16 02:40:36 I forgot. My bad, man. Please forgive me. Nov 16 02:40:45 back to the LoadCape! Nov 16 02:41:08 I mean, it's not a bad thing that you're trying to help... but it's not helpful when you're just adding confusing things to an already confused situation Nov 16 02:41:35 but I know you're just trying to help Nov 16 02:41:39 I understand completely. I know my way to help is not like an actual answer. Nov 16 02:41:58 I just help the person push further into it, i.e. basically. Nov 16 02:42:28 For instance...why stop here when right around that corner is something 50 x's more difficult? Nov 16 02:42:55 kar just needs to check everything. many things all have to be right for the can communication to work Nov 16 02:43:16 and I do remember it being pretty fickle Nov 16 02:43:16 Oh. Nov 16 02:43:35 but it does work when everything is configured right Nov 16 02:44:01 I understand that you come to a conclusion on items that you are already familiar w/. I like to work and work and work. Nov 16 02:44:22 ongoing vs. means-to-an-end? Nov 16 02:45:01 Anywho? I am about to run my first program w/ the LoadCape. Nov 16 02:45:07 brb Nov 16 02:45:22 I cannot wait to see you two make things work! Nov 16 02:45:35 CAN! Nov 16 02:48:22 kar: if you have access to a scope, then checking the electrical signals is obviously also a good idea, to figure out on which side it's going wrong Nov 16 02:49:19 also: There is a CommsCape that handles CAN. Sorry. That is all. Nov 16 02:50:00 people also just cobble something together themselves => https://www.instructables.com/id/DIY-Beaglebone-CAN-Bus-Cape/ Nov 16 02:50:46 (this guide is more specific to sniffing a car's CAN bus though) Nov 16 02:52:47 (and it's rather old, so it uses an overlay rather than config-pin) Nov 16 02:57:58 That CommsCape is supposedly the BBB.io Cape of Capes for now. I bet there will be revisions. **** ENDING LOGGING AT Fri Nov 16 02:59:58 2018