I haven't tried any i2c stuff yet, I should though. I'll get one of those grove sensors to try, and I'll see if I can put together an example project of two Arduinos talking with i2c.

I think it should be pretty easy. First, use the Include Files form to tell Embrio where the .h and .cpp files are that you want to use in the project and they will be copied to the compile directory. Get to that form from the view menu or by right clicking on a custom Arduino node. Then add the include lines in the Includes section of a node.

Also note that you'll want to leave out any code that has to do with timing when making a custom Arduino node (no delay() calls). When you add a new code block to an Arduino node it defaults to "every update". Then notice the refresh rate on the bottom right of the screen. The code in the Every Update code block will run that many times per second.

With the non-licensed version of Embrio you can only work in connected mode, where the Arduino is communicating with the computer via the serial cable. If the i2c library needs to use the serial port that will be a problem. I'll do some tests and update this thread, but if you manage to get something working (or have trouble) please update as well!

Lol Admin, you ARE on top of it. I'm glad I paid that $50. Hardly ever seen support that fast.

I tried your guideline on a TH02 temperature/humidity high accuracy sensor from Seeedstudio, using this code. The sketch runs in the Arduino IDE, and I tried to translate it into Embrio. It compiled (after a few tries, ;-) ) without errors, yet nothing appears on the outputs.

What am I doing wrong?

The generated node is below:

<Nodes>
<Node>
<UniqueID>7eecc49d-7ed1-4ae3-add0-f48df17957cd</UniqueID>
<AssemblyType>Embrio.NodeEngine.AgentController.Nodes.AgentControllerCustomArduinoNode</AssemblyType>
<NodeType>Custom Arduino Node</NodeType>
<UserDefinedName></UserDefinedName>
<Description>A node that lets you write any Arduino code to interact with the Arduino hardware. Can be both an input and output.</Description>
<NodeColor>201,204,227,255</NodeColor>
<X>0</X>
<Y>0</Y>
<Width>834</Width>
<IncludeCode>#include &lt;arduino.h&gt;
#include &lt;TH02.h&gt;
#include &lt;I2C.h&gt;</IncludeCode>
<DeclerationCode>// Instantiate TH02 sensor
TH02 sensor;
uint8_t devID;
int16_t temp, rh, rh_comp;</DeclerationCode>
<SetupCode>I2c.begin();
I2c.pullup(true); // Enable I2C Internal pullup
I2c.setSpeed(1); // Set I2C to 400Khz
// TH02 ID is 4 MSB
devID = sensor.getId() &gt;&gt; 4;</SetupCode>
<ImageName>arduino.png</ImageName>
<InfoURL></InfoURL>
<CodeDefinitions>
<CodeDefinition>
<UpdateCondition>EveryUpdate</UpdateCondition>
<Code>// Get temperature calculated
sensor.startTempConv();
sensor.waitEndConversion();
temp = sensor.getConversionValue();
Output_Temperature = sensor.getLastRawTemp()/100.0 ;

// Convert humidity
sensor.startRHConv();
sensor.waitEndConversion();
rh = sensor.getConversionValue();
Output_Raw_Humidity = sensor.getLastRawRH()/100.0 ;
Output_Compensated_Humidity = sensor.getConpensatedRH(0)/100.0 ;</Code>
<UniqueID>15dc4bee-78ba-47ce-9c50-6742589a1376</UniqueID>
</CodeDefinition>
</CodeDefinitions>
<Inputs></Inputs>
<Outputs>
<Output>
<UniqueID>47956206-4569-4151-bafe-eddbc6bc597d</UniqueID>
<DefinitionID>00000000-0000-0000-0000-000000000000</DefinitionID>
<DefaultName>Activation</DefaultName>
<CustomName>Temperature</CustomName>
<IsDisplayed>True</IsDisplayed>
<IsNative>False</IsNative>
<TypeName>Numeric</TypeName>
<IsOutsideConnection>False</IsOutsideConnection>
<IOType>Embrio.NodeEngine.NodeIO.NumericNodeOutput</IOType>
<ShowGraph>True</ShowGraph>
<LinkedIOID>00000000-0000-0000-0000-000000000000</LinkedIOID>
<IsUserAdded>True</IsUserAdded>
<MinValue>0</MinValue>
<MaxValue>1</MaxValue>
<UseNegativeRange>False</UseNegativeRange>
<CanUseNegativeRange>True</CanUseNegativeRange>
</Output>
<Output>
<UniqueID>01ffcd6a-2426-41eb-90fe-fee04e14a4ec</UniqueID>
<DefinitionID>00000000-0000-0000-0000-000000000000</DefinitionID>
<DefaultName>Activation 1</DefaultName>
<CustomName>Raw_Humidity</CustomName>
<IsDisplayed>True</IsDisplayed>
<IsNative>False</IsNative>
<TypeName>Numeric</TypeName>
<IsOutsideConnection>False</IsOutsideConnection>
<IOType>Embrio.NodeEngine.NodeIO.NumericNodeOutput</IOType>
<ShowGraph>True</ShowGraph>
<LinkedIOID>00000000-0000-0000-0000-000000000000</LinkedIOID>
<IsUserAdded>True</IsUserAdded>
<MinValue>0</MinValue>
<MaxValue>1</MaxValue>
<UseNegativeRange>False</UseNegativeRange>
<CanUseNegativeRange>True</CanUseNegativeRange>
</Output>
<Output>
<UniqueID>0904f836-7d7e-4ad8-945c-d561632be26c</UniqueID>
<DefinitionID>00000000-0000-0000-0000-000000000000</DefinitionID>
<DefaultName>Activation 2</DefaultName>
<CustomName>Compensated_Humidity</CustomName>
<IsDisplayed>True</IsDisplayed>
<IsNative>False</IsNative>
<TypeName>Numeric</TypeName>
<IsOutsideConnection>False</IsOutsideConnection>
<IOType>Embrio.NodeEngine.NodeIO.NumericNodeOutput</IOType>
<ShowGraph>True</ShowGraph>
<LinkedIOID>00000000-0000-0000-0000-000000000000</LinkedIOID>
<IsUserAdded>True</IsUserAdded>
<MinValue>0</MinValue>
<MaxValue>1</MaxValue>
<UseNegativeRange>False</UseNegativeRange>
<CanUseNegativeRange>True</CanUseNegativeRange>
</Output>
</Outputs>
</Node>
</Nodes>

