Using the SLSC Web API

You can configure the SLSC chassis by using the web API to create web clients that send HTTP POST requests to the URL of the web server on the SLSC chassis. The web server returns HTTP responses. The body of the HTTP request and response follows the JSON-RPC 2.0 Specification. 

The format of the URL of the web server is http://<IP address or hostname of the web server>/nislsc/call. For example, a URL can be http://10.144.160.151/nislsc/call, where 10.144.160.151 is the IP address of the web server. A URL can also be http://SLSC-12001-030FD4DE/nislsc/call, where SLSC-12001-030FD4DE is the hostname of the web server.

The following example shows the body of a request:

{
   "id": "1",
   "jsonrpc": "2.0",
   "method": "initializeSession",
   "params":
   {
       "devices": "SLSC-12001-030898C6-Mod2"
   }
}

The following table lists the members in the request. These members follow the JSON-RPC 2.0 specification.

Table 1. Members in a request of the SLSC web API

 

The following example shows the body of the response without errors:

{
   "id": "1",
   "jsonrpc": "2.0",
   "result":
   {
       "session_id": "_session99"
   }
}

The following examples show the body of the response with errors:

{
   "jsonrpc": "2.0",
   "id": null,
   "error": {
       "code": -32700,
       "message": "Invalid JSON was received by the server. An error occurred on the server while parsing the JSON text.  Details: Invalid value. Offset: 148"
   }
}

 

{
   "jsonrpc": "2.0",
   "id": "1",
   "error": {
       "code": -32000,
       "message": "SLSC error.",
       "data": {
           "nislsc_code": -250806,
           "nislsc_message": "The specified device was not found.  Device: SLSC-12001-030898C6-Mod2"
       }
   }
}

 

The following tables explain the members in the response. These members follow the JSON-RPC 2.0 specification.

Table 2. Members in a response of the SLSC web API without errors

 

Table 3. Members in a response of the SLSC web API with errors

 

The error member includes the following objects:

Table 4. Objects in the error member

 

Batch Request and Response

Following the JSON-RPC 2.0 specification, a batch request can send several methods in one request. However, the web server handles batch requests differently from the JSON-RPC 2.0 specification in the following ways:

• The web server handles the methods in a batch request in sequence.
• The web server can handle only one batch request at a time. When the web server is handling a batch request, any other single or batch request is blocked until the current batch request is complete. However, the web server can handle multiple single requests at a time.
• If a method in the batch request returns an error, the web server returns errors for all methods that follow.

The following example shows a batch request:

[
   { "id": "2", "jsonrpc": "2.0", "method": "readRegister", "params": { "session_id": "_session0", "register_address": 256 } },
   { "id": "3", "jsonrpc": "2.0", "method": "getProperty:", "params": { "session_id": "_session0", "property": "NI.Debug.Led0Bool" } },
   { "id": "4", "jsonrpc": "2.0", "method": "executeCommand", "params": { "session_id": "_session0", "command": "NI.Debug.EnableLED0Immediate"} }
]

The following example shows the batch response without errors:

[
   { "id": "2", "jsonrpc": "2.0", "result": { "data": 128 } },
   { "id": "3", "jsonrpc": "2.0", "result": { "value": false } },
   { "id": "4", "jsonrpc": "2.0", "result": {} }
]

The following example shows the batch response with errors:

[
   { "id": "2", "jsonrpc": "2.0", "result": { "data": 128 } },
   { "id": "3", "jsonrpc": "2.0", "error": { "code": -32000, "message": "SLSC error", "data": { "nislsc_code": -250893, "nislsc_message": "Chassis power-on hours property write failed." } } },
   { "id": "4", "jsonrpc": "2.0", "error": { "code": -32001, "message": "Error occurred in previous request."} }
]

 

SLSC Web API Error Codes

The following table lists SLSC web API error codes. The JSON-RPC 2.0 specification defines all SLSC web API error codes except -32000 and -32001.

Table 5. SLSC web API error codes

 

Enum Values

If the data type of a parameter in an HTTP request is enum, you can specify the parameter with a key or value. The key must be a String and the value must be a Number.

 

Static and Dynamic Properties

There are two categories of properties in the web API: static properties and dynamic properties. Static properties are defined by the SLSC driver, whereas dynamic properties are defined by the user of the SLSC device. You can find dynamic properties in the SLSC module capabilities. You can use the getDevicePropertyList method to get both static and dynamic properties.

 

