I got a feeling that it will take more than that to help the ones you ran over with your truck...
Nano can do about anything a Revo can except built in telemetry.
Set it up with a GPS / INS13 / AirspeedSensor (software) module enabled so that it has some idea of airspeed or you will have to detune the PIDs a lot to avoid oscillation.
Watch out for magnetic hatch/cowl hold downs. My fixed wing GPS ship has them and I put the GPS/mag on top of the rudder.
Make sure your failsafes (RC and/or FC) are set right to at least stop the motor and hold other controls for now.
Set your AIrspeedSettings.AirspeedSensorType to GSBWE and enable the Airspeed module in System -> Settings -> HwSettings.OptionalModules
Get it flying with Manual and INS13. Recenter the Tx trims after each flight and adjust the linkages instead. It is important that the tx trims be where they were during the transmitter wizard for all modes besides Manual.
I suggest a forward CG (and a little up trim so that it climbs when you add power) and set up Manual so that it flies at a leisurely cruise speed hands off.
Then add Rate mode and tune the standard PIDs up till you get an oscillation and then back them off till it completely goes away. Rate mode should feel good, about like Manual. Personally, on my 4 channel fixed wings, I don't stabilize yaw (leave it Manual) because I presume that forces you to coordinate your turns.
Then add Attitude mode, set FixedWingPathFollowerSettings thrust limits to something like 0.3 0.4 0.5 if that is a good range (needed for waypoint and RTB), and tune FixedWingPathFollowerSettings PIDs if needed to get it flying in Attitude mode. Adjust FixedWingPathFollowerSettings PitchLimit Neutral to get a nice leasurely cruise speed at the correct pitch angle.
Beware that stabilization winds up (not good) in Manual and so switching from Manual to Attitude will go a bit crazy for a couple seconds. Go to zero throttle before switching from Manual to Attitude to work around this because the default ZeroIntegralWhenThrottleLow unwinds it when throttle is zero. Flying in Rate and switching to Attitude doesn't have this issue IIRC so that is a good way to avoid it since Rate is so similar to Manual that you can just use Rate for your base mode once you get Rate tuned.
Determine (telemetry) what your cruise speed is and set
vtolpfs FWPFS min speed and max speed equal that. Set SystemSettings.AirspeedMax and AirspeedMin to reasonable values that you should not see in gentle flight.
I suggest that you get RTB working at this point. Always have Rate or Manual on the FMS and test RTB till you are confident in it.
To do waypoint flight, you will find that you get some atti/stab overspeed underspeed errors and it will keep jumping back to the first waypoint. Adjust your
VTOLPFS FWPFS thrust limits to keep your speed reasonable and set your waypoint "error destinations" all to -1 to ignore these speed errors if you have controlled them but can't get rid of them (e.g. GPS airspeed estimation is inaccurate?) and want to continue testing.
Beware that when you set your failsafe to RTB that switching the transmitter off first can make the motor come on!
One of my future projects is to install an FC in a fixed wing as if I were a beginner who required Attitude mode from the beginning, and see if I can do it and write about it.