Actions

Difference between revisions of "MIPS"

From Unofficial Stationeers Wiki

(Examples)
(Add info about batch read with no devices)
 
(64 intermediate revisions by 25 users not shown)
Line 1: Line 1:
 
[[Category:MIPS Programming]]
 
[[Category:MIPS Programming]]
 
=MIPS scripting language for IC10 housings / chips=
 
=MIPS scripting language for IC10 housings / chips=
 +
MIPS is [[Stationeers]]' in-game scripting language. It runs on [[Integrated Circuit (IC10)|IC10 chips]] crafted at the [[Electronics Printer]].
 +
 +
==Registers==
 +
Internal registers '''r?''': The IC contains 16 CPU registers, numbered '''r0''' to '''r15'''. From now on referred to as '''r?'''.
 +
 +
Device registers '''d? logicType''': Device registers are written to and from the IC. A device register is numbered '''d0''' to '''d5''' (select via screw), or '''db''' (connected device). From now on referred to as '''d?'''.
 +
 +
=== Logic and algorithmic with '''Internal registers''' ===
 +
All calculations are exclusively performed to and from '''r?''' registers, or generally more understood as variables in programming. You can use aliases to give convenient names with the <code>alias string r?|d?</code>command (see below).
 +
 +
Internal registers can be manipulated in various ways.
 +
* Write constant values <code>move r? (r?|num)</code>: Example: <code>move r0 2</code> sets r0 to the number 2.
 +
* Calculate: Calculations are done to- and from these registers, like <code>add r? a(r?|num) b(r?|num)</code>. Example: <code>add r1 r0 3</code> adds 3 to r0, and writes to r1.
 +
 +
Note, for any kind of if statements or loop behaviours, knowing about labels, branching, and jumps is essential knowledge. See below.
 +
 +
=== IO to '''Device registers''' ===
 +
Acronym '''d?''' stands for device, where ? is a number corresponding to the screw device selector on the socket.
 +
You can also read/write to the device where the IC is planted in using device '''db'''.
 +
 +
Generally, there are up to 6 devices which can be set using the screwdriver '''d0''' to '''d5'''. A special device register '''db''' is the device wherever the IC is mounted upon. Very convenient for atmospheric devices where no separate IC socket is required.
 +
 +
Note, the IC is completely unaware where d? is actually connected to. So if you get a logicType error, check d? number, or check if the screw has been set opn the socket. An alias is only convenient to convey what is expected to be set on the d? screw, it does not actually set or program the screq.
 +
 +
* Read from device (load) <code>l r? d? logicType</code>: Reads logicType, like Pressure from a [[Sensors|gas sensor]], from device d? to register r?. Values can be read from connected devices and put into the register using the '''l''' (load) command. For example, if you want to load the state of a door. <br> Example: <code>l r0 Door Open</code> reads the 'Open' field of an object named 'Door', that would be connected to the IC housing of the chip.
 +
* Write to a device (set) <code>s d? logicType r?</code>: Write a value from a register back to a device using the command <code>s d? logicType r?</code>. For example, if d0 is set to a door using the screwdriver, <code>s d0 Open 0</code> sets the 'Open' status of the d0 (a door) to 0, effectively closing the door.
 +
 +
=== batch IO to - '''Device registers''' ===
 +
'''Batch writing''' needs to be done to a specific '''deviceHash''' instead of d?. Is unique per device type, which you can find in the [[Stationpedia]] entries.
 +
* <code>lb r? deviceHash logicType batchMode</code>
 +
* <code>sb deviceHash logicType r?</code>
 +
Additionally, using the following batch commands, a '''nameHash''' can be provided to only modify devices with a certain name.
 +
* <code>lbn r? deviceHash nameHash logicType batchMode </code>
 +
* <code>sbn deviceHash nameHash logicType r?</code>
 +
 +
'''batchMode''' is a parameter equal to 0, 1, 2, or 3. These are also defined as the constants '''Average''', '''Sum''', '''Minimum''', and '''Maximum''' respectively. The word or number can be used.
 +
 +
Combining one of these functions with the <code>HASH()</code> function can be advantageous:
 +
 +
<code>lbn r0 HASH("StructureGasSensor") HASH("Sensor 1") Temperature Average</code>
 +
 +
This code will load the average temperature of all gas sensors on the network named "Sensor 1" onto register '''r0'''
 +
 +
If the batch read (lb/lbn) is done on a network without any matching devices the results will be as specified in the table:
 +
{| class="wikitable"
 +
|+ Batch read with no devices
 +
|-
 +
! Batch Mode !! Result
 +
|-
 +
| Average (0) || nan
 +
|-
 +
| Sum (1) || 0
 +
|-
 +
| Minimum (2) || 0
 +
|-
 +
| Maximum (3) || ninf
 +
|}
 +
 +
=== Examples ===
 +
 +
Here are some examples demonstrating all three operations:
 +
 +
<code>move r0 10</code><br>Sets register '''r0''' to the value 10
 +
 +
<code>move r0 r1</code><br>Copies the value of register '''r1''' to register '''r0'''
 +
 +
<code>l r0 d0 Temperature</code><br>Reads the Temperature parameter from device '''d0''' and places the value in register '''r0'''.
 +
Note: not all devices have a Temperature parameter, check the in-game stationpedia.
 +
 +
To set a device specific value (like '''On'''), you can write into this value.
 +
 +