Using the Default Value of a Parameter

To use the default value of a parameter, you can specify an alias for the parameter, remove the parameter, or specify an empty string for the parameter.

 

Specifying an Alias for a Parameter

You can specify an alias for the parameter to explicitly use the default value of a member. Aliases are special names that start with a $ sign:

• $DefaultDevices–Default devices of the session.
• $DefaultNVMEMAreas–Default NVMEM areas of the session.
• $DefaultPhysChans–Default physical channels of the session.

The following example uses an alias to specify the default devices of the session:

{
   "id": "4",
   "jsonrpc": "2.0",
   "method": "connectToDevices",
   "params":
   {
       "session_id": "_session0",
       "devices": "$DefaultDevices"
   }
}

 

Removing a Parameter from a Request

The following example removes the devices parameter from the request to use the default devices of the session:

{
   "id": "4",
   "jsonrpc": "2.0",
   "method": "connectToDevices",
   "params":
   {

       "session_id": "_session0"
   }
}

 

Specifying an Empty String for a Parameter

The following example specifies an empty string for the parameter to use the default devices of the session:

{
   "id": "4",
   "jsonrpc": "2.0",
   "method": "connectToDevices",
   "params":
   {
       "session_id": "_session0",
       "devices": ""
   }
}

 

 

You can use the following methods to manipulate the SLSC chassis and modules:

• General Methods
  • abortSession
  • closeSession
  • connectToDevices
  • disconnectFromDevices
  • initializeSession
  • renameDevice
  • reserveDevices
  • resetDevices
  • unreserveDevices
• Property Methods
  • commitProperties
  • getDevicePropertyList
  • getSessionPropertyList
  • getProperty
  • getPropertyInformation
  • setProperty
• Command Methods
  • executeCommand
  • getCommandList
  • getCommandInformation
• NVMEM Methods
  • commitNvmemAreas
  • getNvmemBytes
  • setNvmemBytes
• Register Methods
  • readRegister
  • writeRegister

You can also refer to the attachment for examples of requests and responses, schema files, and default values.

 

abortSession

Cancels a method that blocks network communications. 

 

Parameters

 

After aborting the session, the session handle remains valid, but methods that access network connections return errors. To recover from an aborted session, close the session and initialize a new one.

 

Example

The following example shows a request:

{
   "id": "3",
   "jsonrpc": "2.0",
   "method": "abortSession",
   "params":
   {
       "session_id": "_session0"
   }
}

The following example shows the response:

{
   "id": "3",
   "jsonrpc": "2.0",
   "result": {}
}

Back to Web API Method Reference 

closeSession

Closes an SLSC session.

 

Parameters

 

Example

The following example shows a request:

{
   "id": "2",
   "jsonrpc": "2.0",
   "method": "closeSession",
   "params":
   {
       "session_id": "_session0"
   }
}

The following example shows the response:

{
   "id": "2",
   "jsonrpc": "2.0",
   "result": {}
}

Back to Web API Method Reference 

connectToDevices

Connects to an SLSC device.

 

Parameters

 

 

Example

The following example shows a request:

{
   "id": "4",
   "jsonrpc": "2.0",
   "method": "connectToDevices",
   "params":
   {
       "session_id": "_session0",
       "devices":
       [
           "SLSC-12001-030898C6-Mod1",
           "SLSC-12001-030898C6-Mod2"
       ]
   }
}

The following example shows the response:

{
   "id": "4",
   "jsonrpc": "2.0",
   "result": {}
}

Back to Web API Method Reference 

disconnectFromDevices

Closes network connections for one or multiple devices.

 

Parameters

 

If multiple devices share a network connection because they are in the same SLSC chassis, the network connection remains open until the last device is disconnected.

 

Example

The following example shows a request:

{
   "id": "5",
   "jsonrpc": "2.0",
   "method": "disconnectFromDevices",
   "params":
   {
       "session_id": "_session0",
       "devices":
       [
           "SLSC-12001-030898C6-Mod1",
           "SLSC-12001-030898C6-Mod2"
       ]
   }
}

The following example shows the response:

{
   "id": "5",
   "jsonrpc": "2.0",
   "result": {}
}

Back to Web API Method Reference

initializeSession

Initializes an SLSC session.

 

