I am trying to adapt the MLX()640 cam to the 2.4" TFT FEATHERWING. using the AMG88xx GridEYE software as an example.
I get a problem with the interpolation, my program doesn't find the following :
undefined reference to `get_point
Is there an include lib to do the interpolation?
2.4" TFT FEATHERWING AND MLX90640 software
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
- alainsam
- Posts: 200
- Joined: Tue Oct 04, 2016 7:58 pm
2.4" TFT FEATHERWING AND MLX90640 software
- Attachments
-
- MLX90640TFTDisplay.txt
- (8.22 KiB) Downloaded 2 times
-
- MLX90640TFTDisplay_output.txt
- Sketch and output
- (260.09 KiB) Downloaded 3 times
- adafruit_support_mike
- Posts: 67446
- Joined: Thu Feb 11, 2010 2:51 pm
Re: 2.4" TFT FEATHERWING AND MLX90640 software
The function interpolate_image() lives in one of the AMG88xx examples:
https://github.com/adafruit/Adafruit_AM ... nterpolate
For the MLX90640, try using the code for the breakout with a built-in display:
https://learn.adafruit.com/mlx90640-the ... g/overview
https://github.com/adafruit/Adafruit_AM ... nterpolate
For the MLX90640, try using the code for the breakout with a built-in display:
https://learn.adafruit.com/mlx90640-the ... g/overview
- alainsam
- Posts: 200
- Joined: Tue Oct 04, 2016 7:58 pm
Re: 2.4" TFT FEATHERWING AND MLX90640 software
in which directory should I put the interpolation.cpp file? It doesn't seem to work in the directory of my sketch.
- adafruit_support_mike
- Posts: 67446
- Joined: Thu Feb 11, 2010 2:51 pm
Re: 2.4" TFT FEATHERWING AND MLX90640 software
That's where any project-specific external code should live.
Do you get separate tabs for the main sketch and the interpolaton code when you open the project in the Arduino IDE?
Do you get separate tabs for the main sketch and the interpolaton code when you open the project in the Arduino IDE?
- alainsam
- Posts: 200
- Joined: Tue Oct 04, 2016 7:58 pm
Re: 2.4" TFT FEATHERWING AND MLX90640 software
Yes I have both tabs and compilation does not show any error, the monitor display the temperature values but the display stays black.
- Attachments
-
[The extension ino has been deactivated and can no longer be displayed.]
- adafruit_support_mike
- Posts: 67446
- Joined: Thu Feb 11, 2010 2:51 pm
Re: 2.4" TFT FEATHERWING AND MLX90640 software
That means things are probably working on the software side, so let's check the hardware side.
Post a photo showing your hardware and connections and we'll take a look. 800x600 images usually work best.
Post a photo showing your hardware and connections and we'll take a look. 800x600 images usually work best.
- alainsam
- Posts: 200
- Joined: Tue Oct 04, 2016 7:58 pm
Re: 2.4" TFT FEATHERWING AND MLX90640 software
I do not see any problem with the hardware tft and cam work with test software and the connections are correct...
- adafruit_support_mike
- Posts: 67446
- Joined: Thu Feb 11, 2010 2:51 pm
Re: 2.4" TFT FEATHERWING AND MLX90640 software
I don't see anything out of order there.
Drop back to the test code for the TFT Featherwing:
https://learn.adafruit.com/adafruit-2-4 ... phics-test
Does that work?
Drop back to the test code for the TFT Featherwing:
https://learn.adafruit.com/adafruit-2-4 ... phics-test
Does that work?
- alainsam
- Posts: 200
- Joined: Tue Oct 04, 2016 7:58 pm
Re: 2.4" TFT FEATHERWING AND MLX90640 software
Yes, the graphictest_featherwing example works fine.
Since I get the temperatures display for the MLX90640, I wonder if my sketch part for the interpolation is correct, but I do not see an error on it?
Since I get the temperatures display for the MLX90640, I wonder if my sketch part for the interpolation is correct, but I do not see an error on it?
- adafruit_support_mike
- Posts: 67446
- Joined: Thu Feb 11, 2010 2:51 pm
Re: 2.4" TFT FEATHERWING AND MLX90640 software
If the hardware works and the demo code works, the problem has to be in the code that doesn't work. Not seeing the error is different from knowing there are no errors.
Make a copy of the working demo code and modify that to what you're doing with the code that doesn't work. Move in small steps, and test the code after each change to make sure it works. That way any problem that makes the code stop working will always be in the latest change from a working version.
Make a copy of the working demo code and modify that to what you're doing with the code that doesn't work. Move in small steps, and test the code after each change to make sure it works. That way any problem that makes the code stop working will always be in the latest change from a working version.
Please be positive and constructive with your questions and comments.