No, the TH02 library needs a special I2C library, that's probably the error you got (it's in the descriptive text of the link).

Anyway, it have it almost working, but there either is something wrong with the transform function, or I am missing something. I added a few text debug fields and displayed the recorded values in there with the ToString function. However, the output fields do not display anything, despite the fact that the debug fields DO show the correct values.

Attached, you can find a screenshot, including the code. So what am I doing wrong here?

Worked perfectly (see below).
But what's the point of being able to specify a min-max endrange if you HAVE to use 0.0 to 1.0?
Or is that a bug?

Why don't you make the Transform function work as explained and have it transform values from one range into another? It's kind of illogical that it doesn't do that.

Anyway, now that I've got the hang of it, I can start playing. I really like this tool.

I noticed a spelling error: Compile and upload the controller to a coNnected arduino. There's another spelling error somewhere, but I can't find it anymore. I'll let you know when I come across it again.

A bug? New version available: doesn't show the changes (blank) and started the download, but never got to completion. Had to manually install version 1.1.6.

Tip: right clicking on the canvas displays the menu, clicking delete then deletes the selected node. It would however be wise to that the right click on a node also selects it first. I have often deleted the wrong node.

Question: how can I assign an icon to a node like the ones in the library have (distance and axis sensors).

Well, you said it yourself:

.

In my previous code, I wrote:



in which I wanted to transform a range of 0-1000 into a range from 0 to 100. That didn't show up in the output field. (It remained 0, no graph, no values, although the text output for debugging did show the correct value).

You then suggested to change it to:



so changing the last 100.0 value (max target range) into a 1.0 value (max 1.0 target range), and then the graph and values showed up.

So I guess the Transform function has a flaw in it, because any other value besides 1.0 as the max destination range, does not display the value, nor does it graph in the Node Output.

Edited by user Thursday, April 09, 2015 11:36:20 AM(UTC)  | Reason: added some text

The reason is the numeric values are "activations", from the "agent based" philosophy of the architecture. Its very loosely based on brains and neurons which are connected in ways where activating and suppressing other neurons is how they do their work. An activation of 0 leaves something off and an activation of 1 turns something on, and in that range the multiplying of values coming into the same input is very clean. Values in that range make sense, but values above it don't. An activation of 4 doesn't really mean anything, so activations are all clamped between 0 (or -1) and 1. I like the simplicity of the only data types being activations and triggers, but you're right some times it is strange when you have a value that you want to be a number but you have to transform it to an activation before using it, and then back to a number. I might end up adding another numeric input/output type if that ends up making things easier and more flexible, but I'm actually a little on the fence about it still. If anything I'll add one more numeric type which would be used similar to the text type, I really don't want to start adding a whole bunch of input/output types for each variant of a number people could want to use, that kind of goes against the idea of the software.

I'll add it to the long list. If you do find now that you understand the activation data type that you end up not wanting a number data type any more let me know, or also if you really find a numeric type will be useful.

Code in the deceleration block is scoped to just that node. This is done by finding all of the variables declared in the block, and giving them a unique name and replacing them for all code in that node. That's the reason for the "Variables" list under that block, it shows you what variable names it's picking up on. I left that in to make it easy to see if something you think is a variable isn't being picked up on, but I should probably hide that at some point.

If you define a function in the Declaration block, that's not given a unique name yet. I just noticed that when doing interrupt stuff and declaring interrupt function there. I'll fix that eventually.

The idea is that it's really easy to get simple programs working in Arduino, but then gets hard when you need to put a few examples together into one program. I think it's powerful to be able to put one example program into each node and keep them isolated in Embrio, and use the agent based architecture to build the program up around those example pieces.