Parameters

 

If reservation_timeout is greater than 0 and access is ReadWrite, a circular waiting may occur when multiple sessions try to reserve multiple devices. The following table shows a circular waiting that occurs when two sessions try to reserve two modules.

 

 

Both session 1 and session 2 return errors when timeout expires. To avoid the circular waiting, ensure that session 1 and session 2 reserve modules in the same order. If session 1 reserves module 1 first and then reserves module 2, ensure that session 2 also reserves module 1 first and then reserves module 2.

The following table shows the keys and values of the access parameter.

 

 

You can specify only one of the following three parameters in one request: devices, physical_channels, and nvmem_areas. If you do not specify any of the three parameters, this method initializes the session with no resources.

The following table lists the return values.

 

 

Example

The following example shows a request without resources. You can also omit the params member.

{
   "id": "1",
   "jsonrpc": "2.0",
   "method": "initializeSession",
   "params": {}
}

The following example shows a request with resources:

{
   "id": "1",
   "jsonrpc": "2.0",
   "method": "initializeSession",
   "params":
   {
       "devices":
       [
           "SLSC-12001-030898C6-Mod2",
           "SLSC-12001-030898C6-Mod3"
       ],
       "access": "ReadWrite",
       "reservation_group": "nitest"
   }
}

The following example shows the response:

{
   "id": "1",
   "jsonrpc": "2.0",
   "result":
   {
       "session_id": "_session0"
   }
}

Back to Web API Method Reference 

renameDevice

Renames a device.

 

Parameters

 

Example

The following example shows a request:

{
   "id": "9",
   "jsonrpc": "2.0",
   "method": "renameDevice",
   "params":
   {
       "session_id": "_session0",
       "device": "SLSC-12001-030898C6",
       "new_device_name": "SLSC-12001-TEST"
   }
}

The following example shows the response:

{
   "id": "9",
   "jsonrpc": "2.0",
   "result": {}
}

Back to Web API Method Reference

reserveDevices

Reserves one or multiple devices to prevent other sessions from accessing the devices. You must reserve a device before using it. To reserve a device that has been reserved by another session with ReadWrite access, you can close the session, unreserve the device, or use the same reservation group name as that of the device. You can directly reserve a device that has been reserved by another session with ReadOnly access.

 

Parameters

 

The following table shows the keys and values of the access parameter.

 

 

If reservation_timeout is greater than 0 and access is ReadWrite, a circular waiting may occur when multiple sessions try to reserve multiple devices. The following table shows a circular waiting that occurs when two sessions try to reserve two modules.

 

 

Both session 1 and session 2 return errors when timeout expires. To avoid the circular waiting, ensure that session 1 and session 2 reserve modules in the same order. If session 1 reserves module 1 first and then reserves module 2, ensure that session 2 also reserves module 1 first and then reserves module 2.

 

Example

The following example shows a request:

{
   "id": "6",
   "jsonrpc": "2.0",
   "method": "reserveDevices",
   "params":
   {
       "session_id": "_session0",
       "devices":
       [
           "SLSC-12001-030898C6-Mod1",
           "SLSC-12001-030898C6-Mod2"
       ],
       "access": "ReadWrite",
       "reservation_group": "nitest"
   }
}

The following example shows the response:

{
   "id": "6",
   "jsonrpc": "2.0",
   "result": {}
}

Back to Web API Method Reference

resetDevices

Resets devices to default state. This method sends the specified modules a software reset signal, reinitializes module registers to their initial value, and rereads the module's non-volatile memory. If you specify a chassis, this method resets all modules in the chassis.

 

Parameters

 

Example

The following example shows a request:

{
   "id": "8",
   "jsonrpc": "2.0",
   "method": "resetDevices",
   "params":
   {
       "session_id": "_session0",
       "devices":
       [
           "SLSC-12001-030898C6-Mod1",
           "SLSC-12001-030898C6-Mod2"
       ]
   }
}

The following example shows the response:

{
   "id": "8",
   "jsonrpc": "2.0",
   "result": {}
}

Back to Web API Method Reference

unreserveDevices

Unreserves one or multiple devices so that other sessions can reserve them.

 

Parameters

 

Example

The following example shows a request:

{
   "id": "7",
   "jsonrpc": "2.0",
   "method": "unreserveDevices",
   "params":
   {
       "session_id": "_session0",
       "devices":
       [
           "SLSC-12001-030898C6-Mod1",
           "SLSC-12001-030898C6-Mod2"
       ]
   }
}

