Since I couldn’t find any frequency hopping example online, I tried one on my own and it works.
For those who don’t know what is Frequency Hopping see this Frequency Hopping .It is a nice feature for secure communication.FHSS is unhackable (though it also depends on how randomly you change the frequencies )
I have tried Frequency (Channel) Hopping with the Auto Acknowledgement feature of nrf24l01 so that I can change the frequencies on both Tx and Rx devices in synchronism. Sometimes there is a loss of synchronism (possible “different” latencies of the mcus [atmega328p] ).In that case, I manually set them using Serial of Arduino IDE.
In the given example I am sending a 32-byte array of data and hopping linearly between channels 90 and 125 (back and forth with an increment of 2 ) each new array of data is Transmitted on a different channel (frequency). Continue reading “Frequency Hopping with NRF24l01+”→
Motion Processing is an important concept to know if you want to interact with real time data you should be able to interact with motion parameters such as Linear acceleration, Angular acceleration, Magnetic North of the planet with a reference point on the object.
Yes! the Real time position of any celestial body can be calculated using some parameters called Orbital Elements (or Osculating Elements or Keplerian Elements). These are the parameters that define an orbit at a particular time.
Inclination (i)angle between the plane of the Ecliptic and th
e plane of the orbit.
Longitude of the Ascending Node (o)states the position in the orbit where the elliptical path of the planet passes through the plane of the ecliptic, from below the plane to above the plane.
Longitude of Perihelion (p)states the position in the orbit where the planet is
closest to the Sun.
Mean distance (a)the value of the semi-major axis of the orbit – measured in Astronomical Units for the major planets.
Daily motion (n)states how far in degrees the planet moves in one (mean solar) day. This figure can be used to find the mean anomaly of the planet for a given number of days either side of the date of the elements. The figures quoted in the Astronomical Almanac do not tally with the period of the planet as calculated by applying Kepler’s 3rd Law to the semi-major axis.
Eccentricity (e)eccentricity of the ellipse which describes the orbit.
Mean Longitude (L)Position of the planet in the orbit on the date of the elements.source:2
This project aims to make a system that effectively tracks celestial bodies (such as planets ) with a fair amount of accuracy. We will be using some algorithms along with a processing unit for the calculations and a servo mechanism to show the location of the planet physically!. The hardware used in the project is pretty much basic and simple because the primary focus of this project is the software that is to make people understand the algorithms and their implementations. So please bear with my “un-formatted” hardware.
Not just planet tracking you will learn some additional important things that you can implement in your other projects:
Planet tracking using Kepler’s algorithms
Many coordinate systems and their interconversion
pan-tilt programming and servo mapping (3.5 turns Servo and 180 degrees Servo )
MPU9250 auto-calibration programming
Using Madwicks/Mahony Filter to Stabilise MPU readings.