Search the Community

Showing results for tags 'can'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Test and Measurement
    • Measurement Computing (MCC)
    • Add-on Boards
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions
    • Archived

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 7 results

  1. I am trying to use the PmodCAN module together with PetaLinux on the ZedBoard, to display a CAN interface within the OS. So far I can make it show up in the interface overview with the following device tree overlay: /* <petalinux-project-root>/project-spec/meta-user/recipes-bsp/device-tree/files/system-user.dtsi */ /include/ "system-conf.dtsi" / { osc: can_osc { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <20000000>; }; }; &gpio0 { #interrupt-cells = <2>; interrupt-controller; }; &spi1 { is-decoded-cs = <0>; num-cs = <1>; status = "okay"; spidev@0x00 { compatible = "microchip,mcp25625"; spi-max-frequency = <10000000>; clocks = <&osc>; interrupt-parent = <&gpio0>; interrupts = <0 0x2>; reg = <0>; } }; I can even send and receive messages using `candump` and `cansend`, but the interface behaves strange together with some CAN libraries. E.g. Messages are sometimes not sent, when the library tries to send multiple messages without any delay between them. On the other hand, when I connect the PmodCAN to a RaspberryPi and use same said libraries, everything works fine. So the only difference I can see between the working Raspberry Pi and the "strange" behaving Zynq setup, is the manually defined device tree overlay you see above. Long story short: Is my device tree overlay for the PmodCAN correct, to use it together with the ZedBoard on the JE Pmod connector? Maybe there is even a template somewhere? Based on the issues I have, I suspect something might be wrong with the clock and frequency definitions ...
  2. Hi, I am currently working with the PmodCAN module and I am trying to make it work inside a bigger design with other AXI IPs. Unfortunately I can not find any documentation about the PmodCAN Vivado IP and the AXI address space. So I have some questions: 1. It is not clear to me, what the use case of the `AXI_LITE_GPIO` interface is. From what I can see, the PMOD interface is pre-defined to be used for the SPI communication with the MCP25625 IC; other SPI PMODS doesn't seem to need it either. I have the suspicion that some of the MCP25625 Pins can be configured as GPIOs in some way, but anything I thought would make sense, does not match with your provided C code examples. Which brings me to my second question. 2. Is there any documentation about the AXI address space and how to use it to configure, send and receive messages? I am currently trying to understand how the IP works by looking at the signals and the VHDL code. Unfortunately this approach is very time consuming and I could get things done much faster, if there is any documentation about the address space. Maybe I am just overlooking something here. To summarize, I would like to ask, if the intention behind the Vivado IP was primarily for demo purposes to use it from C code or not; should I rather implement my own IP to let it directly communicate with other AXI IPs?
  3. Hello, Just bought a DMC60c and trying to get started. I am not using it with FIRST or robot controls, I want to use a CAN message to control a DC motor. I confirmed the DMC60c works with PWM input. I am now trying to get CAN communication working. I am in the automotive industry, I am using ATI Vision with a KVaser Leaf Light to send CAN messages. From the Documentation it looks like I should send 0x00000240 as a 29bit identifier. I am sending the message, but DMC60C is alternating flashing Red lights indicating it doesn't see CAN. To confirm there is CAN I have a Vector VN1630 which I am monitoring the CAN network with it sees the message is being sent. I attached a block diagram of the layout I have. I assume I must misunderstand what or how to send the message to the DMC60c. Also attached is a screen shot of the message I am sending. I have tried sending messages with 4 and 8 bytes of data, sending all 0's and with Device Type 2 and Manufacturer Encoding 6. Anyway I send I get no indication the DMC60C acknowledges any CAN message. Any help would be greatly appreciated. Thanks
  4. I am able to capture a CAN message using the logic analyzer with a "Simple" trigger of falling edge on the TX line (polarity low), but have not succeeded in triggering using the "Protocol" trigger. Attached is a screenshot of a transmit capture using "Simple" and the waveform looks correct. However when I use the attached "Protocol" settings, the analyzer never triggers. What am I missing?
  5. I have one of the older Cerebot boards which should be equivalent to the Diglent Pro MX7 Embedded Systems Trainer Board that is currently for sale. I would like to capture CAN traffic using an Analog Discovery module and Waveforms software. I have two basic questions. After studying related posts on this forum, I get the strong sense that Analog Discovery and Waveforms software are better suited for connecting to the "PIC side" of the transceivers (RX and TX), rather than CAN side, where CANH and CANL are differential signals. (1) Is this correct? After studying the Cerebot schematic and reference manual, it appears that I can't directly connect to RX and TX for either CAN1 or CAN2. However, it appears that if I short together all of three pins of JP1 and all three pins of JP2, then the RX and TX of CAN1 will be available on pins 1 and 4 of connector JF. As far as I can tell, shorting all three pins together will not create an electrical short, as nothing on the board is driving the outside pins of JP1 and JP2. (2) Is this correct? Thanks!
  6. opethmc

    DMC60c CAN Bus

    I am looking at the DMC60c CAN protocol guide and also the software API reference manual. What are the API numbers needed in the CAN message to communicate with the DMC60c. For example if I wanted to send a voltage command using the function driveVoltage, what should go in the API field (Byte 1) of the message identifier? Thanks, matt
  7. Hello, I am using a couple of DMC60C with an NI-XNET USB 8502. I have had some good luck but am running into a very specific question. The control message: 0x02060000 Uses a signed 24-bit integer for both closed loop velocity and closed loop position control setpoints. However, the makeup of that value is only loosely described in the documentation. My questions are: 1) is the byte order as shown in the manual correct? It appears strange to go trgtH in byte 3, targtL in bye 4, and trgtM in byte 5. I could understand H, M, L or L, M, H but it seems oddly shuffled as presented. 2) is a negative 24 bit value stored as 2's complement? Thank you for any advice. My motor does not appear to like the values I have been sending for velocity control mode. Sincerely, Brian