Image representative of product style, product supplied may vary. We have created a series of short CPR videos to break down all the significant areas and have updated our 'CPR for Cables' guide, available for you to download. For the latest information on CPR for Cables, you can visit our dedicated CPR Explained web page. This product is an excellent alternative to Times Microwave LMR® cables or Commscope®, Andrew®, CNT®.ĬPR-Compliant options are available for this cable and are indicated in the product table. If you are looking for a DNV-GL offshore approved product try RF 400, exclusively available from FSC. The RF400 comes with an SHF1 LSZH (Low Smoke Zero Halogen) sheath tested to IEC 6 Cat.A and is UV resistant to ASTM G 154. Typical applications for RF400 cables include LMR, mobile phone transmitters, broadband services, satellite antennas, marine satellite systems, Wi-Fi, military and environments where a durable SHF1 jacket is required. Specially designed to offer high performance across the bandwidth spectrum these products provide a real advantage over traditional corrugated cables. Both types are Low Smoke Halogen Free and flame retardant to IEC60332-3. Heavy duty SHF2 sheathed versions are available for installations where the risk of oil and chemical exposure is high. Often, the response body will contain more information about the failure.Īuthentication through the API is done using authentication tokens which can be retrieved from the Authentication endpoints.The RF400 is an ideal choice for LMR (Land Mobile Radio) communications, the interconnection of transceivers and satellite systems in a marine or offshore environment. Requirements for specific fields are specified for each endpoint. This is typically caused by missing fields or fields that contain invalid data. Unable to satisfy request due to semantic errors. The response body is the current version of the resource. This is caused by the provided revisionid being different than the current version. Unsupported HTTP request method for endpoint.Ĭonflict during save of resource. User has insufficient privileges to perform request on specified resource. If the request failed, you'll receive one of seven responses: Each response includes a status code which will tell you if the request succeeded or failed and why. We use HTTP Status Codes to notify the client of any problems that occurred during the request. This is also used in actions such as un-favoriting and un-completing a guide. If the resource doesn't exist, it is created. PATCH Update to a resource, only changing the provided attributes. For a more detailed explanation, check out the full list of HTTP Request Methods. Where possible, we use appropriate HTTP verbs for each action. Pretty simple! If you want to build an offline tool, an archived collection of oManual files is also available. The best way to get started is to just dive right in! You don't need an app id for most requests, so you can start writing your app right now. When we introduce changes that may break existing apps, we will increment the version number. The MOUNT 400, with its ball joint, helps you achieve an aesthetic and functionally perfect installation. Make sure to version your API calls with 2.0. If you build on our API, we will support you by maintaining future compatibility. For human-palatable formatted json, append ?pretty to the end of any request. The API responds with JSON by default, but you can also request XML (on some endpoints). The API provides access to our guides (step-by-step guides and namespace pages), categories, users, teams, and our reputation badges. We can't wait to see what you come up with! What can I do with the API?Īnything you want! The sky is the limit for awesome applications built using our database of guides. Our API provides programmatic access to loxone, enabling anyone to write innovative applications and utilities on top of our rich database.
0 Comments
Leave a Reply. |