-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Temperature offset at pluto_temp.sh #11
Comments
Hi Manfred, First of all the temperature readings are die temperatures. Besides this the temp sensor on the AD936x TRX requires a one-point calibration, please see here: -Michael |
Hello Michael, BR |
Hello Michael, sorry to bother you again short before christmas: I read the link about one point calibration and understood this is valid for the AD936x temp readings. pluto_temp=$(iio_attr ${uri} -c ad9361-phy temp0 input) pluto is displayed as °C. Is the procedure described in the link done in the background ? So is the temp displayed already the "calibrated" temp reading ? In contradiction, the lines in the code related to the FPGA / xadc show a work work with an offset xadc_raw=$(iio_attr ${uri} -c xadc temp0 raw) xadc is dispayed as °C. So to sum up and in short words, do the both temps shown by the script represent the "correct" die temperatures will all "calibration" in it ? BR |
can i log into a pluto with putty and modify that offset? |
When using pluto_temp.sh on a version "C" there is a temperature difference shown between FPGA and Tuner of approx 20°C.
Even if the pluto is started from "cold" and massive heat-sinks are connected to FPGA and Tuner this temperature difference is shown - which seems not to be correct.
Any information to the background of this difference is highly welcome.
BR
Manfred
The text was updated successfully, but these errors were encountered: