Answers.Body: <p>The LEGO <em>EV3 Block Developer Kit</em> documentation refers to these as &quot;gray blobs&quot;. These are compiler intrinsics and don't have a .vix implementation. They generally correspond directly to the bytecodes from the <em>EV3 Firmware Developer Kit</em>.</p>
  <hr />
  <p>Note: Developer kits are available on the official LEGO MINDSTORMS <a href="https://www.lego.com/en-us/themes/mindstorms/downloads" rel="nofollow noreferrer">download page</a>.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-31T14:26:17.177Z
Answers.Text: Thank you so much! This is exactly what i was looking for!
  I didn't except to get an answer so quickly, since most of the questions here are about Lego minifigures, but it's nice to know there are also people like you, that know a lot about the EV3 brick
Answers.UserDisplayName: MoCsabi
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-31T14:27:39.793Z
Answers.Text: The main reason I asked this question, is because the Start block seemingly has a "result" output. Do you have any idea what thats for?
Answers.UserDisplayName: MoCsabi
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-31T19:12:11.690Z
Answers.Text: I think the start block is a little different that other blocks since it starts a VM thread instead of calling a specific bytecode command. The output is probably just the program flow wire that connects to the next block to run.
Answers.UserDisplayName: David Lechner
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-31T14:10:29.250Z
Answers.LastActivityDate: 2021-08-31T14:10:29.250Z
Answers.UserDisplayName: David Lechner
Body: <p>They look like this:</p>
  <p><a href="https://i.sstatic.net/JLVBH.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/JLVBH.png" alt="Image of low-level functions" /></a></p>
  <p>By default, when you refer to a vix file, it looks like this:</p>
  <p><code>&lt;Reference Type=&quot;VILib&quot; Name=&quot;TerminalTerminal.vix&quot; /&gt; </code></p>
  <p>But, to refer to these low-level functions, you need to write:</p>
  <p><code>&lt;Reference Name=&quot;X3.Lib:StartBlockTest&quot; Type=&quot;VILib&quot; SubType=&quot;StartBlock&quot;/&gt;</code></p>
  <p>Where can I find this &quot;X3.Lib&quot;?</p>
  <p>Thanks in advance,
  Csabi</p>
  
Tags: <programming><software><ev3-g>
Title: EV3G Where can I find the .vix file for the low-level functions? (Set integer, IO operations, start block)
UserDisplayName: MoCsabi
ThreadText: # EV3G Where can I find the .vix file for the low-level functions? (Set integer, IO operations, start block)
  
  (Asked by: username_0 on 2021-08-31)
  
  They look like this:
  
  [![Image of low-level functions](https://i.sstatic.net/JLVBH.png)](https://i.sstatic.net/JLVBH.png)
  
  By default, when you refer to a vix file, it looks like this:
  
  But, to refer to these low-level functions, you need to write:
  
  Where can I find this "X3.Lib"?
  
  Thanks in advance,
  Csabi
  
  **Tags:** programming, software, ev3-g
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-08-31. Score: 3 | Accepted answer
  
  The LEGO *EV3 Block Developer Kit* documentation refers to these as "gray blobs". These are compiler intrinsics and don't have a .vix implementation. They generally correspond directly to the bytecodes from the *EV3 Firmware Developer Kit*.
  
  ---
  
  Note: Developer kits are available on the official LEGO MINDSTORMS [download page](https://www.lego.com/en-us/themes/mindstorms/downloads).
  
  > **Comments:**
  > **username_0**: Thank you so much! This is exactly what i was looking for! I didn't except to get an answer so quickly, since most of the questions here are about Lego minifigures, but it's nice to know there are also people like you, that know a lot about the EV3 brick  
  > **username_0**: The main reason I asked this question, is because the Start block seemingly has a "result" output. Do you have any idea what thats for?  
  > **username_1**: I think the start block is a little different that other blocks since it starts a VM thread instead of calling a specific bytecode command. The output is probably just the program flow wire that connects to the next block to run.  
  
  ---
  
  