NOTE: Requires a premium CloudRF account
Interface to the 3D simulation API at CloudRF.com. This powerful full 3D API supports configurable radios and antennas as well as the following features:
https://cloudrf.com/documentation/developer/#/3D
Access to the CloudRF account is available to Silver and Gold customers who have purchased a plan. Pay as you go and subscriptions available:
A command line API demo for this API is available on Github:
https://github.com/Cloud-RF/CloudRF-API-clients/tree/master/bash/3d
It POSTs a blender scene to the model upload API, then POSTs a JSON request containing radio settings to the 3D API.
Results are loaded upon the scene as a GLB file.
This works best with simple meshes but can work with complex meshes like Google photorealistic models sourced via the BLOSM plugin. The more complex the mesh, the longer it takes.
Extreme models eg. London at 10cm, are reduced automatically at the API to fit inside a Megavoxel limit linked to your plan. The silver plan is 10MP at the time of writing.
Add transmitters to your environment from the "Layout" display by clicking on "Add" at the top of the screen, then hover over "Transmitters" and choose a 2.2GHz template radio.
To move a transmitter, use Blender's Move tool from the top left toolbox. This will show colour coded X/Y/Z planes which you can drag to move the transmitter in three dimensions.
Transmitter Properties like power, antenna gain etc can be configured in the data tab in the properties area, located in the bottom right of the screen
NOTE: This is resource intensive so your account can only run one job at a time. You will need to wait if a job is still in process.
Plugin is open source on Github: https://github.com/Cloud-RF/CloudRF-API-clients/tree/master/integrations/blender
This extension requests the following permissions:
Needed to save and load a GLB model
Needed to communicate with the CloudRF API
Hey, unfortunately I haven't reviewed past first sentence of the description
NOTE: Requires a premium CloudRF account
This goes against the terms of service of extensions.blender.org. We usually do not accept extensions that require login and account in non-blender.org environments, but only make exceptions when service that requires login is aligned to Blenders mission, and premium subscription services obviously is not.
We might make it work if add-on worked with free plan, but I can't give any guarantees at this point.
Checking the code (not testing).
Unused imports:
from multiprocessing import Pool
from bpy_extras.io_utils import ImportHelper
Online access (in this case access to https://api.cloudrf.com
) must only run when bpy.app.online_access
is True, otherwise this may report or display a message in the UI.
Hey everyone,
Just a heads-up about a recent change regarding the licensing of add-ons on the Blender extension platform. Moving forward, all add-ons will need to be released under the GNU/GPL 3.0 license (SPDX:GPL-3.0-or-later). This is mainly to keep things simple and consistent across the board.
Previously, we accepted various licenses as long as they were compatible with Blender’s distribution. However, to avoid any confusion and streamline the process, all add-ons using the bpy API should now be presented as GPL 3 (the same license the Blender bundle is distributed). Regardless of whether the original code was under GPL 2, or something else like MIT or ZLIB.
Existing add-ons versions won't be affected. However, new updates will need to comply to the revised requirements.
Thanks for understanding, and feel free to reach out if you have any questions.
Sign in to comment.
Ready for review