<code>s d0 On r0</code><br>Writes the value from register '''r0''' out to '''On''' parameter of device '''d0'''. In this example the device will be turned On, if valve of register r0 equals 1, otherwise (register r0 equals 0) it will turned off. See section [[MIPS#Device_Variables|Device Variables]].
 +
 +
It's recommended to use labels (like: ''someVariable'') instead of a direct reference to the register. See '''alias''' in section [[MIPS#Instructions|Instructions]].
 +
 +
=== Special registers ===
 +
There are two more registers. One called '''ra''' (return address) and one called '''sp''' (stack pointer). The '''ra''' is used by certain jump and branching instructions (those ending with '''-al''') to remember which line in the script it should return to. The '''sp''' tracks the next index within the stack (a memory that can store up to 512 values) to be pushed (written) to or popped (read) from. Neither '''ra''' or '''sp''' is protected, their values can be changed by instructions like any other register.
 +
 +
==Stack Memory==
 +
;push r?: adds the value of register '''r?''' to the stack memory at index '''sp''' and increments the '''sp''' by 1.
 +
;pop r?: loads the value in the stack memory at index <code>sp-1</code> into register '''r?''' and decrements the '''sp''' by 1.
 +
;peek r?: loads the value in the stack memory at index <code>sp-1</code> into register '''r?'''.
 +
 +
As mentioned previously, '''sp''' can be both written to and read from any time. When reading ('''peek''' or '''pop'''), '''sp''' must be between 1 and 512, inclusive. While writing ('''push'''), '''sp''' must be between 0 and 511, inclusive.
 +
 +
Stack memory is persistent on logic chips. This means that if you have a logic chip and push values to the stack, the code that pushes those values can be removed and the stack will retain those values.
 +
 +
Note that this does not carry over to any other logic chips which receive the program of the original; They will need to have their stack memories programmed individually.
 +
 +
'''Stack Traversing'''
 +
 +
Traversing the stack can be done similarly to how an array would be traversed in some other languages:
 +
<blockquote>
 +
<nowiki />#this will traverse indices {min value} through {max value} - 1
 +
 +
move sp {min value}
 +
 +
 +
loop:
 +
 +
add sp sp 1
 +
 +
peek r0
 +
<nowiki />#do something here with your stack values (loaded into r0)
 +
 +
blt sp {max value} loop
 +
 +
 +
<nowiki />#continue on
 +
 +
</blockquote>
 +
 +
Alternatively, you can use the pop function's decrementing to make a more efficient loop:
 +
 +
<blockquote>
 +
move sp {max value}
 +
 +
add sp sp 1
  
<pre>
 
# Text after a # will be ignored to the end of the line. The amount of white
 
# space between arguments isn't important, but new lines start a new command.
 
</pre>
 
  
==Registers==
+
loop:
The IC contains 16 registers, numbered r0-r15. Think of these as variables in other programming languages. In fact, you can name them with the alias command (see below).
 
  
To set a register directly (such as r0=2), use the <b>move</b> command. To read a value from a device, use l (load). To write a value back to a device, use s (set). Note that
+
pop r0
like most machine languages, the <i>destination</i> goes first, so instructions always look like: action destination source.
 
  
There are two more registers. One called ra (return address) and one called sp (stack pointer). The ra is used by certain jump and branching instructions (those ending with -al) to remember which line in the script it should return to. The sp tracks the next index within the stack (a memory that can store up to 512 values) to be pushed (written) to or popped (read) from. Neither ra or sp is protected, their values can be changed by instructions like any other register.
+
<nowiki />#do something here with your stack values (loaded into r0)
  
<code>move r0 10</code><br>Sets r0 to the value 10
+
bgt sp {min value} loop
  
<code>move r0 r1</code><br>Copies the value of r1 to r0
 
  
<code>l r0 d0</code><br>Reads from device 0 and places the value in r0
+
<nowiki />#continue on
  
<code>s d0 r0</code><br>Writes the value from register 0 out to device 0
+
</blockquote>
  
 
==Device Ports==
 
==Device Ports==
ICs can interact with up to 6 other devices via d0 - d5, as well as the device it's attached to via db. To change or set a device, use a screwdriver and adjust the device in the IC housing. You can read or set any of the device's properties, so it is possible to do things like read the pressure and oxygen content of a room on the same Device port.  
+
ICs can interact with up to 6 other devices via d0 - d5, as well as the device it's attached to via db. To change or set a device, use a screwdriver and adjust the device in the IC housing. You can read or set any of the device's properties, so it is possible to do things like read the pressure or oxygen content of a room on the same Device port.
 +
 
 +
Additionally, is possible to set other IC housings as devices, allowing you to create programs that run across multiple ICs together. For example, an Gas Mixing IC could check the ''' Setting'''  field of a Atmosphere Sensor IC and act based on the value of the sensor chip.
  
The l (load) and s (set) instructions let you read and set values on a device.
+
The '''l''' (load) or '''s''' (set) instructions you have to read or set these values to your device. Examples:
  
<code>l r0 d0 Temperature</code> #Reads the temperature from an atmosphere sensor into r0.
+
<code>l r0 d0 Temperature</code> #Reads the '''Temperature''' from an atmosphere sensor at device port '''d0''' into register '''r0'''.
  
<code>s d1 Setting r0 </code> # Writes r0 to the device on port 1 to the Setting variable.
+
<code>s d1 Setting r0 </code> # Writes the value of the register '''r0''' to the device on port '''d1''' into the variable '''Setting'''.
  
 
==Labels==
 
==Labels==
Lables are used to make it easier to jump between lines in the script. The label will have a numerical value that is the same as its line number. Even though it's possible to use a labels value for calculations, doing so is a bad idea since any changes to the code can change the line numbers of the labels.
+
Labels are used to make it easier to jump between lines in the script. The label will have a numerical value that is the same as its line number. Even though it's possible to use a labels value for calculations, doing so is a bad idea since any changes to the code can change the line numbers of the labels.
<br><code>main:</code>
+
 
<br><code>j main</code>
+
<br><code>main:</code> # define a jump mark with label '''main'''
 +
<br><code>j main</code> # jumps back to '''main'''
  
 
==Constants==
 
==Constants==
Instead of using a register to store a fixed value, a constant can be made. Using this name will refer to the assigned value.
+
Instead of using a register to store a fixed value, a constant can be made. Using this name will refer to the assigned value. With the help of Constants you can save register places.
<br><code>define pi 3.14159</code>
+
<br><code>define pi 3.14159</code> # defines a Constant with name '''pi''' and set it's value to 3.14159
<br><code>move r0 pi</code>
+
 
 +
You can use these constants like any other variables (see: alias in section [[MIPS#Instructions|Instructions]]). Example:
 +
<br><code>move r0 pi</code> # set the value of register '''r0''' to the value of constant named '''pi'''.
  
 
==Indirect referencing==
 
==Indirect referencing==
This is a way of accessing a register by using another register as a pointer. Adding an additional r infront of the register turns on this behaviour. The value stored in the register being used as the pointer must be between 0 to 15, this will then point to a register from r0 to r15, higher or lower values will cause an error.
+
This is a way of accessing a register by using another register as a pointer. Adding an additional r in front of the register turns on this behaviour. The value stored in the register being used as the pointer must be between 0 to 15, this will then point to a register from r0 to r15, higher or lower values will cause an error.
  
 
<code>move r0 5</code> stores the value 5 in r0
 
<code>move r0 5</code> stores the value 5 in r0
Line 57: Line 173:
 
<br><code>s dr0 On 1</code> is now the same as <code>s d2 On 1</code>, r0 has the value 2 so dr0 points at d2
 
<br><code>s dr0 On 1</code> is now the same as <code>s d2 On 1</code>, r0 has the value 2 so dr0 points at d2
  
==Debugging advice==
+
==Network Referencing / Channels==
The value stored in a register can easily be seen by writing it to the Setting parameter of the IC housing, this has no sideeffects, too see the value just stand close and look directly at the housing (<code>s db Setting r0</code>).
 
<br>To check if a certain block of code is executed, use the above trick but with a number that you choose, like the line number (<code>s db Setting 137</code>).
 
<br>The configuration card can be used to manually check the data values stored in all connected devices.
 
  
==What a typical program looks like==
+
All cable networks have 8 Channels which can have data loaded from/stored to via a device and connection reference. Connections for each supported device are listed in the stationpedia. All 'connections' a device can make are a connection (pipe, chute, cable), but only cable networks have channels.
A program is usually written to be a long continuous loop, that compares values to determine what to do next, sometimes it jumps out of the main loop to do a task before returning back to it. The <code>yield</code> instruction will force the program to wait to the next game tick, so the rest of the game can keep running, but the game is smart enough to force programs to take breaks to prevent them from freezing the entire game if <code>yield</code> is missing. The <code>beq</code> means "branch (jump) if equal" and compares two numbers.
+
 
 +
The 8 channels (Channel0 to Channel7) are however volatile, in that data is destroyed if any part of the cable network is changed, removed, or added to, and also whenever the world is exited. All these channels default to NaN. Strictly speaking, they default to what we would call "quiet NaN", in that its not an error it simply means its not a number yet. Recommend you use these channels for reading and writing between networks, rather than as a data store. This effectively means an IC can read all the networks for all devices to connected to it, so not just their own local network, but any networks any device they can reference is connected to.
 +
 
 +
<br><code>l r0 d0:0 Channel0</code> d0 is device zero, and the :0 refers to that device's 0 connection
 +
 
 +
For example: on an IC Housing, the 0 connection is the data port and 1 is power, so you could write out r0 to Channel0 of the power network of the Housing using <code>s db:1 Channel0 r0</code>
 +
 
 +
==Comments==
 +
Comments can be placed using a '''#''' symbol. All comments are ignored by the game when it reads commands. Below is an example of valid code with two comments.
 +
 
 +
<code> alias MyAlias r0 # Text after the hash tag will be ignored to the end of the line. </code> <br>
 +
<code> # You can also write comments on their own lines, like this. </code>
 +
 
 +
==Debugging advices==
 +
The value stored in a register or variable can easily be displayed by writing it to the Setting parameter of the IC housing. This has no side effects. To see the value, just stand close to the IC housing and look directly at the housing.<br>
 +
<code>s db Setting r0</code>. # sets/writes the value of register '''r0''' into the parameter '''Setting''' of the IC Housing('''db''')
 +
 
 +
To check if a certain block of code is executed, use the above trick but with a random number that you choose, like the line number.<br> This example will display the number 137 on the IC housing.<br>
 +
<code>s db Setting 137</code> # sets/writes the number 137 into the parameter '''Setting''' of the IC Housing('''db''')
 +
 
 +
Always use unique names for labels. When a label is named after a MIPS keyword like "Temperature:" or "Setting:" the original meaning of the keyword is overwritten, so when an instruction tries to use it an error will occur.
 +
 
 +
A [[Cartridge#Configuration|configuration cartridge]] installed in a [[Handheld_Tablet|tablet]]  can be used to see all available values and configuration parameter for all devices you focus on.
 +
 
 +
==Learning MIPS==
 +
MIPS can be difficult to get started with. So here is a list of instructions that are useful for beginners. These can be used to write many different scripts.
 +
 
 +
General:
 +
* <code>alias</code> make the script easier to read by assigning a name to a register or device, example: <code>alias rTemperature r15</code>
 +
* <code>label:</code> where "label" can be replaced with almost any word, jump and branch instructions can use these in place of line numbers, example: <code>start:</code>
 +
* <code>yield</code> pause for 1-tick and then resume, if not used the script will automatically pause for 1-tick after 128 lines
 +
 
 +
 
 +
<br>Jumps:
 +
*<code>j someLabelName</code> jump to line with '''someLabelName'''
 +
*<code>jal someLabelName</code> stores the next line number into the register ra (return address) and then jump to '''someLabelName'''
 +
*<code>j ra</code> jump to register ra (return address)
 +
 
 +
 
 +
<br>Branching (jump-if):<br>
 +
<code>beq a(r?|num) b(r?|num) c(r?|num)</code> if '''a''' is equal to '''b''' goto '''c'''  (label or linenumber) <br>
 +
<code>bne a(r?|num) b(r?|num) c(r?|num)</code> if  '''a''' not-equal '''b''' goto  '''c''' (label or linenumber) <br>
 +
<code>bgt a(r?|num) b(r?|num) c(r?|num)</code> if  '''a''' greater than '''b''' goto  '''c''' (label or linenumber) <br>
 +
<code>blt a(r?|num) b(r?|num) c(r?|num)</code> if  '''a''' less than '''b''' goto '''c''' (label or linenumber) <br>
 +
The suffix -al can be added to each of these (example: beqal) to save the '''next''' line number into the "return address" register. this is called using <code>j ra</code>
 +
 
 +
<br>Device interactions:
 
<pre>
 
<pre>
alias myDevice d0
+
l (load)
alias myImportantNumber r4
+
lb (load batch, requires one of the following: 0(Average) / 1(Sum) / 2(Minimum) / 3(Maximum))
 +
ls (load slot)
 +
s (store)
 +
sb (store batch)
 +
</pre>
  
main:
+
<br>Logic and Math:
yield
+
<pre>
#this is a comment, the program will ignore it, they are often used to explain something to a reader, or to turn off instructions without deleting them
+
seqz (common NOT-gate: turns 0 into 1, and all other values into 0)
...
+
move
beq myImportantNumber 42 myFunction
+
add (addition)
j main
+
sub (subtraction)
 +
mul (multiplication)
 +
div (division)
 +
</pre>
  
myFunction:
+
<br>Common device variables:
...
+
<pre>
j main
+
On (1 is on, 0 is off)
 +
Open (1 is open, 0 is closed)
 +
Setting (meaning varies between devices, example: a LED display(console) will show this value)
 +
Activate (1 usually means running, example: a Daylight sensor is 1 when the sun shines on it)
 +
Temperature (in Kelvin, Celsius - 273.15)
 +
Pressure (in kPa)
 
</pre>
 
</pre>
 +
 +
<br>Notes:
 +
<br>-All instructions and variables can be seen in-game in the MIPS editor window by clicking the "f", "x" and "s(x)" buttons on the top right.
 +
<br>-The stationpedia is the best source to see which variables are available to each device.
 +
<br>-Most scripts are loops, they end with a jump instruction that leads back up to the start. Otherwise they will just run once and then stop.
 +
 +
Two practice scripts:
 +
<br>Automatic Night Light: Load "Activate" from a Daylight sensor, flip the value with a NOT-gate, store the value to the "On" variable of one or more lights.
 +
<br>Automatic Wall Cooler: Read "Temperature" from a Gas Sensor. Branch if the value is greater than X, turn on the cooler. Branch if the value is less than Y, turn off the cooler. (Wall coolers need a minimum of 12.5 kPa pressure in the connected pipe)
  
  
 
----
 
----
 +
 
=Instructions=
 
=Instructions=
 
----
 
----
Line 254: Line 435:
 
<div id="lb"></div>
 
<div id="lb"></div>
 
;lb
 
;lb
:      r? typeHash var batchMode # Loads var from all output network devices with provided typeHash  using provided batchMode: Average(0), Sum (1), Minimum (2), Maximum (3). Can be used word or number. Result store into r?
+
:      r? deviceHash logicType batchMode # Loads LogicType from all output network devices with the provided type hash using the provided batch mode. Average (0), Sum (1), Minimum (2), Maximum (3). Can use either the word, or the number. The result is stored into r?.
  
 
<div id="sb"></div>
 
<div id="sb"></div>
 
;sb
 
;sb
:      typeHash var r? # Store register r? to var on all output network devices with provided typeHash
+
:      deviceHash logicType r? # Stores the register value to LogicType on all output network devices with the provided type hash.
 +
 
 +
<div id="lbn"></div>
 +
;lbn
 +
:      r? deviceHash nameHash logicType batchMode # Loads LogicType from all output network devices with the provided type and name hashes using provided batch mode. Average(0), Sum (1), Minimum (2), Maximum (3). Can use either the word, or the number. The result is stored into r?.
 +
 
 +
<div id="sbn"></div>
 +
;sbn
 +
:      deviceHash nameHash logicType r? # Stores the register value to LogicType on all output network devices with the provided type and name hashes.
  
 
<div id="#"></div>
 
<div id="#"></div>
Line 315: Line 504:
  
 
All approximate functions require additional argument denoting how close two numbers need to be considered equal. E.g.: <code>sap r0 100 101 0.01</code> will consider 100 and 101 almost equal (not more than 1%=0.01 different) and will set r0 to 1. The exact formula is <code>if abs(a - b) <= max(c * max(abs(a), abs(b)), float.epsilon * 8)</code> for <code>-ap</code> and is similar for other approximate functions.
 
All approximate functions require additional argument denoting how close two numbers need to be considered equal. E.g.: <code>sap r0 100 101 0.01</code> will consider 100 and 101 almost equal (not more than 1%=0.01 different) and will set r0 to 1. The exact formula is <code>if abs(a - b) <= max(c * max(abs(a), abs(b)), float.epsilon * 8)</code> for <code>-ap</code> and is similar for other approximate functions.
 +
 +
https://en.wikipedia.org/wiki/Machine_epsilon
 +
<br/>
 +
'''Example:'''
 +
  FLT_EPSILON = 2^(−23) ≈ 1.19e−07;        <span style="color:blue;">float (32 bit)</span>
 +
  DBL_EPSILON = 2^(−52) ≈ 2.20e−16;        <span style="color:#4c9700;">double (64 bit)</span>
 +
<br/>
 +
  <code>if abs(100 - 101) <= max(0.01 * max(abs(100), abs(101)), float.epsilon * 8)</code>
 +
  <code>if abs(-1) <= max(0.01 * 101), float.epsilon * 8)</code>
 +
  <code>if 1 <= max(0.01 * 101, float.epsilon * 8)</code>
 +
<br/>
 +
  if 1 <= max(1.01, FLT_EPSILON * 8)
 +
  if 1 <= max(1.01, DBL_EPSILON * 8)
 +
<br/>
 +
  <span style="color:blue;">if 1 <= max(1.01, 1.19e−07 * 8)</span>
 +
  <span style="color:#4c9700;">if 1 <= max(1.01, 2.20e−16 * 8)</span>
 +
<br/>
 +
  <span style="color:blue;">if 1 <= max(1.01, 0.000000952)</span>
 +
  <span style="color:#4c9700;">if 1 <= max(1.01, 0.00000000000000176)</span>
 +
<br/>
 +
  <span style="color:blue;">if 1 <= 1.01  TRUE  1</span>
 +
  <span style="color:#4c9700;">if 1 <= 1.01  TRUE  1</span>
  
 
==Device Variables==
 
==Device Variables==
Line 330: Line 541:
 
:    The current charge the device has.
 
:    The current charge the device has.
 
<div id="CLearMemory"></div>
 
<div id="CLearMemory"></div>
;CLearMemory
+
;ClearMemory
 
:    When set to 1, clears the counter memory (e.g. ExportCount).  Will set itself back to 0 when triggered.
 
:    When set to 1, clears the counter memory (e.g. ExportCount).  Will set itself back to 0 when triggered.
 
<div id="Color"></div>
 
<div id="Color"></div>
 
;Color
 
;Color
:    0 (or lower) = Blue
+
:    <span style="color:blue;">▇▇▇</span>&nbsp; 0 (or lower) = Blue
:    1 = Grey
+
:    <span style="color:grey;">▇▇▇</span>&nbsp;1 = Grey  
:    2 = Green
+
:    <span style="color:green;">▇▇▇</span>&nbsp;2 = Green  
:    3 = Orange
+
:    <span style="color:orange;">▇▇▇</span>&nbsp;3 = Orange  
:    4 = Red
+
:    <span style="color:red;">▇▇▇</span>&nbsp;4 = Red  
:    5 = Yellow
+
:    <span style="color:yellow;">▇▇▇</span>&nbsp;5 = Yellow  
:    6 = White
+
:    <span style="color:white;">▇▇▇</span>&nbsp;6 = White  
:    7 = Black
+
:    <span style="color:black;">▇▇▇</span>&nbsp;7 = Black  
:    8 = Brown
+
:    <span style="color:brown;">▇▇▇</span>&nbsp;8 = Brown  
:    9 = Khaki
+
:    <span style="color:khaki;">▇▇▇</span>&nbsp;9 = Khaki  
:    10 = Pink
+
:    <span style="color:pink;">▇▇▇</span>&nbsp;10 = Pink  
:    11 (or higher) = Purple
+
:    <span style="color:purple;">▇▇▇</span>&nbsp;11 (or higher) = Purple  
 
<div id="CompletionRatio"></div>
 
<div id="CompletionRatio"></div>
 
;CompletionRatio
 
;CompletionRatio
Line 439: Line 650:
 
;RecipeHash
 
;RecipeHash
 
<div id="RequestHash"></div>
 
<div id="RequestHash"></div>
 +
;ReferenceId
 +
:    Unique Identifier of a Device, this value is different for every device in a save.
 +
<div id="ReferenceId"></div>
 
;RequestHash
 
;RequestHash
 
<div id="RequiredPower"></div>
 
<div id="RequiredPower"></div>
Line 518: Line 732:
 
:<code>ls r0 d0 0 Mature # Store 1 in r0 if d0 has a mature crop</code>
 
:<code>ls r0 d0 0 Mature # Store 1 in r0 if d0 has a mature crop</code>
 
:<code>ls vMature dThisVictim 0 Mature # Store 1 in vMature if dThisVictim has a mature crop</code>
 
:<code>ls vMature dThisVictim 0 Mature # Store 1 in vMature if dThisVictim has a mature crop</code>
 +
;ReferenceId
 +
:    Unique Identifier of a Device, this value is different for every device in a save.
 +
<div id="ReferenceId"></div>
 +
----
  
----
 
 
=Examples=
 
=Examples=
 +
Previous examples were obsolete due to game changes, or confusing, they have been moved into the Discussions section
 
----
 
----
  
 
===Harvie automation===
 
===Harvie automation===
This script uses the batch instruction <code>sb ...</code> to control all Harvies on the network. But only one Harvie and one Tray will be the ''master'' and have their values read, the rest of the Harvies will just repeat whatever the ''master'' unit does. Some problems with this is that different types of crops mature at different speeds, and if manually planting and giving the ''master'' unit the first seed the harvesting action will be performed too early on the other plants.
+
This script uses the batch instruction <code>sb ...</code> to control all Harvie devices on the network. But only one Harvie and one Tray will be the ''master'' and have their values read, the rest of the Harvies will repeat exactly what this unit does. Some problems with this design is that different types of crops mature at different speeds, and if seeds were manually planted and the master unit recieved the first seed, the harvesting action will be performed too early on all the other plants since they are growing a few seconds slower.
  
 
<div class="mw-collapsible mw-collapsed" data-expandtext="{{int:Expand, Automated Harvie Script}}" data-collapsetext="{{int:Collapse, Automated Harvie Script}}">
 
<div class="mw-collapsible mw-collapsed" data-expandtext="{{int:Expand, Automated Harvie Script}}" data-collapsetext="{{int:Collapse, Automated Harvie Script}}">
Line 545: Line 763:
 
beq r0 1 harvestCrop
 
beq r0 1 harvestCrop
 
ls r0 dTray 0 Seeding
 
ls r0 dTray 0 Seeding
  #seeds on plant returns 1, all seeds picked returns 0
+
  #seeds available returns 1, all seeds picked returns 0
  #plants too young or old for seeds return -1
+
  #plants too young or old for seeds returns -1
 
beq r0 1 harvestCrop
 
beq r0 1 harvestCrop
 
j main
 
j main
Line 554: Line 772:
 
  #otherwise it will plant nothing repeatedly
 
  #otherwise it will plant nothing repeatedly
 
ls r0 dHarvie 0 Occupied
 
ls r0 dHarvie 0 Occupied
beq r0 0 ra
+
beq r0 0 main
 
sb rHarvieHash Plant 1
 
sb rHarvieHash Plant 1
 
j main
 
j main
Line 562: Line 780:
 
j main
 
j main
  
### End Script
+
### End Script ###
  
 
</pre>
 
</pre>
Line 569: Line 787:
 
-----
 
-----
  
 +
===Solar Panel 2-axis tracking===
 +
This script was copied from the [[Solar_Logic_Circuits_Guide]] (code provided by bti, comments and readability changes by Fudd79)
 +
<div class="mw-collapsible mw-collapsed" data-expandtext="{{int:Expand, Solar Panel 2-axis tracking}}" data-collapsetext="{{int:Collapse, Solar Panel 2-axis tracking}}">
 +
<pre>
 +
# This code assumes the following:
 +
# Daylight Sensor data-port points north
 +
# Solar Panel data-port points east
 +
 +
alias sensor d0
 +
alias v_angle r0
 +
alias h_angle r1
 +
alias sun_up r2
 +
 +
define solar_panel_hash -539224550
 +
define heavy_solar_panel_hash -1545574413
 +
 +
start:
 +
# Check to see if sun is up
 +
l sun_up sensor Activate
 +
# Go to reset if it's not
 +
beqz sun_up reset
 +
 +
# Calculate vertical angle
 +
l v_angle sensor Vertical
 +
div v_angle v_angle 1.5
 +
sub v_angle 50 v_angle
 +
 +
# Write vertical angle to all solar panels
 +
sb solar_panel_hash Vertical v_angle
 +
sb heavy_solar_panel_hash Vertical v_angle
 +
 +
# Obtain horizontal angle
 +
l h_angle sensor Horizontal
  
==Links==
+
# Write horizontal angle to all solar panels
 +
sb solar_panel_hash Horizontal h_angle
 +
sb heavy_solar_panel_hash Horizontal h_angle
 +
 
 +
# Go to start again
 +
yield
 +
j start
 +
 
 +
reset:
 +
# Park solar panels vertically facing sunrise
 +
sb solar_panel_hash Vertical 0
 +
sb heavy_solar_panel_hash Vertical 0
 +
# Park solar panels horizontally facing sunrise
 +
sb solar_panel_hash Horizontal -90
 +
sb heavy_solar_panel_hash Horizontal -90
 +
# Wait 10 seconds
 +
sleep 10
 +
# Go to start again
 +
j start
 +
 
 +
### End Script ###
 +
 
 +
</pre>
 +
</div>
 +
<br>
 
-----
 
-----
 +
 +
===Example experiment: how many lines of code are executed each tick?===
 +
To determine this, a script without <code>yield</code> will be used. It should have as few lines as possible (so no labels are used, but a reset value at the top will be needed) and count the number of lines, the IC Housing will be used to display the result.
 +
 +
<pre>
 +
move r0 1  #the first line has number 0
 +
add r0 r0 3
 +
s db Setting r0
 +
j 1
 +
</pre>
 +
 +
 +
Result (the numbers appears every 0.5 seconds):
 +
<br>127
 +
<br>256 (+129)
 +
<br>385 (+129)
 +
<br>511 (+126)
 +
<br>640 (+129)
 +
<br>769 (+129)
 +
<br>895 (+126)
 +
<br>1024 (+129)
 +
<br>1153 (+129)
 +
 +
There is a repeating +129, +129, +126 sequence, a hint that the real value is 128. Which also happens to be the number of lines in a script, which makes sense. A variation of this experiment will show that empty rows are also counted towards this number.
 +
 +
----
 +
=Links=
 +
----
 
* [https://stationeering.com/tools/ic] Stationeering.com offers a programmable circuits simulator so you can develop your code without repeatedly dying in game!
 
* [https://stationeering.com/tools/ic] Stationeering.com offers a programmable circuits simulator so you can develop your code without repeatedly dying in game!
* [https://hastebin.com/uwuhidozun.md]
+
* [http://www.easy68k.com/] EASy68K is a 68000 Structured Assembly Language IDE.
* [http://www.easy68k.com/]
+
* [https://marketplace.visualstudio.com/items?itemName=Traineratwot.stationeers-ic10] syntax highlighting for IC10 MIPS for Visual Studio Code (updated Feb 10th 2022)
 
* [https://pastebin.com/6Uw1KSRN] syntax highlighting for IC10 MIPS for KDE kwrite/kate text editor
 
* [https://pastebin.com/6Uw1KSRN] syntax highlighting for IC10 MIPS for KDE kwrite/kate text editor
 
* [https://drive.google.com/file/d/1yEsJ-u94OkuMQ8K6fY7Ja1HNpLcAdjo_/view] syntax highlighting for IC10 MIPS for Notepad++
 
* [https://drive.google.com/file/d/1yEsJ-u94OkuMQ8K6fY7Ja1HNpLcAdjo_/view] syntax highlighting for IC10 MIPS for Notepad++
 
* [https://pastebin.com/3kmGy0NN] syntax highlighting for IC10 MIPS for Notepad++ (updated: 05/05/2021)
 
* [https://pastebin.com/3kmGy0NN] syntax highlighting for IC10 MIPS for Notepad++ (updated: 05/05/2021)
 +
* [https://drive.google.com/file/d/1Xrv5U0ZI5jDcPv7yX7EAAxaGk5hKP0xO/view?usp=sharing] syntax highlighting for IC10 MIPS for Notepad++ (updated: 11/08/2022)
  
==Index==
+
----
-----
+
 
 +
=Index=
 +
----
  
 
{|
 
{|

Latest revision as of 17:49, 9 March 2024

MIPS scripting language for IC10 housings / chips[edit]

MIPS is Stationeers' in-game scripting language. It runs on IC10 chips crafted at the Electronics Printer.

Registers[edit]

Internal registers r?: The IC contains 16 CPU registers, numbered r0 to r15. From now on referred to as r?.

Device registers d? logicType: Device registers are written to and from the IC. A device register is numbered d0 to d5 (select via screw), or db (connected device). From now on referred to as d?.

Logic and algorithmic with Internal registers[edit]

All calculations are exclusively performed to and from r? registers, or generally more understood as variables in programming. You can use aliases to give convenient names with the alias string r?|d?command (see below).

Internal registers can be manipulated in various ways.

  • Write constant values move r? (r?|num): Example: move r0 2 sets r0 to the number 2.
  • Calculate: Calculations are done to- and from these registers, like add r? a(r?|num) b(r?|num). Example: add r1 r0 3 adds 3 to r0, and writes to r1.

Note, for any kind of if statements or loop behaviours, knowing about labels, branching, and jumps is essential knowledge. See below.

IO to Device registers[edit]

Acronym d? stands for device, where ? is a number corresponding to the screw device selector on the socket. You can also read/write to the device where the IC is planted in using device db.

Generally, there are up to 6 devices which can be set using the screwdriver d0 to d5. A special device register db is the device wherever the IC is mounted upon. Very convenient for atmospheric devices where no separate IC socket is required.

Note, the IC is completely unaware where d? is actually connected to. So if you get a logicType error, check d? number, or check if the screw has been set opn the socket. An alias is only convenient to convey what is expected to be set on the d? screw, it does not actually set or program the screq.

  • Read from device (load) l r? d? logicType: Reads logicType, like Pressure from a gas sensor, from device d? to register r?. Values can be read from connected devices and put into the register using the l (load) command. For example, if you want to load the state of a door.
    Example: l r0 Door Open reads the 'Open' field of an object named 'Door', that would be connected to the IC housing of the chip.
  • Write to a device (set) s d? logicType r?: Write a value from a register back to a device using the command s d? logicType r?. For example, if d0 is set to a door using the screwdriver, s d0 Open 0 sets the 'Open' status of the d0 (a door) to 0, effectively closing the door.

batch IO to - Device registers[edit]

Batch writing needs to be done to a specific deviceHash instead of d?. Is unique per device type, which you can find in the Stationpedia entries.

  • lb r? deviceHash logicType batchMode
  • sb deviceHash logicType r?

Additionally, using the following batch commands, a nameHash can be provided to only modify devices with a certain name.

  • lbn r? deviceHash nameHash logicType batchMode
  • sbn deviceHash nameHash logicType r?

batchMode is a parameter equal to 0, 1, 2, or 3. These are also defined as the constants Average, Sum, Minimum, and Maximum respectively. The word or number can be used.

Combining one of these functions with the HASH() function can be advantageous:

lbn r0 HASH("StructureGasSensor") HASH("Sensor 1") Temperature Average

This code will load the average temperature of all gas sensors on the network named "Sensor 1" onto register r0

If the batch read (lb/lbn) is done on a network without any matching devices the results will be as specified in the table:

Batch read with no devices
Batch Mode Result
Average (0) nan
Sum (1) 0
Minimum (2) 0
Maximum (3) ninf

Examples[edit]

Here are some examples demonstrating all three operations:

move r0 10
Sets register r0 to the value 10

move r0 r1
Copies the value of register r1 to register r0

l r0 d0 Temperature
Reads the Temperature parameter from device d0 and places the value in register r0. Note: not all devices have a Temperature parameter, check the in-game stationpedia.

To set a device specific value (like On), you can write into this value.

s d0 On r0
Writes the value from register r0 out to On parameter of device d0. In this example the device will be turned On, if valve of register r0 equals 1, otherwise (register r0 equals 0) it will turned off. See section Device Variables.

It's recommended to use labels (like: someVariable) instead of a direct reference to the register. See alias in section Instructions.

Special registers[edit]

There are two more registers. One called ra (return address) and one called sp (stack pointer). The ra is used by certain jump and branching instructions (those ending with -al) to remember which line in the script it should return to. The sp tracks the next index within the stack (a memory that can store up to 512 values) to be pushed (written) to or popped (read) from. Neither ra or sp is protected, their values can be changed by instructions like any other register.

Stack Memory[edit]

push r?
adds the value of register r? to the stack memory at index sp and increments the sp by 1.
pop r?
loads the value in the stack memory at index sp-1 into register r? and decrements the sp by 1.
peek r?
loads the value in the stack memory at index sp-1 into register r?.

As mentioned previously, sp can be both written to and read from any time. When reading (peek or pop), sp must be between 1 and 512, inclusive. While writing (push), sp must be between 0 and 511, inclusive.

Stack memory is persistent on logic chips. This means that if you have a logic chip and push values to the stack, the code that pushes those values can be removed and the stack will retain those values.

Note that this does not carry over to any other logic chips which receive the program of the original; They will need to have their stack memories programmed individually.

Stack Traversing

Traversing the stack can be done similarly to how an array would be traversed in some other languages:

#this will traverse indices {min value} through {max value} - 1

move sp {min value}


loop:

add sp sp 1

peek r0 #do something here with your stack values (loaded into r0)

blt sp {max value} loop


#continue on

Alternatively, you can use the pop function's decrementing to make a more efficient loop:

move sp {max value}

add sp sp 1


loop:

pop r0

#do something here with your stack values (loaded into r0)

bgt sp {min value} loop


#continue on

Device Ports[edit]

ICs can interact with up to 6 other devices via d0 - d5, as well as the device it's attached to via db. To change or set a device, use a screwdriver and adjust the device in the IC housing. You can read or set any of the device's properties, so it is possible to do things like read the pressure or oxygen content of a room on the same Device port.

Additionally, is possible to set other IC housings as devices, allowing you to create programs that run across multiple ICs together. For example, an Gas Mixing IC could check the Setting field of a Atmosphere Sensor IC and act based on the value of the sensor chip.

The l (load) or s (set) instructions you have to read or set these values to your device. Examples:

l r0 d0 Temperature #Reads the Temperature from an atmosphere sensor at device port d0 into register r0.

s d1 Setting r0 # Writes the value of the register r0 to the device on port d1 into the variable Setting.

Labels[edit]

Labels are used to make it easier to jump between lines in the script. The label will have a numerical value that is the same as its line number. Even though it's possible to use a labels value for calculations, doing so is a bad idea since any changes to the code can change the line numbers of the labels.


main: # define a jump mark with label main
j main # jumps back to main

Constants[edit]

Instead of using a register to store a fixed value, a constant can be made. Using this name will refer to the assigned value. With the help of Constants you can save register places.
define pi 3.14159 # defines a Constant with name pi and set it's value to 3.14159

You can use these constants like any other variables (see: alias in section Instructions). Example:
move r0 pi # set the value of register r0 to the value of constant named pi.

Indirect referencing[edit]

This is a way of accessing a register by using another register as a pointer. Adding an additional r in front of the register turns on this behaviour. The value stored in the register being used as the pointer must be between 0 to 15, this will then point to a register from r0 to r15, higher or lower values will cause an error.

move r0 5 stores the value 5 in r0
move rr0 10 is now the same as move r5 10 since r0 has the value 5, rr0 points at the register r5

Additional r's can be added to do indirect referencing multiple times in a row.
move r1 2
move r2 3
move rrr1 4 is now the same as move r3 4 since r1 points at r2 which points at r3

This also works with devices
move r0 2 stores the value 2 in r0
s dr0 On 1 is now the same as s d2 On 1, r0 has the value 2 so dr0 points at d2

Network Referencing / Channels[edit]

All cable networks have 8 Channels which can have data loaded from/stored to via a device and connection reference. Connections for each supported device are listed in the stationpedia. All 'connections' a device can make are a connection (pipe, chute, cable), but only cable networks have channels.

The 8 channels (Channel0 to Channel7) are however volatile, in that data is destroyed if any part of the cable network is changed, removed, or added to, and also whenever the world is exited. All these channels default to NaN. Strictly speaking, they default to what we would call "quiet NaN", in that its not an error it simply means its not a number yet. Recommend you use these channels for reading and writing between networks, rather than as a data store. This effectively means an IC can read all the networks for all devices to connected to it, so not just their own local network, but any networks any device they can reference is connected to.


l r0 d0:0 Channel0 d0 is device zero, and the :0 refers to that device's 0 connection

For example: on an IC Housing, the 0 connection is the data port and 1 is power, so you could write out r0 to Channel0 of the power network of the Housing using s db:1 Channel0 r0

Comments[edit]

Comments can be placed using a # symbol. All comments are ignored by the game when it reads commands. Below is an example of valid code with two comments.

alias MyAlias r0 # Text after the hash tag will be ignored to the end of the line.
# You can also write comments on their own lines, like this.

Debugging advices[edit]

The value stored in a register or variable can easily be displayed by writing it to the Setting parameter of the IC housing. This has no side effects. To see the value, just stand close to the IC housing and look directly at the housing.
s db Setting r0. # sets/writes the value of register r0 into the parameter Setting of the IC Housing(db)

To check if a certain block of code is executed, use the above trick but with a random number that you choose, like the line number.
This example will display the number 137 on the IC housing.
s db Setting 137 # sets/writes the number 137 into the parameter Setting of the IC Housing(db)

Always use unique names for labels. When a label is named after a MIPS keyword like "Temperature:" or "Setting:" the original meaning of the keyword is overwritten, so when an instruction tries to use it an error will occur.

A configuration cartridge installed in a tablet can be used to see all available values and configuration parameter for all devices you focus on.

Learning MIPS[edit]

MIPS can be difficult to get started with. So here is a list of instructions that are useful for beginners. These can be used to write many different scripts.

General:

  • alias make the script easier to read by assigning a name to a register or device, example: alias rTemperature r15
  • label: where "label" can be replaced with almost any word, jump and branch instructions can use these in place of line numbers, example: start:
  • yield pause for 1-tick and then resume, if not used the script will automatically pause for 1-tick after 128 lines



Jumps:

  • j someLabelName jump to line with someLabelName
  • jal someLabelName stores the next line number into the register ra (return address) and then jump to someLabelName
  • j ra jump to register ra (return address)



Branching (jump-if):
beq a(r?|num) b(r?|num) c(r?|num) if a is equal to b goto c (label or linenumber)
bne a(r?|num) b(r?|num) c(r?|num) if a not-equal b goto c (label or linenumber)
bgt a(r?|num) b(r?|num) c(r?|num) if a greater than b goto c (label or linenumber)
blt a(r?|num) b(r?|num) c(r?|num) if a less than b goto c (label or linenumber)
The suffix -al can be added to each of these (example: beqal) to save the next line number into the "return address" register. this is called using j ra


Device interactions:

l (load)
lb (load batch, requires one of the following: 0(Average) / 1(Sum) / 2(Minimum) / 3(Maximum))
ls (load slot)
s (store)
sb (store batch)


Logic and Math:

seqz (common NOT-gate: turns 0 into 1, and all other values into 0)
move
add (addition)
sub (subtraction)
mul (multiplication)
div (division)


Common device variables:

On (1 is on, 0 is off)
Open (1 is open, 0 is closed)
Setting (meaning varies between devices, example: a LED display(console) will show this value)
Activate (1 usually means running, example: a Daylight sensor is 1 when the sun shines on it)
Temperature (in Kelvin, Celsius - 273.15)
Pressure (in kPa)


Notes:
-All instructions and variables can be seen in-game in the MIPS editor window by clicking the "f", "x" and "s(x)" buttons on the top right.
-The stationpedia is the best source to see which variables are available to each device.
-Most scripts are loops, they end with a jump instruction that leads back up to the start. Otherwise they will just run once and then stop.

Two practice scripts:
Automatic Night Light: Load "Activate" from a Daylight sensor, flip the value with a NOT-gate, store the value to the "On" variable of one or more lights.
Automatic Wall Cooler: Read "Temperature" from a Gas Sensor. Branch if the value is greater than X, turn on the cooler. Branch if the value is less than Y, turn off the cooler. (Wall coolers need a minimum of 12.5 kPa pressure in the connected pipe)



Instructions[edit]


alias
alias str r? d? # labels register or device reference with name. When alias is applied to a device, it will affect what shows on the screws in the IC base. (housing)

alias vTemperature r0
alias dAutoHydro1 d0

move
d s # stores the value of s in d

move r0 42 # Store 42 in register 0

l (load)
l r# d# parameter

Reads from a device (d#) and stores the value in a register (r#)

l r0 d0 Setting
Read from the device on d0 into register 0

l r1 d5 Pressure
Read the pressure from a sensor

This also works with aliases. For example:
alias Sensor d0
l r0 Sensor Temperature

ls (load slot)
ls r# d# slotNum parameter

Reads from a slot (slotNum) of a device (d#) and stores the value in a register (r#)

ls r0 d0 2 Occupied
Read from the second slot of device on d0, stores 1 in r0 if it's occupied, 0 otherwise.

And here is the code to read the charge of an AIMeE:
alias robot d0
alias charge r0
ls charge robot 0 Charge


s (set)
s d# parameter r#

Writes a setting to a device.

s d0 Setting r0


add
d s t # calculates s + t and stores the result in d

add r0 r1 1 # add 1 to r1 and store the result as r0
add r0 r0 1 # increment r0 by one

sub
d s t # calculates s - t and stores the result in d
mul
d s t # calculates s * t and stores the result in d
div
d s t # calculates s / t and stores the result in d
mod
d s t
  1. calculates s mod t and stores the result in d. Note this
  2. doesn't behave like the % operator - the result will be
  3. positive even if the either of the operands are negative
slt
d s t # stores 1 in d if s < t, 0 otherwise
sqrt
d s # calculates sqrt(s) and stores the result in d
round
d s # finds the rounded value of s and stores the result in d
trunc
d s # finds the truncated value of s and stores the result in d
ceil
d s # calculates the ceiling of s and stores the result in d
floor
d s # calculates the floor of s and stores the result in d
max
d s t # calculates the maximum of s and t and stores the result in d
min
d s t # calculates the minimum of s and t and stores the result in d
abs
d s # calculates the absolute value of s and stores the result in d
log
d s # calculates the natural logarithm of s and stores the result
  1. in d
exp
d s # calculates the exponential of s and stores the result in d
rand
d # selects a random number uniformly at random between 0 and 1
  1. inclusive and stores the result in d
  1. boolean arithmetic uses the C convention that 0 is false and any non-zero
  2. value is true.
and
d s t # stores 1 in d if both s and t have non-zero values,
  1. 0 otherwise
or
d s t # stores 1 in d if either s or t have non-zero values,
  1. 0 otherwise
xor
d s t # stores 1 in d if exactly one of s and t are non-zero,
  1. 0 otherwise
nor
d s t # stores 1 in d if both s and t equal zero, 0 otherwise
  1. Lines are numbered starting at zero
j
a # jumps to line a.
bltz
s a # jumps to line a if s < 0
blez
s a # jumps to line a if s <= 0
bgez
s a # jumps to line a if s >= 0
bgtz
s a # jumps to line a if s > 0
beq
s t a # jumps to line a if s == t
bne
s t a # jumps to line a if s != t
bdseal
d? a(r?|num) # Jump execution to line a and store current line number if device d? is set.

bdseal d0 32 #Store line number and jump to line 32 if d0 is assigned.
bdseal dThisVictim HarvestCrop #Store line in ra and jump to sub HarvestCrop if device dThisVictim is assigned.

yield
# ceases code execution for this power tick
lb
r? deviceHash logicType batchMode # Loads LogicType from all output network devices with the provided type hash using the provided batch mode. Average (0), Sum (1), Minimum (2), Maximum (3). Can use either the word, or the number. The result is stored into r?.
sb
deviceHash logicType r? # Stores the register value to LogicType on all output network devices with the provided type hash.
lbn
r? deviceHash nameHash logicType batchMode # Loads LogicType from all output network devices with the provided type and name hashes using provided batch mode. Average(0), Sum (1), Minimum (2), Maximum (3). Can use either the word, or the number. The result is stored into r?.
sbn
deviceHash nameHash logicType r? # Stores the register value to LogicType on all output network devices with the provided type and name hashes.
#
# The following text will be ignored during compiling; use this to create comments.

Other examples

Conditional functions cheatsheet[edit]

suffix description branch to line branch and store return address relative jump to line set register
prefix: b- b-al br- s-
unconditional j jal jr
-eq if a == b beq beqal breq seq
-eqz if a == 0 beqz beqzal breqz seqz
-ge if a >= b bge bgeal brge sge
-gez if a >= 0 bgez bgezal brgez sgez
-gt if a > b bgt bgtal brgt sgt
-gtz if a > 0 bgtz bgtzal brgtz sgtz
-le if a <= b ble bleal brle sle
-lez if a <= 0 blez blezal brlez slez
-lt if a < b blt bltal brlt slt
-ltz if a < 0 bltz bltzal brltz sltz
-ne if a != b bne bneal brne sne
-nez if a != 0 bnez bnezal brnez snez
-dns if device d is not set bdns bdnsal brdns sdns
-dse if device d is set bdse bdseal brdse sdse
-ap if a approximately equals b bap bapal brap sap
-apz if a approximately equals 0 bapz bapzal brapz sapz
-na if a not approximately equals b bna bnaal brna sna
-naz if a not approximately equals 0 bnaz bnazal brnaz snaz

All b- commands require target line as last argument, all s- commands require register to store result as first argument. All br- commands require number to jump relatively as last argument. e.g. breq a b 3 means if a=b then jump to 3 lines after.

All approximate functions require additional argument denoting how close two numbers need to be considered equal. E.g.: sap r0 100 101 0.01 will consider 100 and 101 almost equal (not more than 1%=0.01 different) and will set r0 to 1. The exact formula is if abs(a - b) <= max(c * max(abs(a), abs(b)), float.epsilon * 8) for -ap and is similar for other approximate functions.

https://en.wikipedia.org/wiki/Machine_epsilon
Example:

 FLT_EPSILON = 2^(−23) ≈ 1.19e−07;        float (32 bit)
 DBL_EPSILON = 2^(−52) ≈ 2.20e−16;        double (64 bit)


 if abs(100 - 101) <= max(0.01 * max(abs(100), abs(101)), float.epsilon * 8)
 if abs(-1) <= max(0.01 * 101), float.epsilon * 8)
 if 1 <= max(0.01 * 101, float.epsilon * 8)


 if 1 <= max(1.01, FLT_EPSILON * 8)
 if 1 <= max(1.01, DBL_EPSILON * 8)


 if 1 <= max(1.01, 1.19e−07 * 8)
 if 1 <= max(1.01, 2.20e−16 * 8)


 if 1 <= max(1.01, 0.000000952)
 if 1 <= max(1.01, 0.00000000000000176)


 if 1 <= 1.01   TRUE   1
 if 1 <= 1.01   TRUE   1

Device Variables[edit]


Activate
1 if device is activated (usually means running), otherwise 0
l r0 d0 Activate # sets r0 to 1 if on or 0 if off
AirRelease
Charge
The current charge the device has.
ClearMemory
When set to 1, clears the counter memory (e.g. ExportCount). Will set itself back to 0 when triggered.
Color
▇▇▇  0 (or lower) = Blue
▇▇▇ 1 = Grey
▇▇▇ 2 = Green
▇▇▇ 3 = Orange
▇▇▇ 4 = Red
▇▇▇ 5 = Yellow
▇▇▇ 6 = White
▇▇▇ 7 = Black
▇▇▇ 8 = Brown
▇▇▇ 9 = Khaki
▇▇▇ 10 = Pink
▇▇▇ 11 (or higher) = Purple
CompletionRatio
ElevatorLevel
ElevatorSpeed
Error
1 if device is in error state, otherwise 0
ExportCount
How many items exporfted since last ClearMemory.
Filtration
The current state of the filtration system. For example filtration = 1 for a Hardsuit when filtration is On.
Harvest
Performs the harvesting action for any plant based machinery.
s d0 Harvest 1 # Performs 1 harvest action on device d0
Horizontal
HorizontalRatio
Idle
ImportCount
Lock
Maximum
Mode
On
Open
Output
Plant
Performs the planting operation for any plant based machinery.
s d0 Plant 1 # Plants one crop in device d0
PositionX
PositionY
PositionZ
Power
PowerActual
PowerPotential
PowerRequired
Pressure
PressureExternal
PressureInteral
PressureSetting
Quantity
Total quantity in the device.
Ratio
Context specific value depending on device, 0 to 1 based ratio.
RatioCarbonDioxide
RatioNitrogen
The ratio of nitrogen in device atmosphere.
RatioOxygen
The ratio of oxygen in device atmosphere.
RatioPollutant
The ratio of pollutant in device atmosphere.
RatioVolatiles
The ratio of volatiles in device atmosphere.
RatioWater
The ratio of water in device atmosphere.
Reagents
RecipeHash
ReferenceId
Unique Identifier of a Device, this value is different for every device in a save.
RequestHash
RequiredPower
Setting
SolarAngle
Solar angle of the device.
l r0 d0 SolarAngle # Sets r0 to the solar angle of d0.
Temperature
TemperatureSettings
TotalMoles
VelocityMagnitude
VelocityRelativeX
VelocityRelativeY
VelocityRelativeZ
Vertical
Vertical setting of the device.
VerticalRatio
Ratio of vertical setting for device.
Volume
Returns the device atmosphere volume

Slot Variables[edit]

In general (always?) slots are assigned as follows.

Slot 0: Import
Slot 1: Export
Slot 2: Inside Machine


Occupied
ls r0 d0 2 Occupied #Stores 1 in r0 if d0 has more seeds
ls vOccupied dThisVictim 2 Occupied #stores 1 in vOccupied if dThisVictim has more seeds
OccupantHash
Quantity
Damage
Efficiency
Health
Growth
ls r0 d0 0 Growth # Store the numerical growth stage of d0 in r0
Pressure
Temperature
Charge
ChargeRatio
Class
PressureWaste
PressureAir
MaxQuantity
Mature
ls r0 d0 0 Mature # Store 1 in r0 if d0 has a mature crop
ls vMature dThisVictim 0 Mature # Store 1 in vMature if dThisVictim has a mature crop
ReferenceId
Unique Identifier of a Device, this value is different for every device in a save.

Examples[edit]

Previous examples were obsolete due to game changes, or confusing, they have been moved into the Discussions section


Harvie automation[edit]

This script uses the batch instruction sb ... to control all Harvie devices on the network. But only one Harvie and one Tray will be the master and have their values read, the rest of the Harvies will repeat exactly what this unit does. Some problems with this design is that different types of crops mature at different speeds, and if seeds were manually planted and the master unit recieved the first seed, the harvesting action will be performed too early on all the other plants since they are growing a few seconds slower.

alias dHarvie d0
alias dTray d1

alias rHarvieHash r8
alias rTrayHash r9
l rHarvieHash dHarvie PrefabHash
l rTrayHash dTray PrefabHash

main:
yield
 #read plant data from the Tray
ls r0 dTray 0 Mature
 #harvestable plants return 1, young plants return 0
 #nothing planted returns -1
beq r0 -1 plantCrop
beq r0 1 harvestCrop
ls r0 dTray 0 Seeding
 #seeds available returns 1, all seeds picked returns 0
 #plants too young or old for seeds returns -1
beq r0 1 harvestCrop
j main

plantCrop:
 #stop the planting if no seeds available
 #otherwise it will plant nothing repeatedly
ls r0 dHarvie 0 Occupied
beq r0 0 main
sb rHarvieHash Plant 1
j main

harvestCrop:
sb rHarvieHash Harvest 1
j main

### End Script ###



Solar Panel 2-axis tracking[edit]

This script was copied from the Solar_Logic_Circuits_Guide (code provided by bti, comments and readability changes by Fudd79)

# This code assumes the following:
# Daylight Sensor data-port points north
# Solar Panel data-port points east

alias sensor d0
alias v_angle r0
alias h_angle r1
alias sun_up r2

define solar_panel_hash -539224550
define heavy_solar_panel_hash -1545574413

start:
# Check to see if sun is up
l sun_up sensor Activate
# Go to reset if it's not
beqz sun_up reset

# Calculate vertical angle
l v_angle sensor Vertical
div v_angle v_angle 1.5
sub v_angle 50 v_angle

# Write vertical angle to all solar panels
sb solar_panel_hash Vertical v_angle
sb heavy_solar_panel_hash Vertical v_angle

# Obtain horizontal angle
l h_angle sensor Horizontal

# Write horizontal angle to all solar panels
sb solar_panel_hash Horizontal h_angle
sb heavy_solar_panel_hash Horizontal h_angle

# Go to start again
yield
j start

reset:
# Park solar panels vertically facing sunrise
sb solar_panel_hash Vertical 0
sb heavy_solar_panel_hash Vertical 0
# Park solar panels horizontally facing sunrise
sb solar_panel_hash Horizontal -90
sb heavy_solar_panel_hash Horizontal -90
# Wait 10 seconds
sleep 10
# Go to start again
j start

### End Script ###



Example experiment: how many lines of code are executed each tick?[edit]

To determine this, a script without yield will be used. It should have as few lines as possible (so no labels are used, but a reset value at the top will be needed) and count the number of lines, the IC Housing will be used to display the result.

move r0 1   #the first line has number 0
add r0 r0 3
s db Setting r0
j 1


Result (the numbers appears every 0.5 seconds):
127
256 (+129)
385 (+129)
511 (+126)
640 (+129)
769 (+129)
895 (+126)
1024 (+129)
1153 (+129)

There is a repeating +129, +129, +126 sequence, a hint that the real value is 128. Which also happens to be the number of lines in a script, which makes sense. A variation of this experiment will show that empty rows are also counted towards this number.


Links[edit]


  • [1] Stationeering.com offers a programmable circuits simulator so you can develop your code without repeatedly dying in game!
  • [2] EASy68K is a 68000 Structured Assembly Language IDE.
  • [3] syntax highlighting for IC10 MIPS for Visual Studio Code (updated Feb 10th 2022)
  • [4] syntax highlighting for IC10 MIPS for KDE kwrite/kate text editor
  • [5] syntax highlighting for IC10 MIPS for Notepad++
  • [6] syntax highlighting for IC10 MIPS for Notepad++ (updated: 05/05/2021)
  • [7] syntax highlighting for IC10 MIPS for Notepad++ (updated: 11/08/2022)

Index[edit]


Functions


Device Variables

Slot Variables