Present indeed, but wouldn't they be a little difficult to access under the monstrous metallic mass that is the case? Forgive me if I'm wrong, but I wouldn't imagine that the ISS crew would take kindly to removing the case so that the joystick could be accessed, due to the numerous sharp insides of the Pi...Davespice wrote:The joystick and the push buttons are separate and both will be present on the flight hardware.
Will it be possible to override them, if said functionality is provided via some different route (perhaps a different key combination) in the script?Davespice wrote:The push buttons will have some default actions but this will only be for reboot and shutdown when Tim holds a button for 3 seconds. Reboot will be button B (bottom pair, right), Shutdown is DOWN, top quad bottom.
Ah, thanks much. I'd only seen the Pi in its flight case without the cap installed, and somehow had the notion of the Pi being in a position 90 degrees anti-clockwise from its actual position (hence covered by the case). My mistake.Davespice wrote:I've attached a picture of the flight unit for clarity, the little red track-point cap is the joystick.
* Writes program which buffer-overflows, overwrites the kernel in memory, installs custom hobby OS in the place of Raspian, reboots into said OS, ignores warning... *Davespice wrote:You won't be able to override the reboot/shutdown functionality from your code, that is being controlled at Kernel level.
Just remember we are going to triage all the code that is going on the flight SD cards and something like that is never going to slip throughzeta_5416 wrote:* Writes program which buffer-overflows, overwrites the kernel in memory, installs custom hobby OS in the place of Raspian, reboots into said OS, ignores warning... *
What about a script which dynamically generates itself after a given date (a.k.a. after the judging process has completed)? One could hide the OS binary or some bytecode deep down in .git/... I presume that you are giving the scripts sudo access because of the IMU sensors, so you should manage that carefully.Davespice wrote:Just remember we are going to triage all the code that is going on the flight SD cards and something like that is never going to slip through
Fair point. I shouldn't imagine that they'd be particularly pleased if anything like that slipped through...Davespice wrote:Don't underestimate the resources at the disposal of ESA and NASA
As quoted from the FAQ:jdb wrote:All the competition entries are to be in the Python language.
What programming language and version is required?
Python version 3.2 is the recommended programming language; version 2.7 is also acceptable. Bash shell scripts are also acceptable. If using C or C++, you must provide compiling instructions. Any programming language used must be compatible with the Raspberry Pi.
Certainly. I had almost considered writing mine in C++, and since the underlying RTIMUlib is written in C++ also, I would have access to the sensors - but I gave in and learnt Python instead. Haven't looked back. C/C++ is still my preferred language, but the high-level data structures in Python are extremely useful (and I did not wish to attempt to port the GPIO and PiCamera libraries, as I had not the time available to do so).jdb wrote:the ease-of-use API