The following example shows the response:

{
   "id": "7",
   "jsonrpc": "2.0",
   "result": {}
}

Back to Web API Method Reference

commitProperties

Commits properties with pending changes to SLSC hardware. You must commit dynamic properties for the changes to take effect. You do not have to commit static properties because changes take effect immediately after you set static properties. If you set a property multiple times before you commit the property, this method commits only the last value. 

 

Parameters

 

You can specify only one of the following two parameters in one request: devices and physical_channels. If you do not specify any of the two parameters, the method performs the following operation:

• If the session is initialized with devices or physical channels, use default devices or physical channels of the session.

 

Example

The following example shows a request:

{
   "id": "14",
   "jsonrpc": "2.0",
   "method": "commitProperties",
   "params":
   {
       "session_id": "_session0",
       "devices":
       [
           "SLSC-12001-030898C6-Mod1",
           "SLSC-12001-030898C6-Mod2"
       ]
   }
}

The following example shows the response:

{
   "id": "14",
   "jsonrpc": "2.0",
   "result": {}
}

Back to Web API Method Reference

 

getDevicePropertyList

Lists all device properties. The following table lists the parameters of this method.

 

Parameters

 

You can specify only one of the following three parameters in one request: device, physical_channel, and nvmem_area. If you do not specify any of the three parameters, the method performs the following operation:

• If the session is initialized with device or physical channel, use default device or physical channel of the session for device or physical_channel.

 

Example

The following example shows a request with the device parameter:

{
   "id": "11",
   "jsonrpc": "2.0",
   "method": "getDevicePropertyList",
   "params":
   {
       "session_id": "_session0",
       "device": "SLSC-12001-030898C6-Mod1"
   }
}

The following example shows the response:

{
   "id": "11",
   "jsonrpc": "2.0",
   "result":
   {
       "static_properties":
       [
           "Dev.CapsVersion",
           "Dev.Chassis",
           "Dev.Commands",
           "Dev.Descr",
           "Dev.Events",
           "Dev.FirmwareVersion",
           "Dev.HardwareVersion",
           "Dev.Modules",
           "Dev.NumSlots",
           "Dev.NVMEM.Areas",
           "Dev.NVMEM.Size",
           "Dev.PhysChans",
           "Dev.ProductCategory",
           "Dev.ProductName",
           "Dev.ProductNum",
           "Dev.Properties",
           "Dev.SerialNum",
           "Dev.SlotNum",
           "Dev.TCPIP.EthernetIP",
           "Dev.TCPIP.EthernetMAC",
           "Dev.TCPIP.Hostname",
           "Dev.VendorName",
           "Dev.VendorNum"
       ],
       "dynamic_properties":
       [
           "NI.DateCode",
           "NI.Debug.Alphabet",
           "NI.Debug.LED0Bool",
           "NI.Debug.LED1Bool",
           "NI.Debug.LED2Bool"
       ]
   }
}

Back to Web API Method Reference

getProperty

Gets properties for devices or physical channels.

 

Parameters

 

You can specify only one of the following two parameters in one request: devices and physical_channels. If you do not specify any of the two parameters, the method performs operations in the following order:

1. Searches for the property in the list of system properties and session properties. If the property belongs to system property or session property, this method gets the value of the property.
2. If the property is not in the list of system properties and session properties and the session is initialized with devices, physical channels, or NVMEM areas, this method uses default devices, physical channels, or NVMEM areas of the session.

The following table lists the return values.

 

 

The following table lists keys and values for the data_type return value.

 

 

Example

The following example shows a request to get properties from multiple devices:

{
   "id": "12",
   "jsonrpc": "2.0",
   "method": "getProperty",
   "params":
   {
       "session_id": "_session0",
       "devices":
       [
           "SLSC-12001-030898C6-Mod1",
           "SLSC-12001-030898C6-Mod2"
       ],
       "property": "NI.DebugLED0"
   }
}

The following example shows the response:

{
   "id": "12",
   "jsonrpc": "2.0",
   "result":
   {
       "data_type": "Bool",
       "value":
       [
           false,
           true
       ]
   }
}

The following example shows a request to get properties from multiple physical channels:

