Firmware operating environment
Home / Device Management / Firmware operating environment

Firmware operating environment #

When managing and operating devices with Actcast, there are specific requirements for the actual environment in which they will be installed.

This section describes the operating environment required by the device firmware. If your device isn’t working as expected, check to see if you’ve met the conditions listed below.

Network #

The device firmware sends and receives various data over the network to manage and operate the device with Actcast. This section describes the recommended network environment for using Actcast comfortably and the requirements for using Actcast. The environment in which the device is installed must allow communication using the protocols described below and network connectivity with the communication host.

It also explains how to set up a wired connection and Wi-Fi connection.

It is recommended that the network in which the device is installed meets the following performance.

  • Internet line speed

    We recommend 50 Mbps or more for downlink and 10 Mbps or more for uplink based on actual measurements.

  • Internet connection

    We recommend that you have a stable connection at all times.

  • Wi-Fi standard

    We recommend 802.11g/n/ac.

  • network latency

    We recommend an environment with a measured RTT (round trip time) of 50 ms or less.

Protocol #

This section describes the protocols required for firmware operation and their role on Actcast. Actcast functions cannot be appropriately used in environments where communication through these protocols and ports is blocked.

  • DHCP (UDP/68, 67)

    Used to assign IP addresses to devices unless otherwise set in ActcastWriter . It is also used to obtain the address of the NTP server.

  • DNS (UDP/53)

    It is used to resolve hostnames that require communication, such as actcast.io.

  • NTP (UDP/123)

    Used to adjust the device time. The Raspberry Pi does not have an on-board RTC (Real Time Clock), so NTP is the only way to adjust the time. If the time is incorrect, a TLS connection cannot be established, making it impossible to communicate with the server and prevent proper operation and management of the device.

  • HTTP (TCP/80)

    It is used for time synchronization and firmware download.

  • HTTPS (TCP/443)

    It is used by actcast.io to control devices, upload status, download apps, etc.

  • MQTT (TCP/443)

    It is used to send device status, receive commands, etc.

Communication Host #

Lists the destination hosts with which the firmware communicates. In an environment where communication with these hosts is blocked or an environment that requires connection to a proxy for connection, the device cannot perform the necessary communication, so the Actcast function cannot be used normally.

  • DHCP Server

    A DHCP server provided on the network where the device is configured will be used.

  • DNS server

    The DNS server distributed by the DHCP server is used. If a DNS server address is specified when using a wired LAN connection (explained later), that DNS server will be used. If these DNS servers are found to be out of order, the following Public DNS servers will be used.

    • 8.8.8.8
    • 8.8.4.4

  • NTP Server

    Use the NTP server distributed by the DHCP server. If the DHCP server does not hand out NTP server addresses, the following NTP servers are used as default settings.

    • 0.debian.pool.ntp.org
    • 1.debian.pool.ntp.org
    • 2.debian.pool.ntp.org
    • 3.debian.pool.ntp.org

  • https://iot.actcast.io/

    It is used to register devices and send the results of various commands.

  • https://pkg.actcast.io

    It is used to download the updated contents when performing a firmware update.

  • mqtt://a1sgglpp228nnc-ats.iot.ap-northeast-1.amazonaws.com

    It is used to send Event Log, Device Log, and Act Log, and to receive configuration change notifications.

  • https://746316586548.dkr.ecr.ap-northeast-1.amazonaws.com

    Used for app downloads.

  • https://actcast-prd-thing-storage.s3.amazonaws.com/

    It is used to send images when using the TakePhoto command of Act.

Wired LAN connection #

Normally, to use a wired LAN connection, all you have to do is boot up with the LAN cable plugged into the device. However, if Wired is checked in Actcast Writer, the following items must be set correctly.

  • Static IPv4 address and subnet (CIDR format)
  • Router address (optional)
  • DNS server address (optional)

Wireless LAN connection #

The following is a list of items that are required or should be checked when using a wireless LAN.

  • Access points supported by the device are provided

    In the Raspberry Pi series, the communication standard that can be used differs depending on the type of board. Please check if there is an access point with a communication standard that can be used with your device. Please check the available Wi-Fi for the bands supported by each device.

  • A valid access point is configured

    Internet communication must be enabled for at least one of the access points configured on the dashboard of Writer or actcast.io. For more information on how it works when multiple access points are registered, see Wi-Fi Priority.

  • The signal strength is sufficient for the device to make the required communication.

    If the signal strength of the access point you are trying to use is not sufficient, stable communication cannot be established, and a NotFound status (see Device status) or firmware update fails.

    If there is no signal strength above approximately -70 dB as a guide, please review the location of the device or access point.

  • Stable connection

    The operation of the device may require continuous downloading of data of a coherent size. This occurs especially during firmware updates and Act installations, and depending on the type of application running, a large amount of communication may occur. If the network connection is unstable at this time, the operation is likely to fail. Below is a rough estimate of the amount of communication.

    • Firmware Update

      Several to several tens of MB

    • Download Act

      Tens to hundreds of MB

Camera #

Actcast has confirmed operation with an official camera with a CSI connection (Raspberry Pi Camera Module 2) or a camera with a USB connection. When installing Act, which requires a camera, on a device, one of the cameras must be connected to work properly at the time the installation is specified.

Back to Device Management