Forum Rule: Always post complete source code & details to reproduce any issue!

Search:

Type: Posts; User: amensch

Search: Search took 0.00 seconds.

  1. Replies
    6
    Views
    506

    Problem solved: After some work with the I2C...

    Problem solved: After some work with the I2C calls & a memory dump to Garmin, they did a firmware update to get the I2C alternate addressing to work. If you wish to run dual LL3 LIDARS on a...
  2. Replies
    6
    Views
    506

    Duh. Duh. Duh.

    Duh. Duh. Duh.
  3. Replies
    6
    Views
    506

    Trying something like this... doesn't return the...

    Trying something like this... doesn't return the high and low bytes, rather I think it's hung.......getting out the o-scope.......
    ...... a little more readable.....will work on that.

    ...
  4. Replies
    6
    Views
    506

    Sorry Pete, it's just part of a much larger...

    Sorry Pete, it's just part of a much larger program not really meant to post as 'compiler ready'. The defines for UNIT_ID_HIGH, etc, are indeed insluded in a .h file, I just kept a commented out...
  5. Replies
    6
    Views
    506

    Completed (?) source for moving LidarLite to new I2C address

    Hello again All,
    More on switching Garmin LIDAR Lite I2C address... needed if you want to share two on a single I2C bus.

    I'm going to work on the assumption that the "High:48 Low:128" bytes...
  6. Replies
    6
    Views
    506

    LIDAR Lite address move

    Good Morning All!

    I'm getting two LIDAR's (Garmin Lidar Lite V3 (not HP)) together running from one Teensy 3.2. Had this working once a year back, but am having an issue getting back to where it...
Results 1 to 6 of 6