Search results

  1. B

    Early CAN packets not rec'd by IFCT on Teensy 3.2

    First message after bootup is lost. I can create other scenarios where the first *few* messages are lost after bootup. In all cases, once things start working, they seem to stay working.
  2. B

    Early CAN packets not rec'd by IFCT on Teensy 3.2

    The setup code for IFCT is: Can0.begin(baudrate); // baudrate is 1000000 Can0.enableFIFO(); Can0.enableFIFOInterrupt(); Can0.intervalTimer(); The relevant code which write/reads to the CANbus is: union frame_id_t { struct { uint8_t object_address; uint8_t destination_id...
  3. B

    Early CAN packets not rec'd by IFCT on Teensy 3.2

    Greetings. I am running IFCT on a 3.2 on Arduino 1.8.8. I am talking to a KDE DirectESC (an Electronic Speed Controller, or ESC) over the CAN bus. I can query the state of the ESC using CAN, and I do so. My app is simple: write a CAN packet which queries some trivial state on the ESC, call...
  4. B

    cannot read exteneded CANBus frames in FlexCAN

    I am now using the IFCT library. It's Good Stuff as it works for receiving extended frames. Thanks for the pointer. However, it strikes me as odd that, in order to receive extended frames using IFCT, I need to invoke the following methods at setup() time: enableFIFO() enableFIFOInterrupt()...
  5. B

    cannot read exteneded CANBus frames in FlexCAN

    Greetings. I am running a pair of 3.2's using CollinK's latest FlexCAN implementation. I can, between these two 3.2's, exchange standard CANbus frames all day long. Both sides can happily read and write such frames. But...when I write an extended frame, well, the writing 3.2 happily writes it...
  6. B

    Teensy 3.2/3.6 USB port unresponsive

    I did perform a bright light/magnifier-glass examination and *voila* there is visible damage to the on-board USB connector. In the future, in our system, we will forego the provided surface-mount USB connector, and use the pads on the Teensy to cobble together a pigtail connector so that there...
  7. B

    Teensy 3.2/3.6 USB port unresponsive

    defragster - I understand your points well. The key phrase in your post for me is "non-abused Teensy". I suspect my Teensy's were abused in my embedded environment...but I don't know for sure and, if they were, I don't know how. In an effort to reduce the probability that such abuse will occur...
  8. B

    Teensy 3.2/3.6 USB port unresponsive

    Paul - thanks for that...quite interesting. But, unfortunately for this discussion not as relevant as one might think. The cable I am using to talk to the "failing" Teensy's is the same cable I am using to speak to "working" Teensy's. In this case, "working" means I can program the Teensy. The...
  9. B

    Teensy 3.2/3.6 USB port unresponsive

    Fair enough...except that I cannot program either Teensy device from the IDE, yet both devices seem to come up and run just fine. So it appears the USB link is non-functional in some way. I am wondering if others have seen this behavior before and, even more interesting, what failure modes, or...
  10. B

    Teensy 3.2/3.6 USB port unresponsive

    "Shows a USB device" means that the Ports section of Devcie Manager shows something like the "USB Serial Device" entry in the following: If Device Manager does not show such a line, the Arduino IDE will not download code onto the Teensy. I have pressed the Teensy button; it does not help...
  11. B

    Teensy 3.2/3.6 USB port unresponsive

    Greetings. I have a 3.2 Teensy and a 3.6 Teensy which both worked fine out of the box...and then didn't. The 3.2 is now in a state where, when first connected via USB to a PC, briefly shows a USB device in Device Manager. Then the port disappears after a few seconds. The 3.2 seems OK (its LED...
Back
Top