The Speckle Sender is one of the two basic Speckle components. What it does is very simple: it sends data to other Speckle Receivers.
Once you create a Speckle Sender, a dialog box will ask you which Speckle Account to use. If you’ve followed the installation guide, you already should have an existing Speckle Account.
Double click on the one you want to use, and voila! you get a rather boring grasshopper component.
This component uses the Grasshopper ZUI. Zoom in and click on the plus button on the input parameter side. You can add as many input parameters as you like, and give them any name you want.
There are two main methods/events:
The payload size of any given event is limited to 3mb. If you exceed this much, simply create another Speckle Sender.
The Speckle Receiver listens for updates at a specific stream id. It dynamically recreates the structure of the sender.
Same initial instructions apply as for the Speckle Sender. Once on the canvas, set the
id input parameter to the one you want to listen to.
Please bear in mind one important aspect: stream ids are unique for each Speckle Server. As such, if you create sender with a specific account, a receiver can only listen to it if it is using the same account.
No problem. The receiver will pull the latest update from the Speckle Server.
Changing the Sender Component’s name will change the name of the stream. This can be rather informative for large projects.
We are treating input parameters as “layers”. Add, remove, change their names! All the Speckle Receivers will be updated with the new parameters, as outputs. Name them!
In Grasshopper, the Speckle Senders and Receivers maintain data structure:
This covers the main functionality of the speckle senders and receiver components for grasshopper. There’s a few more secrets in store (like history), but they’re yet to be properly implemented.