# Quickstart

Stream three signals from a new Simulink model into a Nominal dataset.

## 1. Install

Install the Nominal blockset as described in [Install](https://dev.nominal.io/simulink/install.md). The **Nominal Stream Sink**
block then appears in the Simulink Library Browser under **Nominal**.

## 2. Set up a profile

The block reads your API key and your instance’s URL from a profile in Nominal’s config file,
the file Nominal’s other clients read too, so the key is never saved into the model file. It
uses the profile named `default`. A computer already set up for another Nominal client, such as
the Python client, has one. Otherwise
[API keys setup](https://dev.nominal.io/quickstart/quickstart/api-keys-setup/) shows how to create a key and save
it in the file.

## 3. Create a dataset

The block writes to a dataset that already exists. In the Nominal app, open the **Data sources**
page (in the sidebar, click **Data**, then **Data sources**), click **NEW DATASET**, enter a name,
and click **CREATE DATASET**. On the new dataset’s page, hover over **RID** in the **Details**
section and click the copy icon.
[Finding a dataset’s RID](https://dev.nominal.io/quickstart/quickstart/quick/quick-dataset-rid/) has other ways
to get the RID.

## 4. Build the model

Open a new model and drag **Nominal Stream Sink** into it from the Library Browser, or type
`Nominal` on the canvas and pick it from Quick Insert. For a first
run, three source blocks are enough: **Band-Limited White Noise**, **Chirp Signal** and
**Sine Wave**. Wire them into a **Mux** with three inputs, and wire the Mux into the block. Name
the three lines going into the Mux `noise`, `chirp` and `sine`, since the line names become the
channel names in Nominal.

## 5. Configure the block

Double-click the block, then:

1. Click **Detect from connected signal**. **Channel names (comma-separated)** fills in with
   `'noise, chirp, sine'`.
2. Paste the dataset’s RID into **Dataset RID**, inside single quotes: `'<dataset RID>'`. Every
   text field in this dialog takes a MATLAB expression, so text needs the quotes.
3. Set **Sample time (s) — how often to write, not the solver step** to `0.01`. The run then
   makes 1001 rows, which fit in the block’s buffer however fast the simulation runs.
4. Click **OK**.

Leave **Mode** at **Direct to Nominal** and the other fields at their defaults.

## 6. Run the model

Click **Run**. The points cover the run’s 10 simulated seconds, starting from the moment the run
started.

Open the dataset in Nominal. The dataset now has the channels `noise`, `chirp` and `sine`.

## If nothing arrives

When the run stops with a message about the Nominal config file or a profile, the message names
the file and what it is missing. [API keys setup](https://dev.nominal.io/quickstart/quickstart/api-keys-setup/)
shows what the file holds.

When Simulink reports that it can’t evaluate **Dataset RID**, the value is missing its quotes.

A warning when the run ends,
`Nominal Stream Sink: execution <ID>: <dropped> of <total> rows did not reach Nominal`, means
some rows didn’t arrive. When requests failed, the `Last error` at the end of the warning gives
the reason. Check that the profile’s URL is that of the instance the dataset belongs to, and
that **Dataset RID** is that dataset’s RID.

[Errors and warnings](https://dev.nominal.io/simulink/ref/messages.md) lists every message the block shows.

## Next

- [Choose and name channels](https://dev.nominal.io/simulink/guides/channels.md): how the block maps signals to channels.
- [Timing and dropped rows](https://dev.nominal.io/simulink/guides/timing.md): sample time, timestamps and the buffer.
- [Stream through a proxy](https://dev.nominal.io/simulink/guides/proxy.md): keep the API key off the computer running the model.