**** BEGIN LOGGING AT Mon Apr 22 03:00:09 2019 Apr 22 12:18:41 http://iplogger.info/2GZLg5.jpeg Apr 22 16:29:25 well that is ominous... why is someone trying to harvest IP addresses of users here Apr 22 16:44:53 I bet it's a psychotic person unsastisfied with answers to their questions Apr 22 16:45:02 so they decided to hunt us Apr 22 16:49:17 it happened to me like twice Apr 22 16:49:26 one of them found my name, postal address, school, etc Apr 22 16:49:49 so I did the most rational thing, I insulted him and stopped responding; but nothing happened Apr 22 17:38:55 I am totally new to CAN communication. I have Trinamic TMCM-6212 controller. I am totally fluent in talking to it over USB using Windows. Now I cannected it to BBB using Comms cape. It uses can1. I am trying to get some life out of Trinamic using cansend command. I need to specify the Trinamic CAN ID. How can I find it? Is there a way to querry all the can devices on CAN bus? Apr 22 18:25:21 dreamhiker2: CAN does not have device discovery... CANopen should at least allow you to notice that the device exists and what its node id is, since it will announce its presence at startup Apr 22 18:26:39 maybe try https://github.com/CANopenNode/CANopenSocket Apr 22 18:27:26 or first just try candump Apr 22 18:30:35 looks like the CANopen "electronic datasheet" (which the CANopen stack needs to understand how to talk to your device) is included with the firmware download Apr 22 19:07:45 Is there a way to read the Object dictionary to query the ID? Apr 22 19:10:16 I don't really know anything about CANopen other than what I read in about 5 minutes Apr 22 19:11:07 Actually, using Trinamics IDE, I can see that I can change "CAN Send ID" and "CAN Receive ID". But I am not sure this is the ID that I need to use with cansend. Apr 22 19:11:33 but what you're saying sounds to me like it makes no sense, since I'm pretty sure you need the node id to query anything... but like I said, it should broadcast it on startup Apr 22 19:11:38 that sounds weird Apr 22 19:12:02 I am conected to TMCM-6212 over usb Apr 22 19:12:37 my impression is that a node simply has a node id... having separate "send" and "receive" ids sounds nonsensical to me Apr 22 19:13:17 Yes, agree. I do not see to IDs in the CAN description Apr 22 19:13:52 I'm assuming you're using the CANopen Firmware? since that's the first thing I saw with CAN in the name on their site Apr 22 19:14:44 https://pasteboard.co/ Apr 22 19:14:58 No, I am using TMCL firmware Apr 22 19:15:54 Sorry: https://pasteboard.co/Ibm394g.png Apr 22 19:15:57 oh, then no idea Apr 22 19:16:02 check the documentation? :P Apr 22 19:16:23 Checked it already :( Apr 22 19:16:50 Just a question: is there a way to query all the can devices on the can bus? Apr 22 19:17:28 I already answered that Apr 22 19:17:55 20:25 < zmatt> dreamhiker2: CAN does not have device discovery... CANopen should at least allow you to notice that the device exists and what its node id is, since it will announce its presence at startup Apr 22 19:18:48 so with the CANopen firmware you should be able to detect the device, with the TMCL firmware no idea, probably not but depends on what the protocol looks like obviously Apr 22 19:19:01 where do I read this announcement? Apr 22 19:19:20 it would show up in candump for example Apr 22 19:19:34 Thanks! Apr 22 19:21:17 the message format for the TMCL firmware is in the TMCL firmware manual btw, sections 3.1 and 3.2 Apr 22 19:22:39 and for that it indeed makes sense that you need to configure separate can identifiers for command and reply Apr 22 22:07:40 I had a c program running on debian 8.2 and now upgrading to debian 9.5 I am finding many issues like gpio configuration does not work and uart2 does not work. I am finding contradicting information on web about how to deal with changes. What do I need to do to get UART2 working? Apr 22 22:11:34 john__: the simplest is to just use config-pin to configure the pins to uart mode Apr 22 22:11:43 the uart device (/dev/ttyS2) should already exist by default Apr 22 22:14:17 alternatively, using an overlay (i.e. BB-UART2-00A0.dtbo) is also still supported. there are a bunch of variables in /boot/uEnv.txt to specify overlays to be loaded (uboot_overlay_addr4..7 and dtb_overlay are the preferred variables for that use) Apr 22 22:15:59 this has the benefit that the pins are automatically configured correctly during early boot, whereas "config-pin" is not persistent and needs to be done again after every reboot Apr 22 22:17:30 it's also fairly easy to do what config-pin does in your own software (it's just a matter of writing the appropriate value to the appropriate sysfs attribute for each pin) **** ENDING LOGGING AT Tue Apr 23 02:59:57 2019