{
   "id": "12",
   "jsonrpc": "2.0",
   "method": "getProperty",
   "params":
   {
       "session_id": "_session0",
       "physical_channels":
       [
           "SLSC-12001-030898C6-Mod1/LED0",
           "SLSC-12001-030898C6-Mod1/LED1"
       ],
       "property": "NI.ChannelName"
   }
}

The following example shows the response:

{
   "id": "12",
   "jsonrpc": "2.0",
   "result":
   {
       "data_type": "String",
       "value":
       [
           "LED0",
           "LED1"
       ]
   }
}

Back to Web API Method Reference

getPropertyInformation

Gets all information of a property. 

 

Parameters

 

You can specify only one of the following three parameters in one request: device, physical_channel, and nvmem_area. If you do not specify any of the three parameters, the method performs operations in the following order:

1. Search for the property in the list of system properties and session properties. If the property belongs to system property or session property, this method gets the value of the property.
2. If the property is not in the list of system properties and session properties and the session is initialized with devices, physical channels, or NVMEM areas, use default devices, physical channels, or NVMEM areas of the session.

 

Example

The following example shows a request for a static property:

{
 "id": "15",
 "jsonrpc": "2.0",
 "method": "getPropertyInformation",
 "params":
 {
   "session_id": "_session1",
   "device": "SLSC-12001-030FD4DE",
   "property": "Dev.FirmwareVersion"
 }
}

The following example shows the response for the static property:

{
   "jsonrpc": "2.0",
   "id": "15",
   "result": {
       "description": "Firmware Version",
       "document": "Indicates the firmware version for the device.",
       "data_type": "String",
       "access": "ReadOnly",
       "driver_defined": true,
       "pending_changes": false
   }
}

The following example shows a request for a dynamic property:

{
   "id": "15",
   "jsonrpc": "2.0",
   "method": "getPropertyInformation",
   "params":
   {
       "session_id": "_session0",
       "device": "SLSC-12001-030898C6-Mod2",
       "property": "NI.Debug.LED0Bool"
   }
}

The following example shows the response for the dynamic property:

{
   "id": "15",
   "jsonrpc": "2.0",
   "result": {
       "description": "One of 4 blue LEDs with Bool data type.",
       "documentation": "Towards back of module, under 2 caps, LED on far right",
       "unit": "",
       "min_value": false,
       "max_value": true,
       "access": "ReadWrite",
       "data_type": "Bool",
       "is_enum": false,
       "pending_changes": false
   }
}

Back to Web API Method Reference

getSessionPropertyList

Lists all session properties. The response of this method is static.

 

Parameters

 

 

Example

The following example shows a request:

{
   "id": "10",
   "jsonrpc": "2.0",
   "method": "getSessionPropertyList",
   "params":
   {
       "session_id": "_session0"
   }
}

The following example shows the response:

{
   "id": "10",
   "jsonrpc": "2.0",
   "result":
   {
       "properties":
       [
           "Sys.Chassis",
           "Sys.DeviceProperties",
           "Sys.Devices",
           "Sys.Modules",
           "Sys.NVMEMAreaProperties",
           "Sys.PhysChanProperties",
           "Sys.SessionProperties",
           "Sys.SystemProperties",
           "Session.ConnectedDevices",
           "Session.DefaultDevices",
           "Session.DefaultNVMEMAreas",
           "Session.DefaultPhysChans",
           "Session.ReservedDevices"
       ]
   }
}

Back to Web API Method Reference

setProperty

Sets properties for devices or physical channels. You must commit dynamic properties for the changes to take effect. You do not have to commit static properties. You can set only one property for one or multiple devices or physical channels.

 

Parameters

 

You can specify only one of the following two parameters in one request: devices and physical_channels. If you do not specify any of the two parameters, this method performs operations in the following order:

1. Search for the property in the list of system properties and session properties. If the property belongs to system property or session property, this method sets the value of the property.
2. If the property is not in the list of system properties and session properties and the session is initialized with devices or physical channels, use default devices or physical channels of the session.

 

Example

The following example shows a request:

{
   "id": "13",
   "jsonrpc": "2.0",
   "method": "setProperty",
   "params":
   {
       "session_id": "_session0",
       "property": "NI.DebugLED0",
       "devices":
       [
           "SLSC-12001-030898C6-Mod1",
           "SLSC-12001-030898C6-Mod2"
       ],
       "value":
       [
           true,
           false
       ]
   }
}

The following example shows the response:

{
   "id": "13",
   "jsonrpc": "2.0",
   "result": {}
}

Back to Web API Method Reference

executeCommand

Executes command on one or more devices or physical channels.

 

Parameters

 

You can specify only one of the following two parameters in one request: devices and physical_channels.

 

Example

The following example shows a request:

{
   "id": "17",
   "jsonrpc": "2.0",
   "method": "executeCommand",
   "params":
   {
       "session_id": "_session0",
       "devices":
       [
           "SLSC-12001-030898C6-Mod1",
           "SLSC-12001-030898C6-Mod2"
       ],
       "command": "NI.EnableLed0Immediate",
       "timeout": 10.0
   }
}

The following example shows the response:

{
   "id": "17",
   "jsonrpc": "2.0",
   "result": {}
}

Back to Web API Method Reference

getCommandInformation

Gets all information of a command. 

 

Parameters

 

You must specify one and only one of the following two parameters in one request: device and physical_channel.

 

Example

The following example shows a request:

{
   "id": "18",
   "jsonrpc": "2.0",
   "method": "getCommandInformation",
   "params":
   {
       "session_id": "_session0",
       "device": "SLSC-12001-030898C6-Mod2",
       "command": "NI.EnableLed0Immediate"
   }
}

The following example shows the response:

{
   "id": "18",
   "jsonrpc": "2.0",
   "result": {
       "description": "Enable LED 0 and complete immediately.",
       "documentation": "Enable LED 0 and complete immediately (doc)."
   }
}

Back to Web API Method Reference

getCommandList

Lists all commands of a device or physical channel. 

 

Parameters

 

You can specify only one of the following two parameters in one request: device and physical_channel.

 

Example

The following example shows a request to get all commands of a device:

{
   "id": "16",
   "jsonrpc": "2.0",
   "method": "getCommandList",
   "params":
   {
       "session_id": "_session0",
       "device": "SLSC-12001-030898C6-Mod1"
       ]
   }
}

The following example shows the response:

{
   "id": "16",
   "jsonrpc": "2.0",
   "result":
   {
       "commands":
       [
           "NI.EnableLed0Immediate",
           "NI.EnableLed0Delay",
           "NI.EnableLed0Poll",
           "NI.Event0TimerExpirationInterrupt",
           "NI.Event1TimerExpirationInterrupt",
           "NI.Event2TimerExpirationInterrupt",
           "NI.Event3TimerExpirationInterrupt"
       ]
   }
}

The following example shows a request to get all commands of a physical channel:

{
   "id": "16",
   "jsonrpc": "2.0",
   "method": "getCommandList",
   "params":
   {
       "session_id": "_session0",
       "physical_channel": "SLSC-12001-030898C6-Mod1/EventCounter0"
   }
}

The following example shows the response:

{
   "id": "16",
   "jsonrpc": "2.0",
   "result":
   {
       "commands":
       [
           "NI.EventCounter.Run",
           "NI.EventCounter.RunAsync",
           "NI.EventCounter.RunAndPoll"
       ]
   }
}

Back to Web API Method Reference

commitNvmemAreas

Commits pending changes to hardware for one or multiple NVMEM areas. If you set the same address multiple times before you commit the value, this method only commits the last value.

 

Parameters

 

Example

The following example shows a request:

{
   "id": "23",
   "jsonrpc": "2.0",
   "method": "commitNvmemAreas",
   "params":
   {
       "session_id": "_session0",
       "nvmem_areas":
       [
           "SLSC-12001-030898C6-Mod1/identification",
           "SLSC-12001-030898C6-Mod1/capabilities"
       ]
   }
}

The following example shows the response:

{
   "id": "23",
   "jsonrpc": "2.0",
   "result": {}
}

Back to Web API Method Reference

getNvmemBytes

Reads the specific number of bytes starting from the given address within an NVMEM area. 

 

Parameters

 

The following table lists the return value of this method.

 

 

Example

The following example shows a request:

{
   "id": "21",
   "jsonrpc": "2.0",
   "method": "getNvmemBytes",
   "params":
   {
       "session_id": "_session0",
       "nvmem_area": "SLSC-12001-030898C6/raw",
       "address": 65536,
       "size": 16
   }
}

The following example shows the response:

{
   "id": "21",
   "jsonrpc": "2.0",
   "result": {
       "data": [37, 80, 68, 70, 45, 49, 46, 213, 183, 23, 92, 12, 255, 255, 255, 255],
       "next_address": 65537
   }
}

Back to Web API Method Reference

setNvmemBytes

Sets the number of bytes of data to write to the given address within an NVMEM area. If you set the same address multiple times before you commit the value, this method only commits the last value. Some areas in the NVMEM of an SLSC module may be protected. You need to specify a serial number and password to write to protected areas. The following table lists the parameters of this method.

 

Parameters

 

The following table lists the return value of this method.

 

 

Example

The following example shows a request:

{
   "id": "22",
   "jsonrpc": "2.0",
   "method": "setNvmemBytes",
   "params":
   {
       "session_id": "_session0",
       "nvmem_area": "SLSC-12001-030898C6/raw",
       "address": 65536,
       "data": [37, 80, 68, 70, 45, 49, 46, 82, 93, 23, 92, 12, 255, 255, 255, 255]
   }
}

The following example shows the response:

{
   "id": "22",
   "jsonrpc": "2.0",
   "result":
   {
       "next_address": 65537
   }
}

Back to Web API Method Reference

 

readRegister

Reads the register of a device.

 

Parameters

 

The following table lists values for the size parameter. The size member does not have keys.

 

The following table lists the return values of this method:

 

 

Example

The following example shows a request:

{
   "id": "19",
   "jsonrpc": "2.0",
   "method": "readRegister",
   "params":
   {
       "session_id": "_session0",
       "device": "SLSC-12001-030898C6",
       "address": 256,
       "size": "64"
   }
}

The following example shows the response:

{
   "id": "19",
   "jsonrpc": "2.0",
   "result":
   {
       "next_address": 257,
       "data": 1
   }
}

Back to Web API Method Reference

writeRegister

Writes data to the register of a device.

 

Parameters

 

The following table lists values for the size parameter. The size member does not have keys.

 

The following table lists the return value of this method.

 

 

Example

The following example shows a request:

{
   "id": "20",
   "jsonrpc": "2.0",
   "method": "writeRegister",
   "params":
   {
       "session_id": "_session0",
       "device": "SLSC-12001-030898C6",
       "address": 256,
       "size": "64",
       "data": 512
   }
}

The following example shows the response:

{
   "id": "20",
   "jsonrpc": "2.0",
   "result":
   {
       "next_address": 257
   }
}

Back to Web API Method Reference

You can use the web API with various programming languages to create a web client to configure the SLSC device:

• Using the Web API with LabVIEW
• Using the Web API with Python
• Using the Web API with C++
• Using the Web API with C#

You can also refer to the attachment for the example code.

 

Using the Web API with LabVIEW

The following example uses the web API with LabVIEW. The POST VI sends a POST request to the web server. The web server returns the response in the response output.

 

Back to Using the Web API with Various Programming Languages

Using the Web API with Python

The following example uses the web API with Python 2.7. The example sends a POST request to the web server and reads the HTTP response.

# coding = utf-8
# using python 2.7
import urllib2
import json
json_text = '''{
"id": "1",
"jsonrpc": "2.0",
"method": "initializeSession",
"params":
{
   "access": "ReadWrite",
   "devices": "SLSC-12001-030BE71A",
   "force_reserve": true
}
}'''

request = urllib2.Request("http://10.144.160.151/nislsc/call",json_text)
response = urllib2.urlopen(request)
data = json.load(response)

if data.has_key('error'):
   if data['error'].has_key('data'):
       print(data['error']['data']['nislsc_message'])
   else:
       print(data['error']['message'])
else:
   print("session id = {}".format(data['result']['session_id']))

Back to Using the Web API with Various Programming Languages

Using the Web API with C++

HTTP support is not included in the C++ Standard Library. You can use some open-source libraries on github.com to use the web API with C++.

You can refer to the attachment for the example that uses the web API with C++ to send a POST request to the web server and read the HTTP response. The library for HTTP support that the example uses is from the embeddedRest repository at https://github.com/fnc12/embeddedRest.  

Back to Using the Web API with Various Programming Languages

Using the Web API with C#

You can refer to the attachment for the example that uses the web API with C# to send a POST request to the web server and read the HTTP response. 

Back to Using the Web API with Various Programming Languages