1. Introduction
2. Presentation
2.1 The YoctoHub-Wireless components
3. First steps
3.1 Manual configuration
3.2 Automated configuration
3.3 Connections
4. Assembly
4.1 Fixing
4.2 Fixing a sub-module
5. Using the YoctoHub-Wireless
5.1 Locating the modules
5.2 Testing the modules
5.3 Configuring modules
5.4 Upgrading firmware
6. Access control
6.1 Protected "admin" access
6.2 Protected "user" access
6.3 Access control and API
6.4 Deleting passwords
7. Interaction with external services
7.1 Configuration
7.2 User defined callback
7.3 Yocto-API callback
7.4 Xively (previously Cosm)
7.5 Thinkspeak
8. Programming
8.1 Accessing connected modules
8.2 Controlling the YoctoHub-Wireless
9. Sleep mode
9.1 Manual configuration of the wake ups
9.2 Configuring the wake up system by software
10. Personalizing the web interface
10.1 Using the file system
10.2 Limitations
11. High-level API Reference
11.1 Yocto-hub port interface
11.2 Wireless function interface
11.3 Network function interface
11.4 Files function interface
11.5 WakeUpMonitor function interface
11.6 WakeUpSchedule function interface
12. Characteristics
13. Index

1. Introduction

The YoctoHub-Wireless module is a 60x58mm module enabling you to control other Yoctopuce modules through a wireless network connection. Seen from the outside, this module behaves exactly like a standard computer running a VirtualHub¹: same interface, same functionalities.

The YoctoHub-Wireless is designed to be easily deployed and to not require any specific maintenance. In the opposite to a mini-computer, it does not have a complex operating system. Some simple settings allow you to use it in many kinds of network environments. These settings can be modified manually or automatically through USB. Therefore, the YoctoHub-Wireless is much more suited to industrialization than a mini-computer. However, you cannot run additional software written by the user on the YoctoHub-Wireless.

The YoctoHub-Wireless is not a standard USB hub with network access. Although it uses USB cables, its down ports use a proprietary protocol, much simpler than USB. It is therefore not possible to control, or even to power, standard USB devices with a YoctoHub-Wireless.

Yoctopuce thanks you for buying this YoctoHub-Wireless and sincerely hopes that you will be satisfied with it. The Yoctopuce engineers have put a large amount of effort to ensure that your YoctoHub-Wireless is easy to install anywhere and easy to use in any circumstance. If you are nevertheless disappointed with this device, do not hesitate to contact Yoctopuce support².

2. Presentation

1:	Yocto-button	9:	Sleep neutralization
2:	Control and power USB port	10:	Back connection
3:	Yocto-led	11:	Down port 1
4:	Overload led	12:	Down port 1 led
5:	Network transfer led	13:	Down port 2
6:	Wake up button	14:	Down port 2 led
7:	Sleep button	15:	Down port 3
8:	Antenna connector	16:	Down port 3 led

2.1. The YoctoHub-Wireless components

Serial number

Each Yocto-module has a unique serial number assigned to it at the factory. For YoctoHub-Wireless modules, this number starts with YHUBWLN1. The module can be software driven using this serial number. The serial number cannot be modified.

Logical name

The logical name is similar to the serial number: it is a supposedly unique character string which allows you to reference your module by software. However, in the opposite of the serial number, the logical name can be modified at will. The advantage is to enable you to build several copies of the same project without needing to modify the driving software. You only need to program the same logical name in each copy. Warning: the behavior of a project becomes unpredictable when it contains several modules with the same logical name and when the driving software tries to access one of these modules through its logical name. When leaving the factory, modules do not have an assigned logical name. It is yours to define.

Yocto-button

The Yocto-button has two functionalities. First, it can activate the Yocto-beacon mode (see below under Yocto-led). Second, if you plug in a Yocto-module while keeping this button pressed, you can then reprogram its firmware with a new version. Note that there is a simpler UI-based method to update the firmware, but this one works even if the firmware on the module is incomplete or corrupted.

Yocto-led

Normally, the Yocto-led is used to indicate that the module is working smoothly. The Yocto-led then emits a low blue light which varies slowly, mimicking breathing. The Yocto-led stops breathing when the module is not communicating any more, as for instance when powered by a USB hub which is disconnected from any active computer.

When you press the Yocto-button, the Yocto-led switches to Yocto-beacon mode. It starts flashing faster with a stronger light, in order to facilitate the localization of a module when you have several identical ones. It is indeed possible to trigger off the Yocto-beacon by software, as it is possible to detect by software that a Yocto-beacon is on.

The Yocto-led has a third functionality, which is less pleasant: when the internal software which controls the module encounters a fatal error, the Yocto-led starts emitting an SOS in morse ³. If this happens, unplug and re-plug the module. If it happens again, check that the module contains the latest version of the firmware and, if it is the case, contact Yoctopuce support⁴.

Power / Control port

This port allows you to power the YoctoHub-Wireless and the modules connected to it with a simple USB charger. This port also allows you to control the YoctoHub-Wireless by USB, exactly like you can do it with a classic Yoctopuce module. It is particularly useful when you want to configure the YoctoHub-Wireless without knowing its IP address.

Down ports

You can connect up to three Yoctopuce modules on these ports. They will then be available as if they were connected to a computer running a VirtualHub. Note that the protocol used between the YoctoHub-Wireless and the USB modules is not USB but a lighter proprietary protocol. Therefore, the YoctoHub-Wireless cannot manage devices other than Yoctopuce devices. A standard USB hub does not work either⁵. If you want to connect more than three Yoctopuce modules, just connect one or more YoctoHub-Shield⁶ to the back ports.

Warning: the USB connectors are simply soldered in surface and can be pulled out if the USB plug acts as a lever. In this case, if the tracks stayed in position, the connector can be soldered back with a good iron and flux to avoid bridges. Alternatively, you can solder a USB cable directly in the 1.27mm-spaced holes near the connector.

Antenna connector

The YoctoHub-Wireless includes an ultra miniature coaxial antenna connector (UFL). Take care of the UFL connector. It is fragile and is not designed to support many connection/deconnection cycles. The YoctoHub-Wireless is sold with a small UFL cable to RP-SMA socket (reverse polarity SMA: threaded on the outside with a plug in the center) and a corresponding RP-SMA plug antenna (threaded on the inside, jack in the center). You can use another antenna of your choice, as long as it is designed for the 2.4 GHz frequency range and it has the correct connector. Beware of the different variants of SMA connectors: there are antennas for each of the four combinations SMA/RP-SMA and plug/socket. Only an RP-SMA plug antenna can be used with the provided antenna cable. Beware also that using a high-gain antenna may drive you to emit a signal stronger than the authorized norm in your country.

Antenna connection

Overload led

The YoctoHub-Wireless continuously monitors its power consumption. If it detects a global consumption of more that 2A, following an overload on one of the down ports for example, it automatically disables all the down ports and lights the overload led. To isolate the source of the issue, you can reactivate the ports one by one, monitoring the power consumption increase. Alternatively, if you know the source of the overload issue and know to have solved it, you can restart the YoctoHub-Wireless to enable all its ports at once.

Note that the overload led is a protection measure which can prevent overheating, but it is not a protection guarantee against shorts.

Sleep

Usually, the YoctoHub-Wireless consumes about 0.5 Watt (110mA), to which you must add the connected module consumption. But it is able to get into sleep to reduce its power consumption to a strict minimum, and to wake up at a precise time (or when an outside contact is closed). This functionality is very useful to build measuring installations working on a battery. When the YoctoHub-Wireless is in sleep mode, most of the electronics of the module as well as the connected Yoctopuce modules are switched off. This reduces the total consumption to 75 µW (15 µA).

Switching to sleep and waking up can be programmed based on a schedule, controlled by software, or controlled manually with two push buttons located on the YoctoHub-Wireless circuit. You can find there two pairs of contacts which enable you to shunt these two buttons.

Sleep and wake up buttons deviation.

The YoctoHub-Wireless includes a switch with which you can disable the sleep mode at the hardware level. This functionality is particularly useful when developing and debugging your project, as well as when updating the firmware.

3. First steps

The aim of this chapter is to help you connect and configure your YoctoHub-Wireless for the first time.

3.1. Manual configuration

If you must use a specific network configuration, you can configure your YoctoHub-Wireless through its USB control port, by using the VirtualHub⁷.

Run the VirtualHub on your preferred computer and connect it to the power / control port of the YoctoHub-Wireless. You need a USB A-MicroB cable.

Configuration: connecting your YoctoHub-Wireless by USB to a computer

Launch your preferred browser⁸ on the URL of your VirtualHub. It usually is http://127.0.0.1:4444. You obtain the list of Yoctopuce modules connected by USB, among which your YoctoHub-Wireless.

List of Yoctopuce modules connected by USB to your computer, among which your YoctoHub-Wireless

Click on the configure button corresponding to your YoctoHub-Wireless. You obtain the module configuration window. This window contains a Network configuration section.

YoctoHub-Wireless module configuration window

Connection to the wireless network

You must first configure your YoctoHub-Wireless to enable it to connect itself to your wifi network. To do so, click on the edit button corresponding to WLAN settings in the Network configuration section. The configuration window of the wireless network shows up:

Wireless network configuration window.

You can then decide if you wish to connect your YoctoHub-Wireless to an existing network, or if you would rather manually enter the SSID of network you wish to use.

You can also configure the YoctoHub-Wireless for it to generate its own wireless network in ad-hoc mode. You can then connect yourself directly on the YoctoHub-Wireless without having to go through an infrastructure server (access point). However, be aware that the ad-hoc mode has important limitations compared to a real wifi network. In particular, devices under Android cannot connect themselves to it.

When you have set the wireless network parameters, and possibly tested them, you can click on the OK button to close this configuration window and go back to the main configuration window.

If needed, you can also configure which IP address must be assigned to the YoctoHub-Wireless. To do so, click on the edit button opposite to the IP addressing line in the main window.

You can then choose between a DHCP assigned IP address or a fixed IP address for your YoctoHub-Wireless module. The DHCP address is recommended in so much as this functionality is supported by most ADSL routers (its the default configuration). If you do not know what a DHCP server is but are used to connect machines on your network and to see them work without any problem, do not touch anything.

You can also choose the network name of your YoctoHub-Wireless. You can then access your YoctoHub-Wireless by using this name rather than its IP address. When the network part is configured, click on the Save button to save your changes and close the configuration window. These modifications are saved in the persistent memory of the YoctoHub-Wireless, they are kept even after the module has been powered off.

Click on the serial number corresponding to your YoctoHub-Wireless. This opens your module property window:

The YoctoHub-Wireless properties

This window contains a section indicating the state of the YoctoHub-Wireless network part. You can find there its MAC address, current IP address, and network name. This section also provides the state of the network connection. Possible states are:

• 0- search for link: The module is searching for a connection with the network. If this state persists, the sought wifi network is most likely not in the neighborhood.
• 1- network exists: The sought wifi network was detected.
• 2- network linked: The YoctoHub-Wireless did connect to the network.
• 3- DHCP ready: The local network is working (IP address obtained).
• 4- DNS ready: DNS server is reachable on the network.
• 5- WWW ready: The module has checked Internet connectivity by connecting itself to a time server (NTP).

When you have checked that your module does indeed have a valid IP address, you can close the property window, stop your VirtualHub, and disconnect your USB cable. They are not needed anymore.

From now on, you can access your YoctoHub-Wireless by typing its IP address directly in the address field of your preferred browser. The module answers to the standard HTTP port, but also to the 4444 port used by the VirtualHub. If your module IP address is 192.168.0.10, you can therefore access it with the http://192.168.0.10 URL.

The YoctoHub-Wireless interface is identical to that of a VirtualHub.

If you have assigned a name to your YoctoHub-Wireless, you can also use this name on the local network. For example, if your have used the yoctohub network name, you can contact the module with the http://yoctohub URL under Windows and the http://yoctohub.local URL under Mac OS X and Linux. Note that this technique is limited to the subnet of the YoctoHub-Wireless. If you want to contact the module by name from another network, you must use a classic DNS infrastructure.

3.2. Automated configuration

You can industrialize the YoctoHub-Wireless network configuration. You can find in the following chapters of this documentation the description of the programming functions enabling you to read the Ethernet address (MAC address) of a module, and to configure all of its network parameters.

The network configuration functions are also available as command lines, using the YNetwork utility software available in the command line programming library ⁹.

After having set some parameters by software, make sure to call the saveToFlash() function to ensure that the new settings are saved permanently in the module flash memory.

3.3. Connections

Power supply

The YoctoHub-Wireless must be powered by the USB control socket.

USB

Simply connect a USB charger in the power / control port port, but make sure that the charger provides enough electric power. The YoctoHub-Wireless consumes about 110mA, to which you must add the power consumption of each submodule. The YoctoHub-Wireless is designed to manage a maximum of 2A. Therefore, we recommend a USB charger able to deliver at least 2A. Moreover, you must make sure that the total power consumption of the set "hub + submodules" does not go above this limit.

The YoctoHub-Wireless can be powered by a regular USB charger

Sub-modules

The YoctoHub-Wireless is able to drive all the Yoctopuce modules of the Yocto range. These modules can be directly connected to the down ports. They are automatically detected. For this, you need Micro-B Micro-B USB cables. Whether you use OTG cables or not does not matter.

Connecting sub-modules with USB cables

Alternatively, you can connect your modules by directly soldering electric cables between the YoctoHub-Wireless and its sub-modules. Indeed, all the Yoctopuce modules have contacts designed for direct cabling. We recommend you to use solid coper ribbon cables, with a 1.27mm pitch. Solid copper ribbon cable is less supple than threaded cable but easier to solder. Pay particular attention to polarity: the YoctoHub-Wireless, like all modules in the Yoctopuce range, is not protected against polarity inversion. Such an inversion would likely destroy your devices. Make sure the positions of the square contacts on both sides of the cable correspond.

Sub-module connection with ribbon cable

The YoctoHub-Wireless is designed so that you can fix a single width module directly on top of it. To do so, you need screws, spacers¹⁰, and a 1.27mm pitch connector¹¹. You can thus transform your USB Yoctopuce module into a network module while keeping a very compact format.

Fixing a module directly on the hub

Beware, the YoctoHub-Wireless is designed to drive only Yoctopuce modules. Indeed, the protocol used between the YoctoHub-Wireless and the sub-modules is not USB but a much lighter proprietary protocol. If, by chance, you connect a device other than a Yoctopuce module on one of the YoctoHub-Wireless down ports, this port is automatically disabled to prevent damages to the device.

4. Assembly

This chapter provides important information regarding the use of the YoctoHub-Wireless module in real-world situations. Make sure to read it carefully before going too far into your project if you want to avoid pitfalls.

4.1. Fixing

While developing your project, you can simply let the hub hang at the end of its cable. Check only that it does not come in contact with any conducting material (such as your tools). When your project is almost at an end, you need to find a way for your modules to stop moving around.

Examples of assembly on supports

The YoctoHub-Wireless module contains 3mm assembly holes. You can use these holes for screws. The screw head diameter must not be larger than 8mm or the heads will damage the module circuits.

Make sure that the lower surface of the module is not in contact with the support. We recommend using spacers. You can fix the module in any position that suits you: however be aware that the YoctoHub-Wireless electronic components, in particular the network part, generate heat. You must not let this heat accumulate.

4.2. Fixing a sub-module

The YoctoHub-Wireless is designed so that you can screw a single width module directly on top of it. By single width, we mean modules with a 20mm width. All the single width modules have their 5 assembly holes and the USB socket in the same position. The sub-module can be assembled with screws and spacers. At the back of the YoctoHub-Wireless and sub-module USB connectors, there are a set of 4 contacts enabling you to easily perform an electrical connection between the hub and the sub-module. If you do not feel sufficiently at ease with a soldering iron, you can also use a simple Micro-B Micro-B USB cable, OTG or not.

Fixing a module directly on the hub

Make sure to mount your module on the designed side, as illustrated above. The module 5 holes must correspond to the YoctoHub-Wireless 5 holes, and the square contact on the module must be connected to the square contact on the YoctoHub-Wireless down port. If you assemble a module on the other side or in another way, the connector polarity will be inverted and you risk to permanently damage your equipment.

All the accessories necessary to fix a module on your YoctoHub-Wireless are relatively usual. You can find them on the Yoctopuce web site, as on most web sites selling electronic equipment. However, beware: the head of the screws used to assemble the sub-module must have a maximum head diameter of 4.5mm, otherwise they could damage the electronic components.

5. Using the YoctoHub-Wireless

Apart from providing network access to the Yoctopuce module, the YoctoHub-Wireless enables you to test and configure your Yoctopuce modules. To do so, connect yourself to your YoctoHub-Wireless with your favorite web browser¹². Use the IP address of the YoctoHub-Wireless or its network name, for example http://192.168.0.10. The list of the connected modules should appear.

YoctoHub-Wireless web interface

5.1. Locating the modules

The main interface displays a line per connected module; if you have several modules of the same model, you can locate a specific module by clicking on the corresponding beacon button: it makes the blue led of the module start blinking and displays a blue disk at the beginning of the corresponding line in the interface. Pressing the Yocto-button of a connected module has the same effect.

Yocto-button (1) and localization led (2) of the Yocto-Demo module. These two elements are usually placed in the same location, whatever the module.

5.2. Testing the modules

To test a module, simply click on the serial number of a module in the interface, a window specific to the module opens. This window generally allows you to activate the main functions of the module. Refer to the User's guide of the corresponding module for more details ¹³.

Property window of the Yocto-Demo module, obtained from the YoctoHub-Wireless interface

5.3. Configuring modules

You can configure a module by clicking on the corresponding configure button in the main interface. A window, specific to the module, then opens. This window allows you minimally to assign a logical name to the module and to update its firmware. Refer to the User's guide of the corresponding module for more details.

"Configuration" window of the Yocto-Demo module

5.4. Upgrading firmware

The Yoctopuce modules are in fact real computers, they even contain a small web server. And, as all computers, it is possible to update their control software (firmware). New firmware for each module are regularly published, they generally allow you to add new functionalities to the module, and/or to correct a hypothetical bug¹⁴.

To update a module firmware, you must first get the new firmware. It can be downloaded from the module product page on the Yoctopuce web site¹⁵. The interface offers also a direct link if it detects that the firmware is not up-to-date ¹⁶. Firmware is available as .byn files of a few tens of kilobytes. Save the one you are interested in on your local disk.

Firmware update window

When the firmware file is locally available, open the module configuration window and click on the upgrade button. The interface asks you to select the firmware file you wish to use. Enter the file name and click on Upload. From then on, everything is automatically performed: the YoctoHub-Wireless restarts the module in "update" mode, updates the firmware, then restarts the module in normal mode. The module configuration settings are kept. Do not disconnect the module during the update process.

The YoctoHub-Wireless firmware can be updated in the same manner.

If control is lost during a firmware update (power failure or unwanted disconnection), it is always possible to manually force a firmware reload, even if the sub-module does not even appear in the YoctoHub-Wireless window. In this case, disconnect the module, and reconnect it while keeping the Yocto-button pressed. This starts the module in "update" mode. You can restart the firmware update process.

6. Access control

The YoctoHub-Wireless is able to perform access control to protect your Yoctopuce devices. Click on the configure button on the line matching the YoctoHub-Wireless in the user interface.

Click on the "configure" button on the first line

Then the configuration window for the YoctoHub-Wireless shows up.

The YoctoHub-Wireless configuration window.

Access control can be configured from the Incoming connections section. There are two levels of access control.

6.1. Protected "admin" access

The admin password locks write access on the modules. When the admin password is set, only users using the admin login are allowed read and write access to the modules. The users using the admin login can configure the modules seen by this YoctoHub-Wireless as they wish.

6.2. Protected "user" access

The user password locks read access to the Yoctopuce modules. When set, any use without password becomes impossible. The user access type allows only read-only access to the modules, that is only to consult the states of the modules. If you simultaneously create "admin" and "user" access controls, users with a "user" login cannot modify the configuration of modules seen by this YoctoHub-Wireless.

If you configure an admin access, without configuring a user access, users are still able to read your device values without any password.

To set up YoctoHub-Wireless access, click the edit button on the line Authentication to read the information from the devices or Authentication to write information to the devices

6.3. Access control and API

Warning, the access control has an impact on Yoctopuce API behavior when trying to connect to this YoctoHub-Wireless. With Yoctopuce API, access control is handled at RegisterHub() function call level. You need to provide the YoctoHub-Wireless address as follow: login:password@address:port, here is an exemple:

6.4. Deleting passwords

If you forget your YoctoHub-Wireless password, the only way to regain control is to reset all the settings to the default value. To do so, find a USB cable for the YoctoHub-Wireless and connect it to a computer running the VirtualHub¹⁷ while keeping the Yocto-button pressed. This forces the YoctoHub-Wireless to start in firmware update mode. It then appears in the VirtualHub below the module list. Click on its serial number and select a firmware file to load on the module. When the firmware is reloaded with this method, the module is reset to the factory settings, without access control.

7. Interaction with external services

The YoctoHub-Wireless can publish the state of connected devices on any web server. The values are posted on a regular basis and each time one of them changes significantly. This feature enables you to interface your Yoctopuce devices with many web services.

7.1. Configuration

To use this feature, just click on the configure button located on the line matching the YoctoHub-Wireless on the main user interface. Then look for the Outgoing calbacks section and click on the edit button.

Just click on the "Configure" button on the first line.

Then edit the "Outgoing callbacks" section.

The callback configuration window shows up. This window enables you to define how your YoctoHub-Wireless interacts with an external web server. Several interaction types are at your disposal.

7.2. User defined callback

The "User defined callback" allow you to fully customize the way the YoctoHub-Wireless interacts with an external web site. You need to provide the URL of the web server where you want the hub to post data. Note that only HTTP protocol is supported (no HTTPS).

The callback configuration window.

If you want to secure access to your callback script, you can setup a standard HTTP authentication. The YoctoHub-Wireless knows how to handle standard HTTP authentication schemes: simply fill in the user and and password fields needed to access the URL. Both Basic and Digest authentication are supported. However, Digest authentication is highly recommended, since it uses a challenge mechanism that avoids sending the password itself over the Internet, and prevents replays.

The YoctoHub-Wireless posts the advertised values¹⁸ on a regular basis, and each time one of these values changes significantly. You can change the default delay between posts.

Tests

To help you debug the process, you can visualize with the YoctoHub-Wireless the answer to the callback sent by the web server. Click on the test button when all required fields are filled. When the result meets your expectations, close the debug window and then click on the "Ok" button.

Format

Values are posted in one of the following formats:

1. If the function has been assigned a logical name:

FUNCTION_NAME = VALUE

2. If the module has been assigned a logical name, but not the function:

MODULE_NAME#HARDWARE_NAME = VALUE

3. If no logical name has been set:

SERIAL_NUMBER#HARDWARE_NAME = VALUE

Here is a short PHP script allowing you to visualize the data posted by the callback and the result in the debug window:

Callback test results with a Yocto-PowerRelay and a Yocto-Temperature.

7.3. Yocto-API callback

The PHP Yoctopuce API is able to work on callback mode. This way, a PHP script can take control of Yoctopuce devices installed behind a NAT filter without having to open any port. Typically, this allows you to control Yoctopuce devices running on a LAN behind a private ADSL router from a public web site. The YoctoHub-Wireless then acts as a gateway. All you have to do is to define the PHP script URL and, if applicable, the credentials needed to access it. You can find more information about this callback mode in your Yoctopuce device User's guide.

7.4. Xively (previously Cosm)

Xively¹⁹ is a paying cloud based service (with a free but limited development mode) enabling you to draw graphs with data coming from your Yoctopuce sensors. You can interface your Yoctopuce sensors with Xively without having to write a single line of code. To achieve this, you need to create a Xively account, then to define a feed ID and a API key on the Xively site. Then enter those two parameters in the YoctoHub-Wireless user interface. That's it. If needed, you will find more information about Xively in the Yoctopuce Blog²⁰. Yoctopuce is not affiliated to Xively.

7.5. Thinkspeak

ThingSpeak²¹ is another cloud service, but completely free. It also enables you to trace graphs with data coming from your Yoctopuce sensors. This service presents some feature limitations compared to Xively, but it has the advantage of not requiring any paying license. You can find on the Yoctopuce blog ²² how to configure your YoctoHub-Wireless to post data directly on ThinkSpeak. Yoctopuce is not affiliated to ThingSpeak.

8. Programming

8.1. Accessing connected modules

The YoctoHub-Wireless behaves itself exactly like a computer running a VirtualHub. The only difference between a program using the Yoctopuce API with modules in native USB and the same program with Yoctopuce modules connected to a YoctoHub-Wireless is located at the level of the registerHub function call. To use USB modules connected natively, the registerHub parameter is usb. To use modules connected to a YoctoHub-Wireless, you must simply replace this parameter by the IP address of the YoctoHub-Wireless. For instance, in Delphi:

becomes

8.2. Controlling the YoctoHub-Wireless

From the programming API standpoint, the YoctoHub-Wireless is a module like the others. You can perfectly manage it from the Yoctopuce API. To do so, you need the following classes:

Module

This class, shared by all Yoctopuce modules, enables you to control the module itself. You can drive the Yocto-led, know the USB power consumption of the YoctoHub-Wireless, and so on.

Network

This class enables you to manage the network part of the YoctoHub-Wireless. You can control the link state, read the MAC address, change the YoctoHub-Wireless IP address, know the power consumption on PoE, and so on.

HubPort

This class enables you to manage the hub part. You can enable or disable the YoctoHub-Wireless ports, you can also know which module is connected to which port.

Files

This class enables you to access files stored in the flash memory of the YoctoHub-Wireless. The YoctoHub-Wireless contains a small file system which allows you to store, for example, a web application controlling the modules connected to the YoctoHub-Wireless.

WakeMonitor

This class enables you to monitor the sleep mode of the YoctoHub-Wireless.

WakeSchedule

This class enables you to schedule one or several wake ups for the YoctoHub-Wireless.

You can find some examples on how to drive the YoctoHub-Wireless by software in the Yoctopuce programming libraries, available free of charge on the Yoctopuce web site.

9. Sleep mode

The YoctoHub-Wireless includes a real time clock (RTC) powered by a super capacitor. This capacitor charges itself automatically when the module is powered. But it is able to keep time without any power for several days. This RTC is used to drive a sleep and wake up system to save power. You can configure the sleep system manually through an interface or drive it through software.

9.1. Manual configuration of the wake ups

You can manually configure the wake up conditions by connecting yourself on the interface of the YoctoHub-Wireless. In the Wake-up scheduler section of the main configuration window, click on the setup button corresponding to one of the "wakeup-schedule". This opens a window enabling you to schedule more or less regular wake ups. Select the boxes corresponding to the wanted occurrences. Empty sections are ignored.

Wake up configuration window: here every 10 minutes between 9h and 17h.

Likewise, you can configure directly in the YoctoHub-Wireless interface the maximal wake up duration, after which the module automatically goes back to sleep. If your YoctoHub-Wireless is running on batteries, this ensures they do not empty even if no explicit sleep command is received.

9.2. Configuring the wake up system by software

At the programming interface level, the wake up system is implemented with two types of functions: the wakeUpMonitor function and the wakeUpSchedule function.

wakeUpMonitor

The wakeUpMonitor function manages wake ups and sleep periods, proper. It provides all the instant managing functionalities : instant wake up, instant sleep, computing the date of the next wake up, and so on...

The wakeUpMonitor function enables you also to define the maximum duration during which the YoctoHub-Wireless stays awake before automatically going back to sleep.

wakeUpSchedule

The wakeUpSchedule function enables you to program a wake up condition followed by a possible sleep. It includes five variables enabling you to define correspondences on minutes, hours, days of the week, days of the month, and months. These variables are integers where each bit defines a correspondence. Schematically, each set of minutes, hours, and days is represented as a set of boxes with each a coefficient which is a power of two, exactly like in the corresponding interface of the YoctoHub-Wireless.

For example, bit 0 for the hours corresponds to hour zero, bit 1 corresponds to hour 1, bit 2 to hour 2, and so on.

To each box is assigned a power of two

Thus, to program the YoctoHub-Wireless for it to wake up every day at noon, you must set bit 12 to 1, which corresponds to the value 2^12 = 4096.

Example for a wake up at 12h

For the module to wake up at 0 hour, 6 hours, and 12 hours, you must set the 0, 6, and 12 bits to 1, which corresponds to the value 2^0 +2^6 +2^12 = 1 + 64 + 4096 = 4161

Example for wake ups at 0, 6, and 12h

Variables can be combined. For a wake up to happen every day at 6h05, 6h10, 12h05, and 12h10, you must set the hours to 2^6 + 2^12 = 4060, minutes to 2^5 and 2^10 = 1056. Variables remaining at the zero value are ignored.

Example for wake ups at 6H05, 6h10, 12h05, and 12h10

Note that if you want to program a wake up at 6h05 and 12h10, but not at 6h10 and 12h05, you need to use two distinct wakeUpSchedule functions.

This paradigm allows you to schedule complex wake ups. Thus, to program a wake up every first Tuesday of the month, you must set to 1 bit 1 of the days of the week and the first seven bits of the days of the month.

Example for a wake up every first Tuesday of the month

Some programming languages, among which JavaScript, do not support 64 bit integers. This is an issue for encoding minutes. Therefore, minutes are available both through a 64 bit integer minutes and two 32 bit integers minutesA and minutesB. These 32 bit integers are supposed to be available in any current programming language.

Minutes are also available in the shape of two 32 bit integers

The wakeUpSchedule function includes an additional variable to define the duration, in seconds, during which the module stays awake after a wake up. If this variable is set to zero, the modules stays awake.

The YoctoHub-Wireless includes two wakeUpSchedule functions, enabling you to program up to two independent wake up types.

10. Personalizing the web interface

Your YoctoHub-Wireless contains a small embedded file system, allowing it to store personalized files for its own use. You can manipulate the file system thanks to the yocto_files library. You can store there the files you want to. If need be, you can store a web application enabling you to manage modules connected to your YoctoHub-Wireless.

10.1. Using the file system

Interactive use

The YoctoHub-Wireless web interface provides a succinct interface to manipulate the content of the file system: simply click the configuration button corresponding to your module in the hub interface, then the manage files button. The files are listed and you can view them, erase them, or add new ones (downloads).

Because of its small size, the file system does not have an explicit concept of directories. You can nevertheless use the slash sign "/" inside file names to sort them as if they were in directories.

Programmed use

Use the yocto_files library to manage the file system. Basic functions are available:

• upload creates a new file on the module, with a content that you provide;
• get_list lists the files on the module, including their content size and CRC32;
• download retrieves in a variable the content of a file present on the module;
• remove erases a file from the module;
• format resets the file system to an empty, not fragmented state.

A piece of software using a well designed file system should always start by making sure that all the files necessary for its working are available on the module and, if needed, upload them on the module. We can thus transparently manage software updates and application deployment on new modules. To make file versions easier to detect, the get_list method returns for each file a 32 bit signature called CRC (Cyclic Redundancy Check) which identifies in a reliable manner the file content. Thus, if the file CRC corresponds, there is less than one chance over 4 billions that the content is not the correct one. You can even compute in advance in your software the CRC of the content you want, and therefore check it without having to download the files. The CRC function used by the Yoctopuce file system is the same as Ethernet, Gzip, PNG, etc. Its characteristic value for the nine character string "123456789" is 0xCBF43926.

HTTP use

You can access the files that your have downloaded on your YoctoHub-Wireless by HTTP at the root of the module (at the same level as the REST API). This allows you to load personalized HTML and Javascript interface pages, for example. You cannot, however, replace the content of a file preloaded on the module, you can only add new ones.

UI and optimisation

Since you can store files on the hub file system, you can easily build a web application to control the devices connected to the hub and store it directly on the hub. This is a very convenient way to build system remote controlled by tablets or smart phones. However the web server embedded in the hub have limited connectivity capabilities: only a few number of sockets can be opened at the same time. Since most web browsers tend to open as many connection as they can to load all elements in a web page, this might lead to very long loading time. To prevent this, try to keep your UI pages as compact as possible by embedding the javascript, CSS code and if possible, images in base64 code.

10.2. Limitations

The file system embedded on your YoctoHub-Wireless has some technical limitations:

• Its maximal storage space is 3.5Mo, allocated in blocks enabling to store up to about 800 files.
• Erasing a file does not necessarily immediately free all the space used by the file. The non freed space is completely reused if you create a new file with the same name, but not necessarily if you create files with a distinct name each time. For this reason, it is not recommended to automatically create files with distinct names.
• You can recover the complete non freed space with the format command which frees all the files.
• Each firmware update implicitly provokes a complete reformatting of the file system.
• As all flash memories, the memory used to store the files has a life of about 100'000 erasing cycles. It is enough, but it is not infinite. Make sure that you do not write and erase files uselessly and very quickly in a loop, or you may destroy your module.

11. High-level API Reference

This chapter summarizes the high-level API functions to drive your YoctoHub-Wireless. Syntax and exact type names may vary from one language to another, but, unless otherwise stated, all the functions are available in every language. For detailed information regarding the types of arguments and return values for a given language, refer to the definition file for this language (yocto_api.* as well as the other yocto_* files that define the function interfaces).

For languages which support exceptions, all of these functions throw exceptions in case of error by default, rather than returning the documented error value for each function. This is by design, to facilitate debugging. It is however possible to disable the use of exceptions using the yDisableExceptions() function, in case you prefer to work with functions that return error values.

This chapter does not explain Yoctopuce programming concepts, in order to stay as concise as possible. You will find more details in the documentation of the devices you plan to connect to your YoctoHub-Wireless.

11.1. Yocto-hub port interface

YHubPort objects provide control over the power supply for every YoctoHub port and provide information about the device connected to it. The logical name of a YHubPort is always automatically set to the unique serial number of the Yoctopuce device connected to it.

Global functions
yFindHubPort(func)
Retrieves a Yocto-hub port for a given identifier.
yFirstHubPort()
Starts the enumeration of Yocto-hub ports currently accessible.
YHubPort methods
hubport→describe()
Returns a short text that describes unambiguously the instance of the Yocto-hub port in the form TYPE(NAME)=SERIAL.FUNCTIONID.
hubport→get_advertisedValue()
Returns the current value of the Yocto-hub port (no more than 6 characters).
hubport→get_baudRate()
Returns the current baud rate used by this Yocto-hub port, in kbps.
hubport→get_enabled()
Returns true if the Yocto-hub port is powered, false otherwise.
hubport→get_errorMessage()
Returns the error message of the latest error with the Yocto-hub port.
hubport→get_errorType()
Returns the numerical error code of the latest error with the Yocto-hub port.
hubport→get_friendlyName()
Returns a global identifier of the Yocto-hub port in the format MODULE_NAME.FUNCTION_NAME.
hubport→get_functionDescriptor()
Returns a unique identifier of type YFUN_DESCR corresponding to the function.
hubport→get_functionId()
Returns the hardware identifier of the Yocto-hub port, without reference to the module.
hubport→get_hardwareId()
Returns the unique hardware identifier of the Yocto-hub port in the form SERIAL.FUNCTIONID.
hubport→get_logicalName()
Returns the logical name of the Yocto-hub port.
hubport→get_module()
Gets the YModule object for the device on which the function is located.
hubport→get_module_async(callback, context)
Gets the YModule object for the device on which the function is located (asynchronous version).
hubport→get_portState()
Returns the current state of the Yocto-hub port.
hubport→get_userData()
Returns the value of the userData attribute, as previously stored using method set_userData.
hubport→isOnline()
Checks if the Yocto-hub port is currently reachable, without raising any error.
hubport→isOnline_async(callback, context)
Checks if the Yocto-hub port is currently reachable, without raising any error (asynchronous version).
hubport→load(msValidity)
Preloads the Yocto-hub port cache with a specified validity duration.
hubport→load_async(msValidity, callback, context)
Preloads the Yocto-hub port cache with a specified validity duration (asynchronous version).
hubport→nextHubPort()
Continues the enumeration of Yocto-hub ports started using yFirstHubPort().
hubport→registerValueCallback(callback)
Registers the callback function that is invoked on every change of advertised value.
hubport→set_enabled(newval)
Changes the activation of the Yocto-hub port.
hubport→set_logicalName(newval)
Changes the logical name of the Yocto-hub port.
hubport→set_userData(data)
Stores a user context provided as argument in the userData attribute of the function.
hubport→wait_async(callback, context)
Waits for all pending asynchronous commands on the module to complete, and invoke the user-provided callback function.

YHubPort.FindHubPort()
yFindHubPort()yFindHubPort()YHubPort.FindHubPort()yFindHubPort()yFindHubPort()[YHubPort FindHubPort: ]yFindHubPort()yFindHubPort()YHubPort.FindHubPort()YHubPort.FindHubPort()YHubPort.FindHubPort()

Retrieves a Yocto-hub port for a given identifier.

The identifier can be specified using several formats:

• FunctionLogicalName
• ModuleSerialNumber.FunctionIdentifier
• ModuleSerialNumber.FunctionLogicalName
• ModuleLogicalName.FunctionIdentifier
• ModuleLogicalName.FunctionLogicalName

This function does not require that the Yocto-hub port is online at the time it is invoked. The returned object is nevertheless valid. Use the method YHubPort.isOnline() to test if the Yocto-hub port is indeed online at a given time. In case of ambiguity when looking for a Yocto-hub port by logical name, no error is notified: the first instance found is returned. The search is performed first by hardware name, then by logical name.

Parameters :

Returns :

a YHubPort object allowing you to drive the Yocto-hub port.

YHubPort.FirstHubPort()
yFirstHubPort()yFirstHubPort()YHubPort.FirstHubPort()yFirstHubPort()yFirstHubPort()[YHubPort FirstHubPort]yFirstHubPort()yFirstHubPort()YHubPort.FirstHubPort()YHubPort.FirstHubPort()YHubPort.FirstHubPort()

Starts the enumeration of Yocto-hub ports currently accessible.

Use the method YHubPort.nextHubPort() to iterate on next Yocto-hub ports.

Returns :

a pointer to a YHubPort object, corresponding to the first Yocto-hub port currently online, or a null pointer if there are none.

hubport→describe()hubport.describe()hubport.describe()hubport→describe()hubport→describe()[hubport describe]hubport.describe()hubport.describe()hubport.describe()hubport.describe()hubport.describe()

Returns a short text that describes unambiguously the instance of the Yocto-hub port in the form TYPE(NAME)=SERIAL.FUNCTIONID.

More precisely, TYPE is the type of the function, NAME it the name used for the first access to the function, SERIAL is the serial number of the module if the module is connected or "unresolved", and FUNCTIONID is the hardware identifier of the function if the module is connected. For example, this method returns Relay(MyCustomName.relay1)=RELAYLO1-123456.relay1 if the module is already connected or Relay(BadCustomeName.relay1)=unresolved if the module has not yet been connected. This method does not trigger any USB or TCP transaction and can therefore be used in a debugger.

Returns :

a string that describes the Yocto-hub port (ex: Relay(MyCustomName.relay1)=RELAYLO1-123456.relay1)

hubport→get_advertisedValue()
hubport→advertisedValue()hubport.get_advertisedValue()hubport.get_advertisedValue()hubport→get_advertisedValue()hubport→get_advertisedValue()[hubport advertisedValue]hubport.get_advertisedValue()hubport.get_advertisedValue()hubport.get_advertisedValue()hubport.get_advertisedValue()hubport.get_advertisedValue()YHubPort get_advertisedValue

Returns the current value of the Yocto-hub port (no more than 6 characters).

Returns :

a string corresponding to the current value of the Yocto-hub port (no more than 6 characters).

On failure, throws an exception or returns Y_ADVERTISEDVALUE_INVALID.

hubport→get_baudRate()
hubport→baudRate()hubport.get_baudRate()hubport.get_baudRate()hubport→get_baudRate()hubport→get_baudRate()[hubport baudRate]hubport.get_baudRate()hubport.get_baudRate()hubport.get_baudRate()hubport.get_baudRate()hubport.get_baudRate()YHubPort get_baudRate

Returns the current baud rate used by this Yocto-hub port, in kbps.

The default value is 1000 kbps, but a slower rate may be used if communication problems are encountered.

Returns :

an integer corresponding to the current baud rate used by this Yocto-hub port, in kbps

On failure, throws an exception or returns Y_BAUDRATE_INVALID.

hubport→get_enabled()
hubport→enabled()hubport.get_enabled()hubport.get_enabled()hubport→get_enabled()hubport→get_enabled()[hubport enabled]hubport.get_enabled()hubport.get_enabled()hubport.get_enabled()hubport.get_enabled()hubport.get_enabled()YHubPort get_enabled

Returns true if the Yocto-hub port is powered, false otherwise.

Returns :

either Y_ENABLED_FALSE or Y_ENABLED_TRUE, according to true if the Yocto-hub port is powered, false otherwise

On failure, throws an exception or returns Y_ENABLED_INVALID.

hubport→get_errorMessage()
hubport→errorMessage()hubport.get_errorMessage()hubport.get_errorMessage()hubport→get_errorMessage()hubport→get_errorMessage()[hubport errorMessage]hubport.get_errorMessage()hubport.get_errorMessage()hubport.get_errorMessage()hubport.get_errorMessage()hubport.get_errorMessage()

Returns the error message of the latest error with the Yocto-hub port.

This method is mostly useful when using the Yoctopuce library with exceptions disabled.

Returns :

a string corresponding to the latest error message that occured while using the Yocto-hub port object

hubport→get_errorType()
hubport→errorType()hubport.get_errorType()hubport.get_errorType()hubport→get_errorType()hubport→get_errorType()hubport.get_errorType()hubport.get_errorType()hubport.get_errorType()hubport.get_errorType()hubport.get_errorType()

Returns the numerical error code of the latest error with the Yocto-hub port.

This method is mostly useful when using the Yoctopuce library with exceptions disabled.

Returns :

a number corresponding to the code of the latest error that occured while using the Yocto-hub port object

hubport→get_friendlyName()
hubport→friendlyName()hubport.get_friendlyName()hubport.get_friendlyName()hubport→get_friendlyName()hubport→get_friendlyName()[hubport friendlyName]hubport.get_friendlyName()hubport.get_friendlyName()hubport.get_friendlyName()

Returns a global identifier of the Yocto-hub port in the format MODULE_NAME.FUNCTION_NAME.

The returned string uses the logical names of the module and of the Yocto-hub port if they are defined, otherwise the serial number of the module and the hardware identifier of the Yocto-hub port (for exemple: MyCustomName.relay1)

Returns :

a string that uniquely identifies the Yocto-hub port using logical names (ex: MyCustomName.relay1)

On failure, throws an exception or returns Y_FRIENDLYNAME_INVALID.

hubport→get_functionDescriptor()
hubport→functionDescriptor()hubport.get_functionDescriptor()hubport.get_functionDescriptor()hubport→get_functionDescriptor()hubport→get_functionDescriptor()[hubport functionDescriptor]hubport.get_functionDescriptor()hubport.get_functionDescriptor()hubport.get_functionDescriptor()hubport.get_functionDescriptor()hubport.get_functionDescriptor()

Returns a unique identifier of type YFUN_DESCR corresponding to the function.

This identifier can be used to test if two instances of YFunction reference the same physical function on the same physical device.

Returns :

an identifier of type YFUN_DESCR.

If the function has never been contacted, the returned value is Y_FUNCTIONDESCRIPTOR_INVALID.

hubport→get_functionId()
hubport→functionId()hubport.get_functionId()hubport.get_functionId()hubport→get_functionId()hubport→get_functionId()[hubport functionId]hubport.get_functionId()hubport.get_functionId()hubport.get_functionId()hubport.get_functionId()

Returns the hardware identifier of the Yocto-hub port, without reference to the module.

For example relay1

Returns :

a string that identifies the Yocto-hub port (ex: relay1)

On failure, throws an exception or returns Y_FUNCTIONID_INVALID.

hubport→get_hardwareId()
hubport→hardwareId()hubport.get_hardwareId()hubport.get_hardwareId()hubport→get_hardwareId()hubport→get_hardwareId()[hubport hardwareId]hubport.get_hardwareId()hubport.get_hardwareId()hubport.get_hardwareId()hubport.get_hardwareId()

Returns the unique hardware identifier of the Yocto-hub port in the form SERIAL.FUNCTIONID.

The unique hardware identifier is composed of the device serial number and of the hardware identifier of the Yocto-hub port (for example RELAYLO1-123456.relay1).

Returns :

a string that uniquely identifies the Yocto-hub port (ex: RELAYLO1-123456.relay1)

On failure, throws an exception or returns Y_HARDWAREID_INVALID.

hubport→get_logicalName()
hubport→logicalName()hubport.get_logicalName()hubport.get_logicalName()hubport→get_logicalName()hubport→get_logicalName()[hubport logicalName]hubport.get_logicalName()hubport.get_logicalName()hubport.get_logicalName()hubport.get_logicalName()hubport.get_logicalName()YHubPort get_logicalName

Returns the logical name of the Yocto-hub port.

Returns :

a string corresponding to the logical name of the Yocto-hub port.

On failure, throws an exception or returns Y_LOGICALNAME_INVALID.

hubport→get_module()
hubport→module()hubport.get_module()hubport.get_module()hubport→get_module()hubport→get_module()[hubport module]hubport.get_module()hubport.get_module()hubport.get_module()hubport.get_module()hubport.get_module()

Gets the YModule object for the device on which the function is located.

If the function cannot be located on any module, the returned instance of YModule is not shown as on-line.

Returns :

an instance of YModule

hubport→get_module_async()
hubport→module_async()hubport.get_module_async()hubport.get_module_async()

Gets the YModule object for the device on which the function is located (asynchronous version).

If the function cannot be located on any module, the returned YModule object does not show as on-line.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking Firefox javascript VM that does not implement context switching during blocking I/O calls. See the documentation section on asynchronous Javascript calls for more details.

Parameters :

Returns :

nothing : the result is provided to the callback.

hubport→get_portState()
hubport→portState()hubport.get_portState()hubport.get_portState()hubport→get_portState()hubport→get_portState()[hubport portState]hubport.get_portState()hubport.get_portState()hubport.get_portState()hubport.get_portState()hubport.get_portState()YHubPort get_portState

Returns the current state of the Yocto-hub port.

Returns :

a value among Y_PORTSTATE_OFF, Y_PORTSTATE_OVRLD, Y_PORTSTATE_ON, Y_PORTSTATE_RUN and Y_PORTSTATE_PROG corresponding to the current state of the Yocto-hub port

On failure, throws an exception or returns Y_PORTSTATE_INVALID.

hubport→get_userData()
hubport→userData()hubport.get_userData()hubport.get_userData()hubport→get_userData()hubport→get_userData()[hubport userData]hubport.get_userData()hubport.get_userData()hubport.get_userData()hubport.get_userData()hubport.get_userData()

Returns the value of the userData attribute, as previously stored using method set_userData.

This attribute is never touched directly by the API, and is at disposal of the caller to store a context.

Returns :

the object stored previously by the caller.

hubport→isOnline()hubport.isOnline()hubport.isOnline()hubport→isOnline()hubport→isOnline()[hubport isOnline]hubport.isOnline()hubport.isOnline()hubport.isOnline()hubport.isOnline()hubport.isOnline()

Checks if the Yocto-hub port is currently reachable, without raising any error.

If there is a cached value for the Yocto-hub port in cache, that has not yet expired, the device is considered reachable. No exception is raised if there is an error while trying to contact the device hosting the Yocto-hub port.

Returns :

true if the Yocto-hub port can be reached, and false otherwise

hubport→isOnline_async()hubport.isOnline_async()hubport.isOnline_async()

Checks if the Yocto-hub port is currently reachable, without raising any error (asynchronous version).

If there is a cached value for the Yocto-hub port in cache, that has not yet expired, the device is considered reachable. No exception is raised if there is an error while trying to contact the device hosting the requested function.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking the Javascript virtual machine.

Parameters :

Returns :

nothing : the result is provided to the callback.

hubport→load()hubport.load()hubport.load()hubport→load()hubport→load()[hubport load: ]hubport.load()hubport.load()hubport.load()hubport.load()hubport.load()

Preloads the Yocto-hub port cache with a specified validity duration.

By default, whenever accessing a device, all function attributes are kept in cache for the standard duration (5 ms). This method can be used to temporarily mark the cache as valid for a longer period, in order to reduce network trafic for instance.

Parameters :

Returns :

YAPI_SUCCESS when the call succeeds.

On failure, throws an exception or returns a negative error code.

hubport→load_async()hubport.load_async()hubport.load_async()

Preloads the Yocto-hub port cache with a specified validity duration (asynchronous version).

By default, whenever accessing a device, all function attributes are kept in cache for the standard duration (5 ms). This method can be used to temporarily mark the cache as valid for a longer period, in order to reduce network trafic for instance.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking the Javascript virtual machine.

Parameters :

Returns :

nothing : the result is provided to the callback.

hubport→nextHubPort()hubport.nextHubPort()hubport.nextHubPort()hubport→nextHubPort()hubport→nextHubPort()[hubport nextHubPort]hubport.nextHubPort()hubport.nextHubPort()hubport.nextHubPort()hubport.nextHubPort()hubport.nextHubPort()

Continues the enumeration of Yocto-hub ports started using yFirstHubPort().

Returns :

a pointer to a YHubPort object, corresponding to a Yocto-hub port currently online, or a null pointer if there are no more Yocto-hub ports to enumerate.

hubport→registerValueCallback()hubport.registerValueCallback()hubport.registerValueCallback()hubport→registerValueCallback()hubport→registerValueCallback()[hubport registerValueCallback: ]hubport.registerValueCallback()hubport.registerValueCallback()hubport.registerValueCallback()hubport.registerValueCallback()hubport.registerValueCallback()

Registers the callback function that is invoked on every change of advertised value.

The callback is invoked only during the execution of ySleep or yHandleEvents. This provides control over the time when the callback is triggered. For good responsiveness, remember to call one of these two functions periodically. To unregister a callback, pass a null pointer as argument.

Parameters :

hubport→set_enabled()
hubport→setEnabled()hubport.set_enabled()hubport.set_enabled()hubport→set_enabled()hubport→set_enabled()[hubport setEnabled: ]hubport.set_enabled()hubport.set_enabled()hubport.set_enabled()hubport.set_enabled()hubport.set_enabled()YHubPort set_enabled

Changes the activation of the Yocto-hub port.

If the port is enabled, the connected module is powered. Otherwise, port power is shut down.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

hubport→set_logicalName()
hubport→setLogicalName()hubport.set_logicalName()hubport.set_logicalName()hubport→set_logicalName()hubport→set_logicalName()[hubport setLogicalName: ]hubport.set_logicalName()hubport.set_logicalName()hubport.set_logicalName()hubport.set_logicalName()hubport.set_logicalName()YHubPort set_logicalName

Changes the logical name of the Yocto-hub port.

You can use yCheckLogicalName() prior to this call to make sure that your parameter is valid. Remember to call the saveToFlash() method of the module if the modification must be kept.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

hubport→set_userData()
hubport→setUserData()hubport.set_userData()hubport.set_userData()hubport→set_userData()hubport→set_userData()[hubport setUserData: ]hubport.set_userData()hubport.set_userData()hubport.set_userData()hubport.set_userData()hubport.set_userData()

Stores a user context provided as argument in the userData attribute of the function.

This attribute is never touched by the API, and is at disposal of the caller to store a context.

Parameters :

hubport→wait_async()hubport.wait_async()hubport.wait_async()

Waits for all pending asynchronous commands on the module to complete, and invoke the user-provided callback function.

The callback function can therefore freely issue synchronous or asynchronous commands, without risking to block the Javascript VM.

Parameters :

Returns :

nothing.

11.2. Wireless function interface

YWireless functions provides control over wireless network parameters and status for devices that are wireless-enabled.

Global functions
yFindWireless(func)
Retrieves a wireless lan interface for a given identifier.
yFirstWireless()
Starts the enumeration of wireless lan interfaces currently accessible.
YWireless methods
wireless→adhocNetwork(ssid, securityKey)
Changes the configuration of the wireless lan interface to create an ad-hoc wireless network, without using an access point.
wireless→describe()
Returns a short text that describes unambiguously the instance of the wireless lan interface in the form TYPE(NAME)=SERIAL.FUNCTIONID.
wireless→get_advertisedValue()
Returns the current value of the wireless lan interface (no more than 6 characters).
wireless→get_channel()
Returns the 802.11 channel currently used, or 0 when the selected network has not been found.
wireless→get_detectedWlans()
Returns a list of YWlanRecord objects that describe detected Wireless networks.
wireless→get_errorMessage()
Returns the error message of the latest error with the wireless lan interface.
wireless→get_errorType()
Returns the numerical error code of the latest error with the wireless lan interface.
wireless→get_friendlyName()
Returns a global identifier of the wireless lan interface in the format MODULE_NAME.FUNCTION_NAME.
wireless→get_functionDescriptor()
Returns a unique identifier of type YFUN_DESCR corresponding to the function.
wireless→get_functionId()
Returns the hardware identifier of the wireless lan interface, without reference to the module.
wireless→get_hardwareId()
Returns the unique hardware identifier of the wireless lan interface in the form SERIAL.FUNCTIONID.
wireless→get_linkQuality()
Returns the link quality, expressed in percent.
wireless→get_logicalName()
Returns the logical name of the wireless lan interface.
wireless→get_message()
Returns the latest status message from the wireless interface.
wireless→get_module()
Gets the YModule object for the device on which the function is located.
wireless→get_module_async(callback, context)
Gets the YModule object for the device on which the function is located (asynchronous version).
wireless→get_security()
Returns the security algorithm used by the selected wireless network.
wireless→get_ssid()
Returns the wireless network name (SSID).
wireless→get_userData()
Returns the value of the userData attribute, as previously stored using method set_userData.
wireless→isOnline()
Checks if the wireless lan interface is currently reachable, without raising any error.
wireless→isOnline_async(callback, context)
Checks if the wireless lan interface is currently reachable, without raising any error (asynchronous version).
wireless→joinNetwork(ssid, securityKey)
Changes the configuration of the wireless lan interface to connect to an existing access point (infrastructure mode).
wireless→load(msValidity)
Preloads the wireless lan interface cache with a specified validity duration.
wireless→load_async(msValidity, callback, context)
Preloads the wireless lan interface cache with a specified validity duration (asynchronous version).
wireless→nextWireless()
Continues the enumeration of wireless lan interfaces started using yFirstWireless().
wireless→registerValueCallback(callback)
Registers the callback function that is invoked on every change of advertised value.
wireless→set_logicalName(newval)
Changes the logical name of the wireless lan interface.
wireless→set_userData(data)
Stores a user context provided as argument in the userData attribute of the function.
wireless→wait_async(callback, context)
Waits for all pending asynchronous commands on the module to complete, and invoke the user-provided callback function.

YWireless.FindWireless()
yFindWireless()yFindWireless()YWireless.FindWireless()yFindWireless()yFindWireless()[YWireless FindWireless: ]yFindWireless()yFindWireless()YWireless.FindWireless()YWireless.FindWireless()YWireless.FindWireless()

Retrieves a wireless lan interface for a given identifier.

The identifier can be specified using several formats:

• FunctionLogicalName
• ModuleSerialNumber.FunctionIdentifier
• ModuleSerialNumber.FunctionLogicalName
• ModuleLogicalName.FunctionIdentifier
• ModuleLogicalName.FunctionLogicalName

This function does not require that the wireless lan interface is online at the time it is invoked. The returned object is nevertheless valid. Use the method YWireless.isOnline() to test if the wireless lan interface is indeed online at a given time. In case of ambiguity when looking for a wireless lan interface by logical name, no error is notified: the first instance found is returned. The search is performed first by hardware name, then by logical name.

Parameters :

Returns :

a YWireless object allowing you to drive the wireless lan interface.

YWireless.FirstWireless()
yFirstWireless()yFirstWireless()YWireless.FirstWireless()yFirstWireless()yFirstWireless()[YWireless FirstWireless]yFirstWireless()yFirstWireless()YWireless.FirstWireless()YWireless.FirstWireless()YWireless.FirstWireless()

Starts the enumeration of wireless lan interfaces currently accessible.

Use the method YWireless.nextWireless() to iterate on next wireless lan interfaces.

Returns :

a pointer to a YWireless object, corresponding to the first wireless lan interface currently online, or a null pointer if there are none.

wireless→adhocNetwork()wireless.adhocNetwork()wireless.adhocNetwork()wireless→adhocNetwork()wireless→adhocNetwork()[wireless adhocNetwork: ]wireless.adhocNetwork()wireless.adhocNetwork()wireless.adhocNetwork()wireless.adhocNetwork()wireless.adhocNetwork()YWireless adhocNetwork

Changes the configuration of the wireless lan interface to create an ad-hoc wireless network, without using an access point.

If a security key is specified, the network is protected by WEP128, since WPA is not standardized for ad-hoc networks. Remember to call the saveToFlash() method and then to reboot the module to apply this setting.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wireless→describe()wireless.describe()wireless.describe()wireless→describe()wireless→describe()[wireless describe]wireless.describe()wireless.describe()wireless.describe()wireless.describe()wireless.describe()

Returns a short text that describes unambiguously the instance of the wireless lan interface in the form TYPE(NAME)=SERIAL.FUNCTIONID.

More precisely, TYPE is the type of the function, NAME it the name used for the first access to the function, SERIAL is the serial number of the module if the module is connected or "unresolved", and FUNCTIONID is the hardware identifier of the function if the module is connected. For example, this method returns Relay(MyCustomName.relay1)=RELAYLO1-123456.relay1 if the module is already connected or Relay(BadCustomeName.relay1)=unresolved if the module has not yet been connected. This method does not trigger any USB or TCP transaction and can therefore be used in a debugger.

Returns :

a string that describes the wireless lan interface (ex: Relay(MyCustomName.relay1)=RELAYLO1-123456.relay1)

wireless→get_advertisedValue()
wireless→advertisedValue()wireless.get_advertisedValue()wireless.get_advertisedValue()wireless→get_advertisedValue()wireless→get_advertisedValue()[wireless advertisedValue]wireless.get_advertisedValue()wireless.get_advertisedValue()wireless.get_advertisedValue()wireless.get_advertisedValue()wireless.get_advertisedValue()YWireless get_advertisedValue

Returns the current value of the wireless lan interface (no more than 6 characters).

Returns :

a string corresponding to the current value of the wireless lan interface (no more than 6 characters).

On failure, throws an exception or returns Y_ADVERTISEDVALUE_INVALID.

wireless→get_channel()
wireless→channel()wireless.get_channel()wireless.get_channel()wireless→get_channel()wireless→get_channel()[wireless channel]wireless.get_channel()wireless.get_channel()wireless.get_channel()wireless.get_channel()wireless.get_channel()YWireless get_channel

Returns the 802.11 channel currently used, or 0 when the selected network has not been found.

Returns :

an integer corresponding to the 802.11 channel currently used, or 0 when the selected network has not been found

On failure, throws an exception or returns Y_CHANNEL_INVALID.

wireless→get_detectedWlans()
wireless→detectedWlans()wireless.get_detectedWlans()wireless.get_detectedWlans()wireless→get_detectedWlans()wireless→get_detectedWlans()[wireless detectedWlans]wireless.get_detectedWlans()wireless.get_detectedWlans()wireless.get_detectedWlans()wireless.get_detectedWlans()wireless.get_detectedWlans()YWireless get_detectedWlans

Returns a list of YWlanRecord objects that describe detected Wireless networks.

This list is not updated when the module is already connected to an acces point (infrastructure mode). To force an update of this list, adhocNetwork() must be called to disconnect the module from the current network. The returned list must be unallocated by the caller.

Returns :

a list of YWlanRecord objects, containing the SSID, channel, link quality and the type of security of the wireless network.

On failure, throws an exception or returns an empty list.

wireless→get_errorMessage()
wireless→errorMessage()wireless.get_errorMessage()wireless.get_errorMessage()wireless→get_errorMessage()wireless→get_errorMessage()[wireless errorMessage]wireless.get_errorMessage()wireless.get_errorMessage()wireless.get_errorMessage()wireless.get_errorMessage()wireless.get_errorMessage()

Returns the error message of the latest error with the wireless lan interface.

This method is mostly useful when using the Yoctopuce library with exceptions disabled.

Returns :

a string corresponding to the latest error message that occured while using the wireless lan interface object

wireless→get_errorType()
wireless→errorType()wireless.get_errorType()wireless.get_errorType()wireless→get_errorType()wireless→get_errorType()wireless.get_errorType()wireless.get_errorType()wireless.get_errorType()wireless.get_errorType()wireless.get_errorType()

Returns the numerical error code of the latest error with the wireless lan interface.

This method is mostly useful when using the Yoctopuce library with exceptions disabled.

Returns :

a number corresponding to the code of the latest error that occured while using the wireless lan interface object

wireless→get_friendlyName()
wireless→friendlyName()wireless.get_friendlyName()wireless.get_friendlyName()wireless→get_friendlyName()wireless→get_friendlyName()[wireless friendlyName]wireless.get_friendlyName()wireless.get_friendlyName()wireless.get_friendlyName()

Returns a global identifier of the wireless lan interface in the format MODULE_NAME.FUNCTION_NAME.

The returned string uses the logical names of the module and of the wireless lan interface if they are defined, otherwise the serial number of the module and the hardware identifier of the wireless lan interface (for exemple: MyCustomName.relay1)

Returns :

a string that uniquely identifies the wireless lan interface using logical names (ex: MyCustomName.relay1)

On failure, throws an exception or returns Y_FRIENDLYNAME_INVALID.

wireless→get_functionDescriptor()
wireless→functionDescriptor()wireless.get_functionDescriptor()wireless.get_functionDescriptor()wireless→get_functionDescriptor()wireless→get_functionDescriptor()[wireless functionDescriptor]wireless.get_functionDescriptor()wireless.get_functionDescriptor()wireless.get_functionDescriptor()wireless.get_functionDescriptor()wireless.get_functionDescriptor()

Returns a unique identifier of type YFUN_DESCR corresponding to the function.

This identifier can be used to test if two instances of YFunction reference the same physical function on the same physical device.

Returns :

an identifier of type YFUN_DESCR.

If the function has never been contacted, the returned value is Y_FUNCTIONDESCRIPTOR_INVALID.

wireless→get_functionId()
wireless→functionId()wireless.get_functionId()wireless.get_functionId()wireless→get_functionId()wireless→get_functionId()[wireless functionId]wireless.get_functionId()wireless.get_functionId()wireless.get_functionId()wireless.get_functionId()

Returns the hardware identifier of the wireless lan interface, without reference to the module.

For example relay1

Returns :

a string that identifies the wireless lan interface (ex: relay1)

On failure, throws an exception or returns Y_FUNCTIONID_INVALID.

wireless→get_hardwareId()
wireless→hardwareId()wireless.get_hardwareId()wireless.get_hardwareId()wireless→get_hardwareId()wireless→get_hardwareId()[wireless hardwareId]wireless.get_hardwareId()wireless.get_hardwareId()wireless.get_hardwareId()wireless.get_hardwareId()

Returns the unique hardware identifier of the wireless lan interface in the form SERIAL.FUNCTIONID.

The unique hardware identifier is composed of the device serial number and of the hardware identifier of the wireless lan interface (for example RELAYLO1-123456.relay1).

Returns :

a string that uniquely identifies the wireless lan interface (ex: RELAYLO1-123456.relay1)

On failure, throws an exception or returns Y_HARDWAREID_INVALID.

wireless→get_linkQuality()
wireless→linkQuality()wireless.get_linkQuality()wireless.get_linkQuality()wireless→get_linkQuality()wireless→get_linkQuality()[wireless linkQuality]wireless.get_linkQuality()wireless.get_linkQuality()wireless.get_linkQuality()wireless.get_linkQuality()wireless.get_linkQuality()YWireless get_linkQuality

Returns the link quality, expressed in percent.

Returns :

an integer corresponding to the link quality, expressed in percent

On failure, throws an exception or returns Y_LINKQUALITY_INVALID.

wireless→get_logicalName()
wireless→logicalName()wireless.get_logicalName()wireless.get_logicalName()wireless→get_logicalName()wireless→get_logicalName()[wireless logicalName]wireless.get_logicalName()wireless.get_logicalName()wireless.get_logicalName()wireless.get_logicalName()wireless.get_logicalName()YWireless get_logicalName

Returns the logical name of the wireless lan interface.

Returns :

a string corresponding to the logical name of the wireless lan interface.

On failure, throws an exception or returns Y_LOGICALNAME_INVALID.

wireless→get_message()
wireless→message()wireless.get_message()wireless.get_message()wireless→get_message()wireless→get_message()[wireless message]wireless.get_message()wireless.get_message()wireless.get_message()wireless.get_message()wireless.get_message()YWireless get_message

Returns the latest status message from the wireless interface.

Returns :

a string corresponding to the latest status message from the wireless interface

On failure, throws an exception or returns Y_MESSAGE_INVALID.

wireless→get_module()
wireless→module()wireless.get_module()wireless.get_module()wireless→get_module()wireless→get_module()[wireless module]wireless.get_module()wireless.get_module()wireless.get_module()wireless.get_module()wireless.get_module()

Gets the YModule object for the device on which the function is located.

If the function cannot be located on any module, the returned instance of YModule is not shown as on-line.

Returns :

an instance of YModule

wireless→get_module_async()
wireless→module_async()wireless.get_module_async()wireless.get_module_async()

Gets the YModule object for the device on which the function is located (asynchronous version).

If the function cannot be located on any module, the returned YModule object does not show as on-line.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking Firefox javascript VM that does not implement context switching during blocking I/O calls. See the documentation section on asynchronous Javascript calls for more details.

Parameters :

Returns :

nothing : the result is provided to the callback.

wireless→get_security()
wireless→security()wireless.get_security()wireless.get_security()wireless→get_security()wireless→get_security()[wireless security]wireless.get_security()wireless.get_security()wireless.get_security()wireless.get_security()wireless.get_security()YWireless get_security

Returns the security algorithm used by the selected wireless network.

Returns :

a value among Y_SECURITY_UNKNOWN, Y_SECURITY_OPEN, Y_SECURITY_WEP, Y_SECURITY_WPA and Y_SECURITY_WPA2 corresponding to the security algorithm used by the selected wireless network

On failure, throws an exception or returns Y_SECURITY_INVALID.

wireless→get_ssid()
wireless→ssid()wireless.get_ssid()wireless.get_ssid()wireless→get_ssid()wireless→get_ssid()[wireless ssid]wireless.get_ssid()wireless.get_ssid()wireless.get_ssid()wireless.get_ssid()wireless.get_ssid()YWireless get_ssid

Returns the wireless network name (SSID).

Returns :

a string corresponding to the wireless network name (SSID)

On failure, throws an exception or returns Y_SSID_INVALID.

wireless→get_userData()
wireless→userData()wireless.get_userData()wireless.get_userData()wireless→get_userData()wireless→get_userData()[wireless userData]wireless.get_userData()wireless.get_userData()wireless.get_userData()wireless.get_userData()wireless.get_userData()

Returns the value of the userData attribute, as previously stored using method set_userData.

This attribute is never touched directly by the API, and is at disposal of the caller to store a context.

Returns :

the object stored previously by the caller.

wireless→isOnline()wireless.isOnline()wireless.isOnline()wireless→isOnline()wireless→isOnline()[wireless isOnline]wireless.isOnline()wireless.isOnline()wireless.isOnline()wireless.isOnline()wireless.isOnline()

Checks if the wireless lan interface is currently reachable, without raising any error.

If there is a cached value for the wireless lan interface in cache, that has not yet expired, the device is considered reachable. No exception is raised if there is an error while trying to contact the device hosting the wireless lan interface.

Returns :

true if the wireless lan interface can be reached, and false otherwise

wireless→isOnline_async()wireless.isOnline_async()wireless.isOnline_async()

Checks if the wireless lan interface is currently reachable, without raising any error (asynchronous version).

If there is a cached value for the wireless lan interface in cache, that has not yet expired, the device is considered reachable. No exception is raised if there is an error while trying to contact the device hosting the requested function.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking the Javascript virtual machine.

Parameters :

Returns :

nothing : the result is provided to the callback.

wireless→joinNetwork()wireless.joinNetwork()wireless.joinNetwork()wireless→joinNetwork()wireless→joinNetwork()[wireless joinNetwork: ]wireless.joinNetwork()wireless.joinNetwork()wireless.joinNetwork()wireless.joinNetwork()wireless.joinNetwork()YWireless joinNetwork

Changes the configuration of the wireless lan interface to connect to an existing access point (infrastructure mode).

Remember to call the saveToFlash() method and then to reboot the module to apply this setting.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wireless→load()wireless.load()wireless.load()wireless→load()wireless→load()[wireless load: ]wireless.load()wireless.load()wireless.load()wireless.load()wireless.load()

Preloads the wireless lan interface cache with a specified validity duration.

By default, whenever accessing a device, all function attributes are kept in cache for the standard duration (5 ms). This method can be used to temporarily mark the cache as valid for a longer period, in order to reduce network trafic for instance.

Parameters :

Returns :

YAPI_SUCCESS when the call succeeds.

On failure, throws an exception or returns a negative error code.

wireless→load_async()wireless.load_async()wireless.load_async()

Preloads the wireless lan interface cache with a specified validity duration (asynchronous version).

By default, whenever accessing a device, all function attributes are kept in cache for the standard duration (5 ms). This method can be used to temporarily mark the cache as valid for a longer period, in order to reduce network trafic for instance.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking the Javascript virtual machine.

Parameters :

Returns :

nothing : the result is provided to the callback.

wireless→nextWireless()wireless.nextWireless()wireless.nextWireless()wireless→nextWireless()wireless→nextWireless()[wireless nextWireless]wireless.nextWireless()wireless.nextWireless()wireless.nextWireless()wireless.nextWireless()wireless.nextWireless()

Continues the enumeration of wireless lan interfaces started using yFirstWireless().

Returns :

a pointer to a YWireless object, corresponding to a wireless lan interface currently online, or a null pointer if there are no more wireless lan interfaces to enumerate.

wireless→registerValueCallback()wireless.registerValueCallback()wireless.registerValueCallback()wireless→registerValueCallback()wireless→registerValueCallback()[wireless registerValueCallback: ]wireless.registerValueCallback()wireless.registerValueCallback()wireless.registerValueCallback()wireless.registerValueCallback()wireless.registerValueCallback()

Registers the callback function that is invoked on every change of advertised value.

The callback is invoked only during the execution of ySleep or yHandleEvents. This provides control over the time when the callback is triggered. For good responsiveness, remember to call one of these two functions periodically. To unregister a callback, pass a null pointer as argument.

Parameters :

wireless→set_logicalName()
wireless→setLogicalName()wireless.set_logicalName()wireless.set_logicalName()wireless→set_logicalName()wireless→set_logicalName()[wireless setLogicalName: ]wireless.set_logicalName()wireless.set_logicalName()wireless.set_logicalName()wireless.set_logicalName()wireless.set_logicalName()YWireless set_logicalName

Changes the logical name of the wireless lan interface.

You can use yCheckLogicalName() prior to this call to make sure that your parameter is valid. Remember to call the saveToFlash() method of the module if the modification must be kept.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wireless→set_userData()
wireless→setUserData()wireless.set_userData()wireless.set_userData()wireless→set_userData()wireless→set_userData()[wireless setUserData: ]wireless.set_userData()wireless.set_userData()wireless.set_userData()wireless.set_userData()wireless.set_userData()

Stores a user context provided as argument in the userData attribute of the function.

This attribute is never touched by the API, and is at disposal of the caller to store a context.

Parameters :

wireless→wait_async()wireless.wait_async()wireless.wait_async()

Waits for all pending asynchronous commands on the module to complete, and invoke the user-provided callback function.

The callback function can therefore freely issue synchronous or asynchronous commands, without risking to block the Javascript VM.

Parameters :

Returns :

nothing.

11.3. Network function interface

YNetwork objects provide access to TCP/IP parameters of Yoctopuce modules that include a built-in network interface.

Global functions
yFindNetwork(func)
Retrieves a network interface for a given identifier.
yFirstNetwork()
Starts the enumeration of network interfaces currently accessible.
YNetwork methods
network→callbackLogin(username, password)
Connects to the notification callback and saves the credentials required to log into it.
network→describe()
Returns a short text that describes unambiguously the instance of the network interface in the form TYPE(NAME)=SERIAL.FUNCTIONID.
network→get_adminPassword()
Returns a hash string if a password has been set for user "admin", or an empty string otherwise.
network→get_advertisedValue()
Returns the current value of the network interface (no more than 6 characters).
network→get_callbackCredentials()
Returns a hashed version of the notification callback credentials if set, or an empty string otherwise.
network→get_callbackEncoding()
Returns the encoding standard to use for representing notification values.
network→get_callbackMaxDelay()
Returns the maximum waiting time between two callback notifications, in seconds.
network→get_callbackMethod()
Returns the HTTP method used to notify callbacks for significant state changes.
network→get_callbackMinDelay()
Returns the minimum waiting time between two callback notifications, in seconds.
network→get_callbackUrl()
Returns the callback URL to notify of significant state changes.
network→get_discoverable()
Returns the activation state of the multicast announce protocols to allow easy discovery of the module in the network neighborhood (uPnP/Bonjour protocol).
network→get_errorMessage()
Returns the error message of the latest error with the network interface.
network→get_errorType()
Returns the numerical error code of the latest error with the network interface.
network→get_friendlyName()
Returns a global identifier of the network interface in the format MODULE_NAME.FUNCTION_NAME.
network→get_functionDescriptor()
Returns a unique identifier of type YFUN_DESCR corresponding to the function.
network→get_functionId()
Returns the hardware identifier of the network interface, without reference to the module.
network→get_hardwareId()
Returns the unique hardware identifier of the network interface in the form SERIAL.FUNCTIONID.
network→get_ipAddress()
Returns the IP address currently in use by the device.
network→get_logicalName()
Returns the logical name of the network interface.
network→get_macAddress()
Returns the MAC address of the network interface.
network→get_module()
Gets the YModule object for the device on which the function is located.
network→get_module_async(callback, context)
Gets the YModule object for the device on which the function is located (asynchronous version).
network→get_poeCurrent()
Returns the current consumed by the module from Power-over-Ethernet (PoE), in milli-amps.
network→get_primaryDNS()
Returns the IP address of the primary name server to be used by the module.
network→get_readiness()
Returns the current established working mode of the network interface.
network→get_router()
Returns the IP address of the router on the device subnet (default gateway).
network→get_secondaryDNS()
Returns the IP address of the secondary name server to be used by the module.
network→get_subnetMask()
Returns the subnet mask currently used by the device.
network→get_userData()
Returns the value of the userData attribute, as previously stored using method set_userData.
network→get_userPassword()
Returns a hash string if a password has been set for "user" user, or an empty string otherwise.
network→get_wwwWatchdogDelay()
Returns the allowed downtime of the WWW link (in seconds) before triggering an automated reboot to try to recover Internet connectivity.
network→isOnline()
Checks if the network interface is currently reachable, without raising any error.
network→isOnline_async(callback, context)
Checks if the network interface is currently reachable, without raising any error (asynchronous version).
network→load(msValidity)
Preloads the network interface cache with a specified validity duration.
network→load_async(msValidity, callback, context)
Preloads the network interface cache with a specified validity duration (asynchronous version).
network→nextNetwork()
Continues the enumeration of network interfaces started using yFirstNetwork().
network→ping(host)
Pings str_host to test the network connectivity.
network→registerValueCallback(callback)
Registers the callback function that is invoked on every change of advertised value.
network→set_adminPassword(newval)
Changes the password for the "admin" user.
network→set_callbackCredentials(newval)
Changes the credentials required to connect to the callback address.
network→set_callbackEncoding(newval)
Changes the encoding standard to use for representing notification values.
network→set_callbackMaxDelay(newval)
Changes the maximum waiting time between two callback notifications, in seconds.
network→set_callbackMethod(newval)
Changes the HTTP method used to notify callbacks for significant state changes.
network→set_callbackMinDelay(newval)
Changes the minimum waiting time between two callback notifications, in seconds.
network→set_callbackUrl(newval)
Changes the callback URL to notify significant state changes.
network→set_discoverable(newval)
Changes the activation state of the multicast announce protocols to allow easy discovery of the module in the network neighborhood (uPnP/Bonjour protocol).
network→set_logicalName(newval)
Changes the logical name of the network interface.
network→set_primaryDNS(newval)
Changes the IP address of the primary name server to be used by the module.
network→set_secondaryDNS(newval)
Changes the IP address of the secondary name server to be used by the module.
network→set_userData(data)
Stores a user context provided as argument in the userData attribute of the function.
network→set_userPassword(newval)
Changes the password for the "user" user.
network→set_wwwWatchdogDelay(newval)
Changes the allowed downtime of the WWW link (in seconds) before triggering an automated reboot to try to recover Internet connectivity.
network→useDHCP(fallbackIpAddr, fallbackSubnetMaskLen, fallbackRouter)
Changes the configuration of the network interface to enable the use of an IP address received from a DHCP server.
network→useStaticIP(ipAddress, subnetMaskLen, router)
Changes the configuration of the network interface to use a static IP address.
network→wait_async(callback, context)
Waits for all pending asynchronous commands on the module to complete, and invoke the user-provided callback function.

YNetwork.FindNetwork()
yFindNetwork()yFindNetwork()YNetwork.FindNetwork()yFindNetwork()yFindNetwork()[YNetwork FindNetwork: ]yFindNetwork()yFindNetwork()YNetwork.FindNetwork()YNetwork.FindNetwork()YNetwork.FindNetwork()

Retrieves a network interface for a given identifier.

The identifier can be specified using several formats:

• FunctionLogicalName
• ModuleSerialNumber.FunctionIdentifier
• ModuleSerialNumber.FunctionLogicalName
• ModuleLogicalName.FunctionIdentifier
• ModuleLogicalName.FunctionLogicalName

This function does not require that the network interface is online at the time it is invoked. The returned object is nevertheless valid. Use the method YNetwork.isOnline() to test if the network interface is indeed online at a given time. In case of ambiguity when looking for a network interface by logical name, no error is notified: the first instance found is returned. The search is performed first by hardware name, then by logical name.

Parameters :

Returns :

a YNetwork object allowing you to drive the network interface.

YNetwork.FirstNetwork()
yFirstNetwork()yFirstNetwork()YNetwork.FirstNetwork()yFirstNetwork()yFirstNetwork()[YNetwork FirstNetwork]yFirstNetwork()yFirstNetwork()YNetwork.FirstNetwork()YNetwork.FirstNetwork()YNetwork.FirstNetwork()

Starts the enumeration of network interfaces currently accessible.

Use the method YNetwork.nextNetwork() to iterate on next network interfaces.

Returns :

a pointer to a YNetwork object, corresponding to the first network interface currently online, or a null pointer if there are none.

network→callbackLogin()network.callbackLogin()network.callbackLogin()network→callbackLogin()network→callbackLogin()[network callbackLogin: ]network.callbackLogin()network.callbackLogin()network.callbackLogin()network.callbackLogin()network.callbackLogin()YNetwork callbackLogin

Connects to the notification callback and saves the credentials required to log into it.

The password is not stored into the module, only a hashed copy of the credentials are saved. Remember to call the saveToFlash() method of the module if the modification must be kept.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→describe()network.describe()network.describe()network→describe()network→describe()[network describe]network.describe()network.describe()network.describe()network.describe()network.describe()

Returns a short text that describes unambiguously the instance of the network interface in the form TYPE(NAME)=SERIAL.FUNCTIONID.

More precisely, TYPE is the type of the function, NAME it the name used for the first access to the function, SERIAL is the serial number of the module if the module is connected or "unresolved", and FUNCTIONID is the hardware identifier of the function if the module is connected. For example, this method returns Relay(MyCustomName.relay1)=RELAYLO1-123456.relay1 if the module is already connected or Relay(BadCustomeName.relay1)=unresolved if the module has not yet been connected. This method does not trigger any USB or TCP transaction and can therefore be used in a debugger.

Returns :

a string that describes the network interface (ex: Relay(MyCustomName.relay1)=RELAYLO1-123456.relay1)

network→get_adminPassword()
network→adminPassword()network.get_adminPassword()network.get_adminPassword()network→get_adminPassword()network→get_adminPassword()[network adminPassword]network.get_adminPassword()network.get_adminPassword()network.get_adminPassword()network.get_adminPassword()network.get_adminPassword()YNetwork get_adminPassword

Returns a hash string if a password has been set for user "admin", or an empty string otherwise.

Returns :

a string corresponding to a hash string if a password has been set for user "admin", or an empty string otherwise

On failure, throws an exception or returns Y_ADMINPASSWORD_INVALID.

network→get_advertisedValue()
network→advertisedValue()network.get_advertisedValue()network.get_advertisedValue()network→get_advertisedValue()network→get_advertisedValue()[network advertisedValue]network.get_advertisedValue()network.get_advertisedValue()network.get_advertisedValue()network.get_advertisedValue()network.get_advertisedValue()YNetwork get_advertisedValue

Returns the current value of the network interface (no more than 6 characters).

Returns :

a string corresponding to the current value of the network interface (no more than 6 characters).

On failure, throws an exception or returns Y_ADVERTISEDVALUE_INVALID.

network→get_callbackCredentials()
network→callbackCredentials()network.get_callbackCredentials()network.get_callbackCredentials()network→get_callbackCredentials()network→get_callbackCredentials()[network callbackCredentials]network.get_callbackCredentials()network.get_callbackCredentials()network.get_callbackCredentials()network.get_callbackCredentials()network.get_callbackCredentials()YNetwork get_callbackCredentials

Returns a hashed version of the notification callback credentials if set, or an empty string otherwise.

Returns :

a string corresponding to a hashed version of the notification callback credentials if set, or an empty string otherwise

On failure, throws an exception or returns Y_CALLBACKCREDENTIALS_INVALID.

network→get_callbackEncoding()
network→callbackEncoding()network.get_callbackEncoding()network.get_callbackEncoding()network→get_callbackEncoding()network→get_callbackEncoding()[network callbackEncoding]network.get_callbackEncoding()network.get_callbackEncoding()network.get_callbackEncoding()network.get_callbackEncoding()network.get_callbackEncoding()YNetwork get_callbackEncoding

Returns the encoding standard to use for representing notification values.

Returns :

a value among Y_CALLBACKENCODING_FORM, Y_CALLBACKENCODING_JSON, Y_CALLBACKENCODING_JSON_ARRAY, Y_CALLBACKENCODING_CSV and Y_CALLBACKENCODING_YOCTO_API corresponding to the encoding standard to use for representing notification values

On failure, throws an exception or returns Y_CALLBACKENCODING_INVALID.

network→get_callbackMaxDelay()
network→callbackMaxDelay()network.get_callbackMaxDelay()network.get_callbackMaxDelay()network→get_callbackMaxDelay()network→get_callbackMaxDelay()[network callbackMaxDelay]network.get_callbackMaxDelay()network.get_callbackMaxDelay()network.get_callbackMaxDelay()network.get_callbackMaxDelay()network.get_callbackMaxDelay()YNetwork get_callbackMaxDelay

Returns the maximum waiting time between two callback notifications, in seconds.

Returns :

an integer corresponding to the maximum waiting time between two callback notifications, in seconds

On failure, throws an exception or returns Y_CALLBACKMAXDELAY_INVALID.

network→get_callbackMethod()
network→callbackMethod()network.get_callbackMethod()network.get_callbackMethod()network→get_callbackMethod()network→get_callbackMethod()[network callbackMethod]network.get_callbackMethod()network.get_callbackMethod()network.get_callbackMethod()network.get_callbackMethod()network.get_callbackMethod()YNetwork get_callbackMethod

Returns the HTTP method used to notify callbacks for significant state changes.

Returns :

a value among Y_CALLBACKMETHOD_POST, Y_CALLBACKMETHOD_GET and Y_CALLBACKMETHOD_PUT corresponding to the HTTP method used to notify callbacks for significant state changes

On failure, throws an exception or returns Y_CALLBACKMETHOD_INVALID.

network→get_callbackMinDelay()
network→callbackMinDelay()network.get_callbackMinDelay()network.get_callbackMinDelay()network→get_callbackMinDelay()network→get_callbackMinDelay()[network callbackMinDelay]network.get_callbackMinDelay()network.get_callbackMinDelay()network.get_callbackMinDelay()network.get_callbackMinDelay()network.get_callbackMinDelay()YNetwork get_callbackMinDelay

Returns the minimum waiting time between two callback notifications, in seconds.

Returns :

an integer corresponding to the minimum waiting time between two callback notifications, in seconds

On failure, throws an exception or returns Y_CALLBACKMINDELAY_INVALID.

network→get_callbackUrl()
network→callbackUrl()network.get_callbackUrl()network.get_callbackUrl()network→get_callbackUrl()network→get_callbackUrl()[network callbackUrl]network.get_callbackUrl()network.get_callbackUrl()network.get_callbackUrl()network.get_callbackUrl()network.get_callbackUrl()YNetwork get_callbackUrl

Returns the callback URL to notify of significant state changes.

Returns :

a string corresponding to the callback URL to notify of significant state changes

On failure, throws an exception or returns Y_CALLBACKURL_INVALID.

network→get_discoverable()
network→discoverable()network.get_discoverable()network.get_discoverable()network→get_discoverable()network→get_discoverable()[network discoverable]network.get_discoverable()network.get_discoverable()network.get_discoverable()network.get_discoverable()network.get_discoverable()YNetwork get_discoverable

Returns the activation state of the multicast announce protocols to allow easy discovery of the module in the network neighborhood (uPnP/Bonjour protocol).

Returns :

either Y_DISCOVERABLE_FALSE or Y_DISCOVERABLE_TRUE, according to the activation state of the multicast announce protocols to allow easy discovery of the module in the network neighborhood (uPnP/Bonjour protocol)

On failure, throws an exception or returns Y_DISCOVERABLE_INVALID.

network→get_errorMessage()
network→errorMessage()network.get_errorMessage()network.get_errorMessage()network→get_errorMessage()network→get_errorMessage()[network errorMessage]network.get_errorMessage()network.get_errorMessage()network.get_errorMessage()network.get_errorMessage()network.get_errorMessage()

Returns the error message of the latest error with the network interface.

This method is mostly useful when using the Yoctopuce library with exceptions disabled.

Returns :

a string corresponding to the latest error message that occured while using the network interface object

network→get_errorType()
network→errorType()network.get_errorType()network.get_errorType()network→get_errorType()network→get_errorType()network.get_errorType()network.get_errorType()network.get_errorType()network.get_errorType()network.get_errorType()

Returns the numerical error code of the latest error with the network interface.

This method is mostly useful when using the Yoctopuce library with exceptions disabled.

Returns :

a number corresponding to the code of the latest error that occured while using the network interface object

network→get_friendlyName()
network→friendlyName()network.get_friendlyName()network.get_friendlyName()network→get_friendlyName()network→get_friendlyName()[network friendlyName]network.get_friendlyName()network.get_friendlyName()network.get_friendlyName()

Returns a global identifier of the network interface in the format MODULE_NAME.FUNCTION_NAME.

The returned string uses the logical names of the module and of the network interface if they are defined, otherwise the serial number of the module and the hardware identifier of the network interface (for exemple: MyCustomName.relay1)

Returns :

a string that uniquely identifies the network interface using logical names (ex: MyCustomName.relay1)

On failure, throws an exception or returns Y_FRIENDLYNAME_INVALID.

network→get_functionDescriptor()
network→functionDescriptor()network.get_functionDescriptor()network.get_functionDescriptor()network→get_functionDescriptor()network→get_functionDescriptor()[network functionDescriptor]network.get_functionDescriptor()network.get_functionDescriptor()network.get_functionDescriptor()network.get_functionDescriptor()network.get_functionDescriptor()

Returns a unique identifier of type YFUN_DESCR corresponding to the function.

This identifier can be used to test if two instances of YFunction reference the same physical function on the same physical device.

Returns :

an identifier of type YFUN_DESCR.

If the function has never been contacted, the returned value is Y_FUNCTIONDESCRIPTOR_INVALID.

network→get_functionId()
network→functionId()network.get_functionId()network.get_functionId()network→get_functionId()network→get_functionId()[network functionId]network.get_functionId()network.get_functionId()network.get_functionId()network.get_functionId()

Returns the hardware identifier of the network interface, without reference to the module.

For example relay1

Returns :

a string that identifies the network interface (ex: relay1)

On failure, throws an exception or returns Y_FUNCTIONID_INVALID.

network→get_hardwareId()
network→hardwareId()network.get_hardwareId()network.get_hardwareId()network→get_hardwareId()network→get_hardwareId()[network hardwareId]network.get_hardwareId()network.get_hardwareId()network.get_hardwareId()network.get_hardwareId()

Returns the unique hardware identifier of the network interface in the form SERIAL.FUNCTIONID.

The unique hardware identifier is composed of the device serial number and of the hardware identifier of the network interface (for example RELAYLO1-123456.relay1).

Returns :

a string that uniquely identifies the network interface (ex: RELAYLO1-123456.relay1)

On failure, throws an exception or returns Y_HARDWAREID_INVALID.

network→get_ipAddress()
network→ipAddress()network.get_ipAddress()network.get_ipAddress()network→get_ipAddress()network→get_ipAddress()[network ipAddress]network.get_ipAddress()network.get_ipAddress()network.get_ipAddress()network.get_ipAddress()network.get_ipAddress()YNetwork get_ipAddress

Returns the IP address currently in use by the device.

The address may have been configured statically, or provided by a DHCP server.

Returns :

a string corresponding to the IP address currently in use by the device

On failure, throws an exception or returns Y_IPADDRESS_INVALID.

network→get_logicalName()
network→logicalName()network.get_logicalName()network.get_logicalName()network→get_logicalName()network→get_logicalName()[network logicalName]network.get_logicalName()network.get_logicalName()network.get_logicalName()network.get_logicalName()network.get_logicalName()YNetwork get_logicalName

Returns the logical name of the network interface.

Returns :

a string corresponding to the logical name of the network interface.

On failure, throws an exception or returns Y_LOGICALNAME_INVALID.

network→get_macAddress()
network→macAddress()network.get_macAddress()network.get_macAddress()network→get_macAddress()network→get_macAddress()[network macAddress]network.get_macAddress()network.get_macAddress()network.get_macAddress()network.get_macAddress()network.get_macAddress()YNetwork get_macAddress

Returns the MAC address of the network interface.

The MAC address is also available on a sticker on the module, in both numeric and barcode forms.

Returns :

a string corresponding to the MAC address of the network interface

On failure, throws an exception or returns Y_MACADDRESS_INVALID.

network→get_module()
network→module()network.get_module()network.get_module()network→get_module()network→get_module()[network module]network.get_module()network.get_module()network.get_module()network.get_module()network.get_module()

Gets the YModule object for the device on which the function is located.

If the function cannot be located on any module, the returned instance of YModule is not shown as on-line.

Returns :

an instance of YModule

network→get_module_async()
network→module_async()network.get_module_async()network.get_module_async()

Gets the YModule object for the device on which the function is located (asynchronous version).

If the function cannot be located on any module, the returned YModule object does not show as on-line.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking Firefox javascript VM that does not implement context switching during blocking I/O calls. See the documentation section on asynchronous Javascript calls for more details.

Parameters :

Returns :

nothing : the result is provided to the callback.

network→get_poeCurrent()
network→poeCurrent()network.get_poeCurrent()network.get_poeCurrent()network→get_poeCurrent()network→get_poeCurrent()[network poeCurrent]network.get_poeCurrent()network.get_poeCurrent()network.get_poeCurrent()network.get_poeCurrent()network.get_poeCurrent()YNetwork get_poeCurrent

Returns the current consumed by the module from Power-over-Ethernet (PoE), in milli-amps.

The current consumption is measured after converting PoE source to 5 Volt, and should never exceed 1800 mA.

Returns :

an integer corresponding to the current consumed by the module from Power-over-Ethernet (PoE), in milli-amps

On failure, throws an exception or returns Y_POECURRENT_INVALID.

network→get_primaryDNS()
network→primaryDNS()network.get_primaryDNS()network.get_primaryDNS()network→get_primaryDNS()network→get_primaryDNS()[network primaryDNS]network.get_primaryDNS()network.get_primaryDNS()network.get_primaryDNS()network.get_primaryDNS()network.get_primaryDNS()YNetwork get_primaryDNS

Returns the IP address of the primary name server to be used by the module.

Returns :

a string corresponding to the IP address of the primary name server to be used by the module

On failure, throws an exception or returns Y_PRIMARYDNS_INVALID.

network→get_readiness()
network→readiness()network.get_readiness()network.get_readiness()network→get_readiness()network→get_readiness()[network readiness]network.get_readiness()network.get_readiness()network.get_readiness()network.get_readiness()network.get_readiness()YNetwork get_readiness

Returns the current established working mode of the network interface.

Level zero (DOWN_0) means that no hardware link has been detected. Either there is no signal on the network cable, or the selected wireless access point cannot be detected. Level 1 (LIVE_1) is reached when the network is detected, but is not yet connected. For a wireless network, this shows that the requested SSID is present. Level 2 (LINK_2) is reached when the hardware connection is established. For a wired network connection, level 2 means that the cable is attached at both ends. For a connection to a wireless access point, it shows that the security parameters are properly configured. For an ad-hoc wireless connection, it means that there is at least one other device connected on the ad-hoc network. Level 3 (DHCP_3) is reached when an IP address has been obtained using DHCP. Level 4 (DNS_4) is reached when the DNS server is reachable on the network. Level 5 (WWW_5) is reached when global connectivity is demonstrated by properly loading the current time from an NTP server.

Returns :

a value among Y_READINESS_DOWN, Y_READINESS_EXISTS, Y_READINESS_LINKED, Y_READINESS_LAN_OK and Y_READINESS_WWW_OK corresponding to the current established working mode of the network interface

On failure, throws an exception or returns Y_READINESS_INVALID.

network→get_router()
network→router()network.get_router()network.get_router()network→get_router()network→get_router()[network router]network.get_router()network.get_router()network.get_router()network.get_router()network.get_router()YNetwork get_router

Returns the IP address of the router on the device subnet (default gateway).

Returns :

a string corresponding to the IP address of the router on the device subnet (default gateway)

On failure, throws an exception or returns Y_ROUTER_INVALID.

network→get_secondaryDNS()
network→secondaryDNS()network.get_secondaryDNS()network.get_secondaryDNS()network→get_secondaryDNS()network→get_secondaryDNS()[network secondaryDNS]network.get_secondaryDNS()network.get_secondaryDNS()network.get_secondaryDNS()network.get_secondaryDNS()network.get_secondaryDNS()YNetwork get_secondaryDNS

Returns the IP address of the secondary name server to be used by the module.

Returns :

a string corresponding to the IP address of the secondary name server to be used by the module

On failure, throws an exception or returns Y_SECONDARYDNS_INVALID.

network→get_subnetMask()
network→subnetMask()network.get_subnetMask()network.get_subnetMask()network→get_subnetMask()network→get_subnetMask()[network subnetMask]network.get_subnetMask()network.get_subnetMask()network.get_subnetMask()network.get_subnetMask()network.get_subnetMask()YNetwork get_subnetMask

Returns the subnet mask currently used by the device.

Returns :

a string corresponding to the subnet mask currently used by the device

On failure, throws an exception or returns Y_SUBNETMASK_INVALID.

network→get_userData()
network→userData()network.get_userData()network.get_userData()network→get_userData()network→get_userData()[network userData]network.get_userData()network.get_userData()network.get_userData()network.get_userData()network.get_userData()

Returns the value of the userData attribute, as previously stored using method set_userData.

This attribute is never touched directly by the API, and is at disposal of the caller to store a context.

Returns :

the object stored previously by the caller.

network→get_userPassword()
network→userPassword()network.get_userPassword()network.get_userPassword()network→get_userPassword()network→get_userPassword()[network userPassword]network.get_userPassword()network.get_userPassword()network.get_userPassword()network.get_userPassword()network.get_userPassword()YNetwork get_userPassword

Returns a hash string if a password has been set for "user" user, or an empty string otherwise.

Returns :

a string corresponding to a hash string if a password has been set for "user" user, or an empty string otherwise

On failure, throws an exception or returns Y_USERPASSWORD_INVALID.

network→get_wwwWatchdogDelay()
network→wwwWatchdogDelay()network.get_wwwWatchdogDelay()network.get_wwwWatchdogDelay()network→get_wwwWatchdogDelay()network→get_wwwWatchdogDelay()[network wwwWatchdogDelay]network.get_wwwWatchdogDelay()network.get_wwwWatchdogDelay()network.get_wwwWatchdogDelay()network.get_wwwWatchdogDelay()network.get_wwwWatchdogDelay()YNetwork get_wwwWatchdogDelay

Returns the allowed downtime of the WWW link (in seconds) before triggering an automated reboot to try to recover Internet connectivity.

A zero value disables automated reboot in case of Internet connectivity loss.

Returns :

an integer corresponding to the allowed downtime of the WWW link (in seconds) before triggering an automated reboot to try to recover Internet connectivity

On failure, throws an exception or returns Y_WWWWATCHDOGDELAY_INVALID.

network→isOnline()network.isOnline()network.isOnline()network→isOnline()network→isOnline()[network isOnline]network.isOnline()network.isOnline()network.isOnline()network.isOnline()network.isOnline()

Checks if the network interface is currently reachable, without raising any error.

If there is a cached value for the network interface in cache, that has not yet expired, the device is considered reachable. No exception is raised if there is an error while trying to contact the device hosting the network interface.

Returns :

true if the network interface can be reached, and false otherwise

network→isOnline_async()network.isOnline_async()network.isOnline_async()

Checks if the network interface is currently reachable, without raising any error (asynchronous version).

If there is a cached value for the network interface in cache, that has not yet expired, the device is considered reachable. No exception is raised if there is an error while trying to contact the device hosting the requested function.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking the Javascript virtual machine.

Parameters :

Returns :

nothing : the result is provided to the callback.

network→load()network.load()network.load()network→load()network→load()[network load: ]network.load()network.load()network.load()network.load()network.load()

Preloads the network interface cache with a specified validity duration.

By default, whenever accessing a device, all function attributes are kept in cache for the standard duration (5 ms). This method can be used to temporarily mark the cache as valid for a longer period, in order to reduce network trafic for instance.

Parameters :

Returns :

YAPI_SUCCESS when the call succeeds.

On failure, throws an exception or returns a negative error code.

network→load_async()network.load_async()network.load_async()

Preloads the network interface cache with a specified validity duration (asynchronous version).

By default, whenever accessing a device, all function attributes are kept in cache for the standard duration (5 ms). This method can be used to temporarily mark the cache as valid for a longer period, in order to reduce network trafic for instance.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking the Javascript virtual machine.

Parameters :

Returns :

nothing : the result is provided to the callback.

network→nextNetwork()network.nextNetwork()network.nextNetwork()network→nextNetwork()network→nextNetwork()[network nextNetwork]network.nextNetwork()network.nextNetwork()network.nextNetwork()network.nextNetwork()network.nextNetwork()

Continues the enumeration of network interfaces started using yFirstNetwork().

Returns :

a pointer to a YNetwork object, corresponding to a network interface currently online, or a null pointer if there are no more network interfaces to enumerate.

network→ping()network.ping()network.ping()network→ping()network→ping()[network ping: ]network.ping()network.ping()network.ping()network.ping()network.ping()YNetwork ping

Pings str_host to test the network connectivity.

Sends four ICMP ECHO_REQUEST requests from the module to the target str_host. This method returns a string with the result of the 4 ICMP ECHO_REQUEST requests.

Parameters :

Returns :

a string with the result of the ping.

network→registerValueCallback()network.registerValueCallback()network.registerValueCallback()network→registerValueCallback()network→registerValueCallback()[network registerValueCallback: ]network.registerValueCallback()network.registerValueCallback()network.registerValueCallback()network.registerValueCallback()network.registerValueCallback()

Registers the callback function that is invoked on every change of advertised value.

The callback is invoked only during the execution of ySleep or yHandleEvents. This provides control over the time when the callback is triggered. For good responsiveness, remember to call one of these two functions periodically. To unregister a callback, pass a null pointer as argument.

Parameters :

network→set_adminPassword()
network→setAdminPassword()network.set_adminPassword()network.set_adminPassword()network→set_adminPassword()network→set_adminPassword()[network setAdminPassword: ]network.set_adminPassword()network.set_adminPassword()network.set_adminPassword()network.set_adminPassword()network.set_adminPassword()YNetwork set_adminPassword

Changes the password for the "admin" user.

This password becomes instantly required to perform any change of the module state. If the specified value is an empty string, a password is not required anymore. Remember to call the saveToFlash() method of the module if the modification must be kept.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→set_callbackCredentials()
network→setCallbackCredentials()network.set_callbackCredentials()network.set_callbackCredentials()network→set_callbackCredentials()network→set_callbackCredentials()[network setCallbackCredentials: ]network.set_callbackCredentials()network.set_callbackCredentials()network.set_callbackCredentials()network.set_callbackCredentials()network.set_callbackCredentials()YNetwork set_callbackCredentials

Changes the credentials required to connect to the callback address.

The credentials must be provided as returned by function get_callbackCredentials, in the form username:hash. The method used to compute the hash varies according to the the authentication scheme implemented by the callback, For Basic authentication, the hash is the MD5 of the string username:password. For Digest authentication, the hash is the MD5 of the string username:realm:password. For a simpler way to configure callback credentials, use function callbackLogin instead. Remember to call the saveToFlash() method of the module if the modification must be kept.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→set_callbackEncoding()
network→setCallbackEncoding()network.set_callbackEncoding()network.set_callbackEncoding()network→set_callbackEncoding()network→set_callbackEncoding()[network setCallbackEncoding: ]network.set_callbackEncoding()network.set_callbackEncoding()network.set_callbackEncoding()network.set_callbackEncoding()network.set_callbackEncoding()YNetwork set_callbackEncoding

Changes the encoding standard to use for representing notification values.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→set_callbackMaxDelay()
network→setCallbackMaxDelay()network.set_callbackMaxDelay()network.set_callbackMaxDelay()network→set_callbackMaxDelay()network→set_callbackMaxDelay()[network setCallbackMaxDelay: ]network.set_callbackMaxDelay()network.set_callbackMaxDelay()network.set_callbackMaxDelay()network.set_callbackMaxDelay()network.set_callbackMaxDelay()YNetwork set_callbackMaxDelay

Changes the maximum waiting time between two callback notifications, in seconds.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→set_callbackMethod()
network→setCallbackMethod()network.set_callbackMethod()network.set_callbackMethod()network→set_callbackMethod()network→set_callbackMethod()[network setCallbackMethod: ]network.set_callbackMethod()network.set_callbackMethod()network.set_callbackMethod()network.set_callbackMethod()network.set_callbackMethod()YNetwork set_callbackMethod

Changes the HTTP method used to notify callbacks for significant state changes.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→set_callbackMinDelay()
network→setCallbackMinDelay()network.set_callbackMinDelay()network.set_callbackMinDelay()network→set_callbackMinDelay()network→set_callbackMinDelay()[network setCallbackMinDelay: ]network.set_callbackMinDelay()network.set_callbackMinDelay()network.set_callbackMinDelay()network.set_callbackMinDelay()network.set_callbackMinDelay()YNetwork set_callbackMinDelay

Changes the minimum waiting time between two callback notifications, in seconds.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→set_callbackUrl()
network→setCallbackUrl()network.set_callbackUrl()network.set_callbackUrl()network→set_callbackUrl()network→set_callbackUrl()[network setCallbackUrl: ]network.set_callbackUrl()network.set_callbackUrl()network.set_callbackUrl()network.set_callbackUrl()network.set_callbackUrl()YNetwork set_callbackUrl

Changes the callback URL to notify significant state changes.

Remember to call the saveToFlash() method of the module if the modification must be kept.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→set_discoverable()
network→setDiscoverable()network.set_discoverable()network.set_discoverable()network→set_discoverable()network→set_discoverable()[network setDiscoverable: ]network.set_discoverable()network.set_discoverable()network.set_discoverable()network.set_discoverable()network.set_discoverable()YNetwork set_discoverable

Changes the activation state of the multicast announce protocols to allow easy discovery of the module in the network neighborhood (uPnP/Bonjour protocol).

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→set_logicalName()
network→setLogicalName()network.set_logicalName()network.set_logicalName()network→set_logicalName()network→set_logicalName()[network setLogicalName: ]network.set_logicalName()network.set_logicalName()network.set_logicalName()network.set_logicalName()network.set_logicalName()YNetwork set_logicalName

Changes the logical name of the network interface.

You can use yCheckLogicalName() prior to this call to make sure that your parameter is valid. Remember to call the saveToFlash() method of the module if the modification must be kept.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→set_primaryDNS()
network→setPrimaryDNS()network.set_primaryDNS()network.set_primaryDNS()network→set_primaryDNS()network→set_primaryDNS()[network setPrimaryDNS: ]network.set_primaryDNS()network.set_primaryDNS()network.set_primaryDNS()network.set_primaryDNS()network.set_primaryDNS()YNetwork set_primaryDNS

Changes the IP address of the primary name server to be used by the module.

When using DHCP, if a value is specified, it overrides the value received from the DHCP server. Remember to call the saveToFlash() method and then to reboot the module to apply this setting.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→set_secondaryDNS()
network→setSecondaryDNS()network.set_secondaryDNS()network.set_secondaryDNS()network→set_secondaryDNS()network→set_secondaryDNS()[network setSecondaryDNS: ]network.set_secondaryDNS()network.set_secondaryDNS()network.set_secondaryDNS()network.set_secondaryDNS()network.set_secondaryDNS()YNetwork set_secondaryDNS

Changes the IP address of the secondary name server to be used by the module.

When using DHCP, if a value is specified, it overrides the value received from the DHCP server. Remember to call the saveToFlash() method and then to reboot the module to apply this setting.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→set_userData()
network→setUserData()network.set_userData()network.set_userData()network→set_userData()network→set_userData()[network setUserData: ]network.set_userData()network.set_userData()network.set_userData()network.set_userData()network.set_userData()

Stores a user context provided as argument in the userData attribute of the function.

This attribute is never touched by the API, and is at disposal of the caller to store a context.

Parameters :

network→set_userPassword()
network→setUserPassword()network.set_userPassword()network.set_userPassword()network→set_userPassword()network→set_userPassword()[network setUserPassword: ]network.set_userPassword()network.set_userPassword()network.set_userPassword()network.set_userPassword()network.set_userPassword()YNetwork set_userPassword

Changes the password for the "user" user.

This password becomes instantly required to perform any use of the module. If the specified value is an empty string, a password is not required anymore. Remember to call the saveToFlash() method of the module if the modification must be kept.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→set_wwwWatchdogDelay()
network→setWwwWatchdogDelay()network.set_wwwWatchdogDelay()network.set_wwwWatchdogDelay()network→set_wwwWatchdogDelay()network→set_wwwWatchdogDelay()[network setWwwWatchdogDelay: ]network.set_wwwWatchdogDelay()network.set_wwwWatchdogDelay()network.set_wwwWatchdogDelay()network.set_wwwWatchdogDelay()network.set_wwwWatchdogDelay()YNetwork set_wwwWatchdogDelay

Changes the allowed downtime of the WWW link (in seconds) before triggering an automated reboot to try to recover Internet connectivity.

A zero value disables automated reboot in case of Internet connectivity loss. The smallest valid non-zero timeout is 90 seconds.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→useDHCP()network.useDHCP()network.useDHCP()network→useDHCP()network→useDHCP()[network useDHCP: ]network.useDHCP()network.useDHCP()network.useDHCP()network.useDHCP()network.useDHCP()YNetwork useDHCP

Changes the configuration of the network interface to enable the use of an IP address received from a DHCP server.

Until an address is received from a DHCP server, the module uses the IP parameters specified to this function. Remember to call the saveToFlash() method and then to reboot the module to apply this setting.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→useStaticIP()network.useStaticIP()network.useStaticIP()network→useStaticIP()network→useStaticIP()[network useStaticIP: ]network.useStaticIP()network.useStaticIP()network.useStaticIP()network.useStaticIP()network.useStaticIP()YNetwork useStaticIP

Changes the configuration of the network interface to use a static IP address.

Remember to call the saveToFlash() method and then to reboot the module to apply this setting.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

network→wait_async()network.wait_async()network.wait_async()

Waits for all pending asynchronous commands on the module to complete, and invoke the user-provided callback function.

The callback function can therefore freely issue synchronous or asynchronous commands, without risking to block the Javascript VM.

Parameters :

Returns :

nothing.

11.4. Files function interface

The filesystem interface makes it possible to store files on some devices, for instance to design a custom web UI (for networked devices) or to add fonts (on display devices).

Global functions
yFindFiles(func)
Retrieves a filesystem for a given identifier.
yFirstFiles()
Starts the enumeration of filesystems currently accessible.
YFiles methods
files→describe()
Returns a short text that describes unambiguously the instance of the filesystem in the form TYPE(NAME)=SERIAL.FUNCTIONID.
files→download(pathname)
Downloads the requested file and returns a binary buffer with its content.
files→download_async(pathname, callback, context)
Downloads the requested file and returns a binary buffer with its content.
files→format_fs()
Reinitializes the filesystem to its clean, unfragmented, empty state.
files→get_advertisedValue()
Returns the current value of the filesystem (no more than 6 characters).
files→get_errorMessage()
Returns the error message of the latest error with the filesystem.
files→get_errorType()
Returns the numerical error code of the latest error with the filesystem.
files→get_filesCount()
Returns the number of files currently loaded in the filesystem.
files→get_freeSpace()
Returns the free space for uploading new files to the filesystem, in bytes.
files→get_friendlyName()
Returns a global identifier of the filesystem in the format MODULE_NAME.FUNCTION_NAME.
files→get_functionDescriptor()
Returns a unique identifier of type YFUN_DESCR corresponding to the function.
files→get_functionId()
Returns the hardware identifier of the filesystem, without reference to the module.
files→get_hardwareId()
Returns the unique hardware identifier of the filesystem in the form SERIAL.FUNCTIONID.
files→get_list(pattern)
Returns a list of YFileRecord objects that describe files currently loaded in the filesystem.
files→get_logicalName()
Returns the logical name of the filesystem.
files→get_module()
Gets the YModule object for the device on which the function is located.
files→get_module_async(callback, context)
Gets the YModule object for the device on which the function is located (asynchronous version).
files→get_userData()
Returns the value of the userData attribute, as previously stored using method set_userData.
files→isOnline()
Checks if the filesystem is currently reachable, without raising any error.
files→isOnline_async(callback, context)
Checks if the filesystem is currently reachable, without raising any error (asynchronous version).
files→load(msValidity)
Preloads the filesystem cache with a specified validity duration.
files→load_async(msValidity, callback, context)
Preloads the filesystem cache with a specified validity duration (asynchronous version).
files→nextFiles()
Continues the enumeration of filesystems started using yFirstFiles().
files→registerValueCallback(callback)
Registers the callback function that is invoked on every change of advertised value.
files→remove(pathname)
Deletes a file, given by its full path name, from the filesystem.
files→set_logicalName(newval)
Changes the logical name of the filesystem.
files→set_userData(data)
Stores a user context provided as argument in the userData attribute of the function.
files→upload(pathname, content)
Uploads a file to the filesystem, to the specified full path name.
files→wait_async(callback, context)
Waits for all pending asynchronous commands on the module to complete, and invoke the user-provided callback function.

YFiles.FindFiles()
yFindFiles()yFindFiles()YFiles.FindFiles()yFindFiles()yFindFiles()[YFiles FindFiles: ]yFindFiles()yFindFiles()YFiles.FindFiles()YFiles.FindFiles()YFiles.FindFiles()

Retrieves a filesystem for a given identifier.

The identifier can be specified using several formats:

• FunctionLogicalName
• ModuleSerialNumber.FunctionIdentifier
• ModuleSerialNumber.FunctionLogicalName
• ModuleLogicalName.FunctionIdentifier
• ModuleLogicalName.FunctionLogicalName

This function does not require that the filesystem is online at the time it is invoked. The returned object is nevertheless valid. Use the method YFiles.isOnline() to test if the filesystem is indeed online at a given time. In case of ambiguity when looking for a filesystem by logical name, no error is notified: the first instance found is returned. The search is performed first by hardware name, then by logical name.

Parameters :

Returns :

a YFiles object allowing you to drive the filesystem.

YFiles.FirstFiles()
yFirstFiles()yFirstFiles()YFiles.FirstFiles()yFirstFiles()yFirstFiles()[YFiles FirstFiles]yFirstFiles()yFirstFiles()YFiles.FirstFiles()YFiles.FirstFiles()YFiles.FirstFiles()

Starts the enumeration of filesystems currently accessible.

Use the method YFiles.nextFiles() to iterate on next filesystems.

Returns :

a pointer to a YFiles object, corresponding to the first filesystem currently online, or a null pointer if there are none.

files→describe()files.describe()files.describe()files→describe()files→describe()[files describe]files.describe()files.describe()files.describe()files.describe()files.describe()

Returns a short text that describes unambiguously the instance of the filesystem in the form TYPE(NAME)=SERIAL.FUNCTIONID.

More precisely, TYPE is the type of the function, NAME it the name used for the first access to the function, SERIAL is the serial number of the module if the module is connected or "unresolved", and FUNCTIONID is the hardware identifier of the function if the module is connected. For example, this method returns Relay(MyCustomName.relay1)=RELAYLO1-123456.relay1 if the module is already connected or Relay(BadCustomeName.relay1)=unresolved if the module has not yet been connected. This method does not trigger any USB or TCP transaction and can therefore be used in a debugger.

Returns :

a string that describes the filesystem (ex: Relay(MyCustomName.relay1)=RELAYLO1-123456.relay1)

files→download()files.download()files.download()files→download()files→download()[files download: ]files.download()files.download()files.download()YFiles download

Downloads the requested file and returns a binary buffer with its content.

Parameters :

Returns :

a binary buffer with the file content

On failure, throws an exception or returns an empty content.

files→download_async()files.download_async()files.download_async()

Downloads the requested file and returns a binary buffer with its content.

This is the asynchronous version that uses a callback to pass the result when the donwload is completed.

Parameters :

Returns :

nothing.

files→format_fs()files.format_fs()files.format_fs()files→format_fs()files→format_fs()[files format_fs]files.format_fs()files.format_fs()files.format_fs()files.format_fs()files.format_fs()YFiles format_fs

Reinitializes the filesystem to its clean, unfragmented, empty state.

All files previously uploaded are permanently lost.

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

files→get_advertisedValue()
files→advertisedValue()files.get_advertisedValue()files.get_advertisedValue()files→get_advertisedValue()files→get_advertisedValue()[files advertisedValue]files.get_advertisedValue()files.get_advertisedValue()files.get_advertisedValue()files.get_advertisedValue()files.get_advertisedValue()YFiles get_advertisedValue

Returns the current value of the filesystem (no more than 6 characters).

Returns :

a string corresponding to the current value of the filesystem (no more than 6 characters).

On failure, throws an exception or returns Y_ADVERTISEDVALUE_INVALID.

files→get_errorMessage()
files→errorMessage()files.get_errorMessage()files.get_errorMessage()files→get_errorMessage()files→get_errorMessage()[files errorMessage]files.get_errorMessage()files.get_errorMessage()files.get_errorMessage()files.get_errorMessage()files.get_errorMessage()

Returns the error message of the latest error with the filesystem.

This method is mostly useful when using the Yoctopuce library with exceptions disabled.

Returns :

a string corresponding to the latest error message that occured while using the filesystem object

files→get_errorType()
files→errorType()files.get_errorType()files.get_errorType()files→get_errorType()files→get_errorType()files.get_errorType()files.get_errorType()files.get_errorType()files.get_errorType()files.get_errorType()

Returns the numerical error code of the latest error with the filesystem.

This method is mostly useful when using the Yoctopuce library with exceptions disabled.

Returns :

a number corresponding to the code of the latest error that occured while using the filesystem object

files→get_filesCount()
files→filesCount()files.get_filesCount()files.get_filesCount()files→get_filesCount()files→get_filesCount()[files filesCount]files.get_filesCount()files.get_filesCount()files.get_filesCount()files.get_filesCount()files.get_filesCount()YFiles get_filesCount

Returns the number of files currently loaded in the filesystem.

Returns :

an integer corresponding to the number of files currently loaded in the filesystem

On failure, throws an exception or returns Y_FILESCOUNT_INVALID.

files→get_freeSpace()
files→freeSpace()files.get_freeSpace()files.get_freeSpace()files→get_freeSpace()files→get_freeSpace()[files freeSpace]files.get_freeSpace()files.get_freeSpace()files.get_freeSpace()files.get_freeSpace()files.get_freeSpace()YFiles get_freeSpace

Returns the free space for uploading new files to the filesystem, in bytes.

Returns :

an integer corresponding to the free space for uploading new files to the filesystem, in bytes

On failure, throws an exception or returns Y_FREESPACE_INVALID.

files→get_friendlyName()
files→friendlyName()files.get_friendlyName()files.get_friendlyName()files→get_friendlyName()files→get_friendlyName()[files friendlyName]files.get_friendlyName()files.get_friendlyName()files.get_friendlyName()

Returns a global identifier of the filesystem in the format MODULE_NAME.FUNCTION_NAME.

The returned string uses the logical names of the module and of the filesystem if they are defined, otherwise the serial number of the module and the hardware identifier of the filesystem (for exemple: MyCustomName.relay1)

Returns :

a string that uniquely identifies the filesystem using logical names (ex: MyCustomName.relay1)

On failure, throws an exception or returns Y_FRIENDLYNAME_INVALID.

files→get_functionDescriptor()
files→functionDescriptor()files.get_functionDescriptor()files.get_functionDescriptor()files→get_functionDescriptor()files→get_functionDescriptor()[files functionDescriptor]files.get_functionDescriptor()files.get_functionDescriptor()files.get_functionDescriptor()files.get_functionDescriptor()files.get_functionDescriptor()

Returns a unique identifier of type YFUN_DESCR corresponding to the function.

This identifier can be used to test if two instances of YFunction reference the same physical function on the same physical device.

Returns :

an identifier of type YFUN_DESCR.

If the function has never been contacted, the returned value is Y_FUNCTIONDESCRIPTOR_INVALID.

files→get_functionId()
files→functionId()files.get_functionId()files.get_functionId()files→get_functionId()files→get_functionId()[files functionId]files.get_functionId()files.get_functionId()files.get_functionId()files.get_functionId()

Returns the hardware identifier of the filesystem, without reference to the module.

For example relay1

Returns :

a string that identifies the filesystem (ex: relay1)

On failure, throws an exception or returns Y_FUNCTIONID_INVALID.

files→get_hardwareId()
files→hardwareId()files.get_hardwareId()files.get_hardwareId()files→get_hardwareId()files→get_hardwareId()[files hardwareId]files.get_hardwareId()files.get_hardwareId()files.get_hardwareId()files.get_hardwareId()

Returns the unique hardware identifier of the filesystem in the form SERIAL.FUNCTIONID.

The unique hardware identifier is composed of the device serial number and of the hardware identifier of the filesystem (for example RELAYLO1-123456.relay1).

Returns :

a string that uniquely identifies the filesystem (ex: RELAYLO1-123456.relay1)

On failure, throws an exception or returns Y_HARDWAREID_INVALID.

files→get_list()
files→list()files.get_list()files.get_list()files→get_list()files→get_list()[files list: ]files.get_list()files.get_list()files.get_list()files.get_list()files.get_list()YFiles get_list

Returns a list of YFileRecord objects that describe files currently loaded in the filesystem.

Parameters :

Returns :

a list of YFileRecord objects, containing the file path and name, byte size and 32-bit CRC of the file content.

On failure, throws an exception or returns an empty list.

files→get_logicalName()
files→logicalName()files.get_logicalName()files.get_logicalName()files→get_logicalName()files→get_logicalName()[files logicalName]files.get_logicalName()files.get_logicalName()files.get_logicalName()files.get_logicalName()files.get_logicalName()YFiles get_logicalName

Returns the logical name of the filesystem.

Returns :

a string corresponding to the logical name of the filesystem.

On failure, throws an exception or returns Y_LOGICALNAME_INVALID.

files→get_module()
files→module()files.get_module()files.get_module()files→get_module()files→get_module()[files module]files.get_module()files.get_module()files.get_module()files.get_module()files.get_module()

Gets the YModule object for the device on which the function is located.

If the function cannot be located on any module, the returned instance of YModule is not shown as on-line.

Returns :

an instance of YModule

files→get_module_async()
files→module_async()files.get_module_async()files.get_module_async()

Gets the YModule object for the device on which the function is located (asynchronous version).

If the function cannot be located on any module, the returned YModule object does not show as on-line.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking Firefox javascript VM that does not implement context switching during blocking I/O calls. See the documentation section on asynchronous Javascript calls for more details.

Parameters :

Returns :

nothing : the result is provided to the callback.

files→get_userData()
files→userData()files.get_userData()files.get_userData()files→get_userData()files→get_userData()[files userData]files.get_userData()files.get_userData()files.get_userData()files.get_userData()files.get_userData()

Returns the value of the userData attribute, as previously stored using method set_userData.

This attribute is never touched directly by the API, and is at disposal of the caller to store a context.

Returns :

the object stored previously by the caller.

files→isOnline()files.isOnline()files.isOnline()files→isOnline()files→isOnline()[files isOnline]files.isOnline()files.isOnline()files.isOnline()files.isOnline()files.isOnline()

Checks if the filesystem is currently reachable, without raising any error.

If there is a cached value for the filesystem in cache, that has not yet expired, the device is considered reachable. No exception is raised if there is an error while trying to contact the device hosting the filesystem.

Returns :

true if the filesystem can be reached, and false otherwise

files→isOnline_async()files.isOnline_async()files.isOnline_async()

Checks if the filesystem is currently reachable, without raising any error (asynchronous version).

If there is a cached value for the filesystem in cache, that has not yet expired, the device is considered reachable. No exception is raised if there is an error while trying to contact the device hosting the requested function.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking the Javascript virtual machine.

Parameters :

Returns :

nothing : the result is provided to the callback.

files→load()files.load()files.load()files→load()files→load()[files load: ]files.load()files.load()files.load()files.load()files.load()

Preloads the filesystem cache with a specified validity duration.

By default, whenever accessing a device, all function attributes are kept in cache for the standard duration (5 ms). This method can be used to temporarily mark the cache as valid for a longer period, in order to reduce network trafic for instance.

Parameters :

Returns :

YAPI_SUCCESS when the call succeeds.

On failure, throws an exception or returns a negative error code.

files→load_async()files.load_async()files.load_async()

Preloads the filesystem cache with a specified validity duration (asynchronous version).

By default, whenever accessing a device, all function attributes are kept in cache for the standard duration (5 ms). This method can be used to temporarily mark the cache as valid for a longer period, in order to reduce network trafic for instance.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking the Javascript virtual machine.

Parameters :

Returns :

nothing : the result is provided to the callback.

files→nextFiles()files.nextFiles()files.nextFiles()files→nextFiles()files→nextFiles()[files nextFiles]files.nextFiles()files.nextFiles()files.nextFiles()files.nextFiles()files.nextFiles()

Continues the enumeration of filesystems started using yFirstFiles().

Returns :

a pointer to a YFiles object, corresponding to a filesystem currently online, or a null pointer if there are no more filesystems to enumerate.

files→registerValueCallback()files.registerValueCallback()files.registerValueCallback()files→registerValueCallback()files→registerValueCallback()[files registerValueCallback: ]files.registerValueCallback()files.registerValueCallback()files.registerValueCallback()files.registerValueCallback()files.registerValueCallback()

Registers the callback function that is invoked on every change of advertised value.

The callback is invoked only during the execution of ySleep or yHandleEvents. This provides control over the time when the callback is triggered. For good responsiveness, remember to call one of these two functions periodically. To unregister a callback, pass a null pointer as argument.

Parameters :

files→remove()files.remove()files.remove()files→remove()files→remove()[files remove: ]files.remove()files.remove()files.remove()files.remove()files.remove()YFiles remove

Deletes a file, given by its full path name, from the filesystem.

Because of filesystem fragmentation, deleting a file may not always free up the whole space used by the file. However, rewriting a file with the same path name will always reuse any space not freed previously. If you need to ensure that no space is taken by previously deleted files, you can use format_fs to fully reinitialize the filesystem.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

files→set_logicalName()
files→setLogicalName()files.set_logicalName()files.set_logicalName()files→set_logicalName()files→set_logicalName()[files setLogicalName: ]files.set_logicalName()files.set_logicalName()files.set_logicalName()files.set_logicalName()files.set_logicalName()YFiles set_logicalName

Changes the logical name of the filesystem.

You can use yCheckLogicalName() prior to this call to make sure that your parameter is valid. Remember to call the saveToFlash() method of the module if the modification must be kept.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

files→set_userData()
files→setUserData()files.set_userData()files.set_userData()files→set_userData()files→set_userData()[files setUserData: ]files.set_userData()files.set_userData()files.set_userData()files.set_userData()files.set_userData()

Stores a user context provided as argument in the userData attribute of the function.

This attribute is never touched by the API, and is at disposal of the caller to store a context.

Parameters :

files→upload()files.upload()files.upload()files→upload()files→upload()[files upload: ]files.upload()files.upload()files.upload()files.upload()files.upload()YFiles upload

Uploads a file to the filesystem, to the specified full path name.

If a file already exists with the same path name, its content is overwritten.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

files→wait_async()files.wait_async()files.wait_async()

Waits for all pending asynchronous commands on the module to complete, and invoke the user-provided callback function.

The callback function can therefore freely issue synchronous or asynchronous commands, without risking to block the Javascript VM.

Parameters :

Returns :

nothing.

11.5. WakeUpMonitor function interface

The WakeUpMonitor function handles globally all wake-up sources, as well as automated sleep mode.

Global functions
yFindWakeUpMonitor(func)
Retrieves a monitor for a given identifier.
yFirstWakeUpMonitor()
Starts the enumeration of monitors currently accessible.
YWakeUpMonitor methods
wakeupmonitor→describe()
Returns a short text that describes unambiguously the instance of the monitor in the form TYPE(NAME)=SERIAL.FUNCTIONID.
wakeupmonitor→get_advertisedValue()
Returns the current value of the monitor (no more than 6 characters).
wakeupmonitor→get_errorMessage()
Returns the error message of the latest error with the monitor.
wakeupmonitor→get_errorType()
Returns the numerical error code of the latest error with the monitor.
wakeupmonitor→get_friendlyName()
Returns a global identifier of the monitor in the format MODULE_NAME.FUNCTION_NAME.
wakeupmonitor→get_functionDescriptor()
Returns a unique identifier of type YFUN_DESCR corresponding to the function.
wakeupmonitor→get_functionId()
Returns the hardware identifier of the monitor, without reference to the module.
wakeupmonitor→get_hardwareId()
Returns the unique hardware identifier of the monitor in the form SERIAL.FUNCTIONID.
wakeupmonitor→get_logicalName()
Returns the logical name of the monitor.
wakeupmonitor→get_module()
Gets the YModule object for the device on which the function is located.
wakeupmonitor→get_module_async(callback, context)
Gets the YModule object for the device on which the function is located (asynchronous version).
wakeupmonitor→get_nextWakeUp()
Returns the next scheduled wake up date/time (UNIX format)
wakeupmonitor→get_powerDuration()
Returns the maximal wake up time (in seconds) before automatically going to sleep.
wakeupmonitor→get_sleepCountdown()
Returns the delay before the next sleep period.
wakeupmonitor→get_userData()
Returns the value of the userData attribute, as previously stored using method set_userData.
wakeupmonitor→get_wakeUpReason()
Returns the latest wake up reason.
wakeupmonitor→get_wakeUpState()
Returns the current state of the monitor
wakeupmonitor→isOnline()
Checks if the monitor is currently reachable, without raising any error.
wakeupmonitor→isOnline_async(callback, context)
Checks if the monitor is currently reachable, without raising any error (asynchronous version).
wakeupmonitor→load(msValidity)
Preloads the monitor cache with a specified validity duration.
wakeupmonitor→load_async(msValidity, callback, context)
Preloads the monitor cache with a specified validity duration (asynchronous version).
wakeupmonitor→nextWakeUpMonitor()
Continues the enumeration of monitors started using yFirstWakeUpMonitor().
wakeupmonitor→registerValueCallback(callback)
Registers the callback function that is invoked on every change of advertised value.
wakeupmonitor→resetSleepCountDown()
Resets the sleep countdown.
wakeupmonitor→set_logicalName(newval)
Changes the logical name of the monitor.
wakeupmonitor→set_nextWakeUp(newval)
Changes the days of the week when a wake up must take place.
wakeupmonitor→set_powerDuration(newval)
Changes the maximal wake up time (seconds) before automatically going to sleep.
wakeupmonitor→set_sleepCountdown(newval)
Changes the delay before the next sleep period.
wakeupmonitor→set_userData(data)
Stores a user context provided as argument in the userData attribute of the function.
wakeupmonitor→sleep(secBeforeSleep)
Goes to sleep until the next wake up condition is met, the RTC time must have been set before calling this function.
wakeupmonitor→sleepFor(secUntilWakeUp, secBeforeSleep)
Goes to sleep for a specific duration or until the next wake up condition is met, the RTC time must have been set before calling this function.
wakeupmonitor→sleepUntil(wakeUpTime, secBeforeSleep)
Go to sleep until a specific date is reached or until the next wake up condition is met, the RTC time must have been set before calling this function.
wakeupmonitor→wait_async(callback, context)
Waits for all pending asynchronous commands on the module to complete, and invoke the user-provided callback function.
wakeupmonitor→wakeUp()
Forces a wake up.

YWakeUpMonitor.FindWakeUpMonitor()
yFindWakeUpMonitor()yFindWakeUpMonitor()YWakeUpMonitor.FindWakeUpMonitor()yFindWakeUpMonitor()yFindWakeUpMonitor()[YWakeUpMonitor FindWakeUpMonitor: ]yFindWakeUpMonitor()yFindWakeUpMonitor()YWakeUpMonitor.FindWakeUpMonitor()YWakeUpMonitor.FindWakeUpMonitor()YWakeUpMonitor.FindWakeUpMonitor()

Retrieves a monitor for a given identifier.

The identifier can be specified using several formats:

• FunctionLogicalName
• ModuleSerialNumber.FunctionIdentifier
• ModuleSerialNumber.FunctionLogicalName
• ModuleLogicalName.FunctionIdentifier
• ModuleLogicalName.FunctionLogicalName

This function does not require that the monitor is online at the time it is invoked. The returned object is nevertheless valid. Use the method YWakeUpMonitor.isOnline() to test if the monitor is indeed online at a given time. In case of ambiguity when looking for a monitor by logical name, no error is notified: the first instance found is returned. The search is performed first by hardware name, then by logical name.

Parameters :

Returns :

a YWakeUpMonitor object allowing you to drive the monitor.

YWakeUpMonitor.FirstWakeUpMonitor()
yFirstWakeUpMonitor()yFirstWakeUpMonitor()YWakeUpMonitor.FirstWakeUpMonitor()yFirstWakeUpMonitor()yFirstWakeUpMonitor()[YWakeUpMonitor FirstWakeUpMonitor]yFirstWakeUpMonitor()yFirstWakeUpMonitor()YWakeUpMonitor.FirstWakeUpMonitor()YWakeUpMonitor.FirstWakeUpMonitor()YWakeUpMonitor.FirstWakeUpMonitor()

Starts the enumeration of monitors currently accessible.

Use the method YWakeUpMonitor.nextWakeUpMonitor() to iterate on next monitors.

Returns :

a pointer to a YWakeUpMonitor object, corresponding to the first monitor currently online, or a null pointer if there are none.

wakeupmonitor→describe()wakeupmonitor.describe()wakeupmonitor.describe()wakeupmonitor→describe()wakeupmonitor→describe()[wakeupmonitor describe]wakeupmonitor.describe()wakeupmonitor.describe()wakeupmonitor.describe()wakeupmonitor.describe()wakeupmonitor.describe()

Returns a short text that describes unambiguously the instance of the monitor in the form TYPE(NAME)=SERIAL.FUNCTIONID.

More precisely, TYPE is the type of the function, NAME it the name used for the first access to the function, SERIAL is the serial number of the module if the module is connected or "unresolved", and FUNCTIONID is the hardware identifier of the function if the module is connected. For example, this method returns Relay(MyCustomName.relay1)=RELAYLO1-123456.relay1 if the module is already connected or Relay(BadCustomeName.relay1)=unresolved if the module has not yet been connected. This method does not trigger any USB or TCP transaction and can therefore be used in a debugger.

Returns :

a string that describes the monitor (ex: Relay(MyCustomName.relay1)=RELAYLO1-123456.relay1)

wakeupmonitor→get_advertisedValue()
wakeupmonitor→advertisedValue()wakeupmonitor.get_advertisedValue()wakeupmonitor.get_advertisedValue()wakeupmonitor→get_advertisedValue()wakeupmonitor→get_advertisedValue()[wakeupmonitor advertisedValue]wakeupmonitor.get_advertisedValue()wakeupmonitor.get_advertisedValue()wakeupmonitor.get_advertisedValue()wakeupmonitor.get_advertisedValue()wakeupmonitor.get_advertisedValue()YWakeUpMonitor get_advertisedValue

Returns the current value of the monitor (no more than 6 characters).

Returns :

a string corresponding to the current value of the monitor (no more than 6 characters).

On failure, throws an exception or returns Y_ADVERTISEDVALUE_INVALID.

wakeupmonitor→get_errorMessage()
wakeupmonitor→errorMessage()wakeupmonitor.get_errorMessage()wakeupmonitor.get_errorMessage()wakeupmonitor→get_errorMessage()wakeupmonitor→get_errorMessage()[wakeupmonitor errorMessage]wakeupmonitor.get_errorMessage()wakeupmonitor.get_errorMessage()wakeupmonitor.get_errorMessage()wakeupmonitor.get_errorMessage()wakeupmonitor.get_errorMessage()

Returns the error message of the latest error with the monitor.

This method is mostly useful when using the Yoctopuce library with exceptions disabled.

Returns :

a string corresponding to the latest error message that occured while using the monitor object

wakeupmonitor→get_errorType()
wakeupmonitor→errorType()wakeupmonitor.get_errorType()wakeupmonitor.get_errorType()wakeupmonitor→get_errorType()wakeupmonitor→get_errorType()wakeupmonitor.get_errorType()wakeupmonitor.get_errorType()wakeupmonitor.get_errorType()wakeupmonitor.get_errorType()wakeupmonitor.get_errorType()

Returns the numerical error code of the latest error with the monitor.

This method is mostly useful when using the Yoctopuce library with exceptions disabled.

Returns :

a number corresponding to the code of the latest error that occured while using the monitor object

wakeupmonitor→get_friendlyName()
wakeupmonitor→friendlyName()wakeupmonitor.get_friendlyName()wakeupmonitor.get_friendlyName()wakeupmonitor→get_friendlyName()wakeupmonitor→get_friendlyName()[wakeupmonitor friendlyName]wakeupmonitor.get_friendlyName()wakeupmonitor.get_friendlyName()wakeupmonitor.get_friendlyName()

Returns a global identifier of the monitor in the format MODULE_NAME.FUNCTION_NAME.

The returned string uses the logical names of the module and of the monitor if they are defined, otherwise the serial number of the module and the hardware identifier of the monitor (for exemple: MyCustomName.relay1)

Returns :

a string that uniquely identifies the monitor using logical names (ex: MyCustomName.relay1)

On failure, throws an exception or returns Y_FRIENDLYNAME_INVALID.

wakeupmonitor→get_functionDescriptor()
wakeupmonitor→functionDescriptor()wakeupmonitor.get_functionDescriptor()wakeupmonitor.get_functionDescriptor()wakeupmonitor→get_functionDescriptor()wakeupmonitor→get_functionDescriptor()[wakeupmonitor functionDescriptor]wakeupmonitor.get_functionDescriptor()wakeupmonitor.get_functionDescriptor()wakeupmonitor.get_functionDescriptor()wakeupmonitor.get_functionDescriptor()wakeupmonitor.get_functionDescriptor()

Returns a unique identifier of type YFUN_DESCR corresponding to the function.

This identifier can be used to test if two instances of YFunction reference the same physical function on the same physical device.

Returns :

an identifier of type YFUN_DESCR.

If the function has never been contacted, the returned value is Y_FUNCTIONDESCRIPTOR_INVALID.

wakeupmonitor→get_functionId()
wakeupmonitor→functionId()wakeupmonitor.get_functionId()wakeupmonitor.get_functionId()wakeupmonitor→get_functionId()wakeupmonitor→get_functionId()[wakeupmonitor functionId]wakeupmonitor.get_functionId()wakeupmonitor.get_functionId()wakeupmonitor.get_functionId()wakeupmonitor.get_functionId()

Returns the hardware identifier of the monitor, without reference to the module.

For example relay1

Returns :

a string that identifies the monitor (ex: relay1)

On failure, throws an exception or returns Y_FUNCTIONID_INVALID.

wakeupmonitor→get_hardwareId()
wakeupmonitor→hardwareId()wakeupmonitor.get_hardwareId()wakeupmonitor.get_hardwareId()wakeupmonitor→get_hardwareId()wakeupmonitor→get_hardwareId()[wakeupmonitor hardwareId]wakeupmonitor.get_hardwareId()wakeupmonitor.get_hardwareId()wakeupmonitor.get_hardwareId()wakeupmonitor.get_hardwareId()

Returns the unique hardware identifier of the monitor in the form SERIAL.FUNCTIONID.

The unique hardware identifier is composed of the device serial number and of the hardware identifier of the monitor (for example RELAYLO1-123456.relay1).

Returns :

a string that uniquely identifies the monitor (ex: RELAYLO1-123456.relay1)

On failure, throws an exception or returns Y_HARDWAREID_INVALID.

wakeupmonitor→get_logicalName()
wakeupmonitor→logicalName()wakeupmonitor.get_logicalName()wakeupmonitor.get_logicalName()wakeupmonitor→get_logicalName()wakeupmonitor→get_logicalName()[wakeupmonitor logicalName]wakeupmonitor.get_logicalName()wakeupmonitor.get_logicalName()wakeupmonitor.get_logicalName()wakeupmonitor.get_logicalName()wakeupmonitor.get_logicalName()YWakeUpMonitor get_logicalName

Returns the logical name of the monitor.

Returns :

a string corresponding to the logical name of the monitor.

On failure, throws an exception or returns Y_LOGICALNAME_INVALID.

wakeupmonitor→get_module()
wakeupmonitor→module()wakeupmonitor.get_module()wakeupmonitor.get_module()wakeupmonitor→get_module()wakeupmonitor→get_module()[wakeupmonitor module]wakeupmonitor.get_module()wakeupmonitor.get_module()wakeupmonitor.get_module()wakeupmonitor.get_module()wakeupmonitor.get_module()

Gets the YModule object for the device on which the function is located.

If the function cannot be located on any module, the returned instance of YModule is not shown as on-line.

Returns :

an instance of YModule

wakeupmonitor→get_module_async()
wakeupmonitor→module_async()wakeupmonitor.get_module_async()wakeupmonitor.get_module_async()

Gets the YModule object for the device on which the function is located (asynchronous version).

If the function cannot be located on any module, the returned YModule object does not show as on-line.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking Firefox javascript VM that does not implement context switching during blocking I/O calls. See the documentation section on asynchronous Javascript calls for more details.

Parameters :

Returns :

nothing : the result is provided to the callback.

wakeupmonitor→get_nextWakeUp()
wakeupmonitor→nextWakeUp()wakeupmonitor.get_nextWakeUp()wakeupmonitor.get_nextWakeUp()wakeupmonitor→get_nextWakeUp()wakeupmonitor→get_nextWakeUp()[wakeupmonitor nextWakeUp]wakeupmonitor.get_nextWakeUp()wakeupmonitor.get_nextWakeUp()wakeupmonitor.get_nextWakeUp()wakeupmonitor.get_nextWakeUp()wakeupmonitor.get_nextWakeUp()

Returns the next scheduled wake up date/time (UNIX format)

Returns :

an integer corresponding to the next scheduled wake up date/time (UNIX format)

On failure, throws an exception or returns Y_NEXTWAKEUP_INVALID.

wakeupmonitor→get_powerDuration()
wakeupmonitor→powerDuration()wakeupmonitor.get_powerDuration()wakeupmonitor.get_powerDuration()wakeupmonitor→get_powerDuration()wakeupmonitor→get_powerDuration()[wakeupmonitor powerDuration]wakeupmonitor.get_powerDuration()wakeupmonitor.get_powerDuration()wakeupmonitor.get_powerDuration()wakeupmonitor.get_powerDuration()wakeupmonitor.get_powerDuration()YWakeUpMonitor get_powerDuration

Returns the maximal wake up time (in seconds) before automatically going to sleep.

Returns :

an integer corresponding to the maximal wake up time (in seconds) before automatically going to sleep

On failure, throws an exception or returns Y_POWERDURATION_INVALID.

wakeupmonitor→get_sleepCountdown()
wakeupmonitor→sleepCountdown()wakeupmonitor.get_sleepCountdown()wakeupmonitor.get_sleepCountdown()wakeupmonitor→get_sleepCountdown()wakeupmonitor→get_sleepCountdown()[wakeupmonitor sleepCountdown]wakeupmonitor.get_sleepCountdown()wakeupmonitor.get_sleepCountdown()wakeupmonitor.get_sleepCountdown()wakeupmonitor.get_sleepCountdown()wakeupmonitor.get_sleepCountdown()YWakeUpMonitor get_sleepCountdown

Returns the delay before the next sleep period.

Returns :

an integer corresponding to the delay before the next sleep period

On failure, throws an exception or returns Y_SLEEPCOUNTDOWN_INVALID.

wakeupmonitor→get_userData()
wakeupmonitor→userData()wakeupmonitor.get_userData()wakeupmonitor.get_userData()wakeupmonitor→get_userData()wakeupmonitor→get_userData()[wakeupmonitor userData]wakeupmonitor.get_userData()wakeupmonitor.get_userData()wakeupmonitor.get_userData()wakeupmonitor.get_userData()wakeupmonitor.get_userData()

Returns the value of the userData attribute, as previously stored using method set_userData.

This attribute is never touched directly by the API, and is at disposal of the caller to store a context.

Returns :

the object stored previously by the caller.

wakeupmonitor→get_wakeUpReason()
wakeupmonitor→wakeUpReason()wakeupmonitor.get_wakeUpReason()wakeupmonitor.get_wakeUpReason()wakeupmonitor→get_wakeUpReason()wakeupmonitor→get_wakeUpReason()[wakeupmonitor wakeUpReason]wakeupmonitor.get_wakeUpReason()wakeupmonitor.get_wakeUpReason()wakeupmonitor.get_wakeUpReason()wakeupmonitor.get_wakeUpReason()wakeupmonitor.get_wakeUpReason()YWakeUpMonitor get_wakeUpReason

Returns the latest wake up reason.

Returns :

a value among Y_WAKEUPREASON_USBPOWER, Y_WAKEUPREASON_EXTPOWER, Y_WAKEUPREASON_ENDOFSLEEP, Y_WAKEUPREASON_EXTSIG1, Y_WAKEUPREASON_SCHEDULE1 and Y_WAKEUPREASON_SCHEDULE2 corresponding to the latest wake up reason

On failure, throws an exception or returns Y_WAKEUPREASON_INVALID.

wakeupmonitor→get_wakeUpState()
wakeupmonitor→wakeUpState()wakeupmonitor.get_wakeUpState()wakeupmonitor.get_wakeUpState()wakeupmonitor→get_wakeUpState()wakeupmonitor→get_wakeUpState()[wakeupmonitor wakeUpState]wakeupmonitor.get_wakeUpState()wakeupmonitor.get_wakeUpState()wakeupmonitor.get_wakeUpState()wakeupmonitor.get_wakeUpState()wakeupmonitor.get_wakeUpState()

Returns the current state of the monitor

Returns :

either Y_WAKEUPSTATE_SLEEPING or Y_WAKEUPSTATE_AWAKE, according to the current state of the monitor

On failure, throws an exception or returns Y_WAKEUPSTATE_INVALID.

wakeupmonitor→isOnline()wakeupmonitor.isOnline()wakeupmonitor.isOnline()wakeupmonitor→isOnline()wakeupmonitor→isOnline()[wakeupmonitor isOnline]wakeupmonitor.isOnline()wakeupmonitor.isOnline()wakeupmonitor.isOnline()wakeupmonitor.isOnline()wakeupmonitor.isOnline()

Checks if the monitor is currently reachable, without raising any error.

If there is a cached value for the monitor in cache, that has not yet expired, the device is considered reachable. No exception is raised if there is an error while trying to contact the device hosting the monitor.

Returns :

true if the monitor can be reached, and false otherwise

wakeupmonitor→isOnline_async()wakeupmonitor.isOnline_async()wakeupmonitor.isOnline_async()

Checks if the monitor is currently reachable, without raising any error (asynchronous version).

If there is a cached value for the monitor in cache, that has not yet expired, the device is considered reachable. No exception is raised if there is an error while trying to contact the device hosting the requested function.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking the Javascript virtual machine.

Parameters :

Returns :

nothing : the result is provided to the callback.

wakeupmonitor→load()wakeupmonitor.load()wakeupmonitor.load()wakeupmonitor→load()wakeupmonitor→load()[wakeupmonitor load: ]wakeupmonitor.load()wakeupmonitor.load()wakeupmonitor.load()wakeupmonitor.load()wakeupmonitor.load()

Preloads the monitor cache with a specified validity duration.

By default, whenever accessing a device, all function attributes are kept in cache for the standard duration (5 ms). This method can be used to temporarily mark the cache as valid for a longer period, in order to reduce network trafic for instance.

Parameters :

Returns :

YAPI_SUCCESS when the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupmonitor→load_async()wakeupmonitor.load_async()wakeupmonitor.load_async()

Preloads the monitor cache with a specified validity duration (asynchronous version).

By default, whenever accessing a device, all function attributes are kept in cache for the standard duration (5 ms). This method can be used to temporarily mark the cache as valid for a longer period, in order to reduce network trafic for instance.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking the Javascript virtual machine.

Parameters :

Returns :

nothing : the result is provided to the callback.

wakeupmonitor→nextWakeUpMonitor()wakeupmonitor.nextWakeUpMonitor()wakeupmonitor.nextWakeUpMonitor()wakeupmonitor→nextWakeUpMonitor()wakeupmonitor→nextWakeUpMonitor()[wakeupmonitor nextWakeUpMonitor]wakeupmonitor.nextWakeUpMonitor()wakeupmonitor.nextWakeUpMonitor()wakeupmonitor.nextWakeUpMonitor()wakeupmonitor.nextWakeUpMonitor()wakeupmonitor.nextWakeUpMonitor()

Continues the enumeration of monitors started using yFirstWakeUpMonitor().

Returns :

a pointer to a YWakeUpMonitor object, corresponding to a monitor currently online, or a null pointer if there are no more monitors to enumerate.

wakeupmonitor→registerValueCallback()wakeupmonitor.registerValueCallback()wakeupmonitor.registerValueCallback()wakeupmonitor→registerValueCallback()wakeupmonitor→registerValueCallback()[wakeupmonitor registerValueCallback: ]wakeupmonitor.registerValueCallback()wakeupmonitor.registerValueCallback()wakeupmonitor.registerValueCallback()wakeupmonitor.registerValueCallback()wakeupmonitor.registerValueCallback()

Registers the callback function that is invoked on every change of advertised value.

The callback is invoked only during the execution of ySleep or yHandleEvents. This provides control over the time when the callback is triggered. For good responsiveness, remember to call one of these two functions periodically. To unregister a callback, pass a null pointer as argument.

Parameters :

wakeupmonitor→resetSleepCountDown()wakeupmonitor.resetSleepCountDown()wakeupmonitor.resetSleepCountDown()wakeupmonitor→resetSleepCountDown()wakeupmonitor→resetSleepCountDown()[wakeupmonitor resetSleepCountDown]wakeupmonitor.resetSleepCountDown()wakeupmonitor.resetSleepCountDown()wakeupmonitor.resetSleepCountDown()wakeupmonitor.resetSleepCountDown()wakeupmonitor.resetSleepCountDown()YWakeUpMonitor resetSleepCountDown

Resets the sleep countdown.

Returns :

YAPI_SUCCESS if the call succeeds. On failure, throws an exception or returns a negative error code.

wakeupmonitor→set_logicalName()
wakeupmonitor→setLogicalName()wakeupmonitor.set_logicalName()wakeupmonitor.set_logicalName()wakeupmonitor→set_logicalName()wakeupmonitor→set_logicalName()[wakeupmonitor setLogicalName: ]wakeupmonitor.set_logicalName()wakeupmonitor.set_logicalName()wakeupmonitor.set_logicalName()wakeupmonitor.set_logicalName()wakeupmonitor.set_logicalName()YWakeUpMonitor set_logicalName

Changes the logical name of the monitor.

You can use yCheckLogicalName() prior to this call to make sure that your parameter is valid. Remember to call the saveToFlash() method of the module if the modification must be kept.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupmonitor→set_nextWakeUp()
wakeupmonitor→setNextWakeUp()wakeupmonitor.set_nextWakeUp()wakeupmonitor.set_nextWakeUp()wakeupmonitor→set_nextWakeUp()wakeupmonitor→set_nextWakeUp()[wakeupmonitor setNextWakeUp: ]wakeupmonitor.set_nextWakeUp()wakeupmonitor.set_nextWakeUp()wakeupmonitor.set_nextWakeUp()wakeupmonitor.set_nextWakeUp()wakeupmonitor.set_nextWakeUp()YWakeUpMonitor set_nextWakeUp

Changes the days of the week when a wake up must take place.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupmonitor→set_powerDuration()
wakeupmonitor→setPowerDuration()wakeupmonitor.set_powerDuration()wakeupmonitor.set_powerDuration()wakeupmonitor→set_powerDuration()wakeupmonitor→set_powerDuration()[wakeupmonitor setPowerDuration: ]wakeupmonitor.set_powerDuration()wakeupmonitor.set_powerDuration()wakeupmonitor.set_powerDuration()wakeupmonitor.set_powerDuration()wakeupmonitor.set_powerDuration()YWakeUpMonitor set_powerDuration

Changes the maximal wake up time (seconds) before automatically going to sleep.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupmonitor→set_sleepCountdown()
wakeupmonitor→setSleepCountdown()wakeupmonitor.set_sleepCountdown()wakeupmonitor.set_sleepCountdown()wakeupmonitor→set_sleepCountdown()wakeupmonitor→set_sleepCountdown()[wakeupmonitor setSleepCountdown: ]wakeupmonitor.set_sleepCountdown()wakeupmonitor.set_sleepCountdown()wakeupmonitor.set_sleepCountdown()wakeupmonitor.set_sleepCountdown()wakeupmonitor.set_sleepCountdown()YWakeUpMonitor set_sleepCountdown

Changes the delay before the next sleep period.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupmonitor→set_userData()
wakeupmonitor→setUserData()wakeupmonitor.set_userData()wakeupmonitor.set_userData()wakeupmonitor→set_userData()wakeupmonitor→set_userData()[wakeupmonitor setUserData: ]wakeupmonitor.set_userData()wakeupmonitor.set_userData()wakeupmonitor.set_userData()wakeupmonitor.set_userData()wakeupmonitor.set_userData()

Stores a user context provided as argument in the userData attribute of the function.

This attribute is never touched by the API, and is at disposal of the caller to store a context.

Parameters :

wakeupmonitor→sleep()wakeupmonitor.sleep()wakeupmonitor.sleep()wakeupmonitor→sleep()wakeupmonitor→sleep()[wakeupmonitor sleep: ]wakeupmonitor.sleep()wakeupmonitor.sleep()wakeupmonitor.sleep()wakeupmonitor.sleep()wakeupmonitor.sleep()YWakeUpMonitor sleep

Goes to sleep until the next wake up condition is met, the RTC time must have been set before calling this function.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupmonitor→sleepFor()wakeupmonitor.sleepFor()wakeupmonitor.sleepFor()wakeupmonitor→sleepFor()wakeupmonitor→sleepFor()[wakeupmonitor sleepFor: ]wakeupmonitor.sleepFor()wakeupmonitor.sleepFor()wakeupmonitor.sleepFor()wakeupmonitor.sleepFor()wakeupmonitor.sleepFor()YWakeUpMonitor sleepFor

Goes to sleep for a specific duration or until the next wake up condition is met, the RTC time must have been set before calling this function.

The count down before sleep can be canceled with resetSleepCountDown.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupmonitor→sleepUntil()wakeupmonitor.sleepUntil()wakeupmonitor.sleepUntil()wakeupmonitor→sleepUntil()wakeupmonitor→sleepUntil()[wakeupmonitor sleepUntil: ]wakeupmonitor.sleepUntil()wakeupmonitor.sleepUntil()wakeupmonitor.sleepUntil()wakeupmonitor.sleepUntil()wakeupmonitor.sleepUntil()YWakeUpMonitor sleepUntil

Go to sleep until a specific date is reached or until the next wake up condition is met, the RTC time must have been set before calling this function.

The count down before sleep can be canceled with resetSleepCountDown.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupmonitor→wait_async()wakeupmonitor.wait_async()wakeupmonitor.wait_async()

Waits for all pending asynchronous commands on the module to complete, and invoke the user-provided callback function.

The callback function can therefore freely issue synchronous or asynchronous commands, without risking to block the Javascript VM.

Parameters :

Returns :

nothing.

wakeupmonitor→wakeUp()wakeupmonitor.wakeUp()wakeupmonitor.wakeUp()wakeupmonitor→wakeUp()wakeupmonitor→wakeUp()[wakeupmonitor wakeUp]wakeupmonitor.wakeUp()wakeupmonitor.wakeUp()wakeupmonitor.wakeUp()wakeupmonitor.wakeUp()wakeupmonitor.wakeUp()YWakeUpMonitor wakeUp

Forces a wake up.

11.6. WakeUpSchedule function interface

The WakeUpSchedule function implements a wake up condition. The wake up time is specified as a set of months and/or days and/or hours and/or minutes when the wake up should happen.

Global functions
yFindWakeUpSchedule(func)
Retrieves a wake up schedule for a given identifier.
yFirstWakeUpSchedule()
Starts the enumeration of wake up schedules currently accessible.
YWakeUpSchedule methods
wakeupschedule→describe()
Returns a short text that describes unambiguously the instance of the wake up schedule in the form TYPE(NAME)=SERIAL.FUNCTIONID.
wakeupschedule→get_advertisedValue()
Returns the current value of the wake up schedule (no more than 6 characters).
wakeupschedule→get_errorMessage()
Returns the error message of the latest error with the wake up schedule.
wakeupschedule→get_errorType()
Returns the numerical error code of the latest error with the wake up schedule.
wakeupschedule→get_friendlyName()
Returns a global identifier of the wake up schedule in the format MODULE_NAME.FUNCTION_NAME.
wakeupschedule→get_functionDescriptor()
Returns a unique identifier of type YFUN_DESCR corresponding to the function.
wakeupschedule→get_functionId()
Returns the hardware identifier of the wake up schedule, without reference to the module.
wakeupschedule→get_hardwareId()
Returns the unique hardware identifier of the wake up schedule in the form SERIAL.FUNCTIONID.
wakeupschedule→get_hours()
Returns the hours scheduled for wake up.
wakeupschedule→get_logicalName()
Returns the logical name of the wake up schedule.
wakeupschedule→get_minutes()
Returns all the minutes of each hour that are scheduled for wake up.
wakeupschedule→get_minutesA()
Returns the minutes in the 00-29 interval of each hour scheduled for wake up.
wakeupschedule→get_minutesB()
Returns the minutes in the 30-59 intervalof each hour scheduled for wake up.
wakeupschedule→get_module()
Gets the YModule object for the device on which the function is located.
wakeupschedule→get_module_async(callback, context)
Gets the YModule object for the device on which the function is located (asynchronous version).
wakeupschedule→get_monthDays()
Returns the days of the month scheduled for wake up.
wakeupschedule→get_months()
Returns the months scheduled for wake up.
wakeupschedule→get_nextOccurence()
Returns the date/time (seconds) of the next wake up occurence
wakeupschedule→get_userData()
Returns the value of the userData attribute, as previously stored using method set_userData.
wakeupschedule→get_weekDays()
Returns the days of the week scheduled for wake up.
wakeupschedule→isOnline()
Checks if the wake up schedule is currently reachable, without raising any error.
wakeupschedule→isOnline_async(callback, context)
Checks if the wake up schedule is currently reachable, without raising any error (asynchronous version).
wakeupschedule→load(msValidity)
Preloads the wake up schedule cache with a specified validity duration.
wakeupschedule→load_async(msValidity, callback, context)
Preloads the wake up schedule cache with a specified validity duration (asynchronous version).
wakeupschedule→nextWakeUpSchedule()
Continues the enumeration of wake up schedules started using yFirstWakeUpSchedule().
wakeupschedule→registerValueCallback(callback)
Registers the callback function that is invoked on every change of advertised value.
wakeupschedule→set_hours(newval)
Changes the hours when a wake up must take place.
wakeupschedule→set_logicalName(newval)
Changes the logical name of the wake up schedule.
wakeupschedule→set_minutes(bitmap)
Changes all the minutes where a wake up must take place.
wakeupschedule→set_minutesA(newval)
Changes the minutes in the 00-29 interval when a wake up must take place.
wakeupschedule→set_minutesB(newval)
Changes the minutes in the 30-59 interval when a wake up must take place.
wakeupschedule→set_monthDays(newval)
Changes the days of the month when a wake up must take place.
wakeupschedule→set_months(newval)
Changes the months when a wake up must take place.
wakeupschedule→set_userData(data)
Stores a user context provided as argument in the userData attribute of the function.
wakeupschedule→set_weekDays(newval)
Changes the days of the week when a wake up must take place.
wakeupschedule→wait_async(callback, context)
Waits for all pending asynchronous commands on the module to complete, and invoke the user-provided callback function.

YWakeUpSchedule.FindWakeUpSchedule()
yFindWakeUpSchedule()yFindWakeUpSchedule()YWakeUpSchedule.FindWakeUpSchedule()yFindWakeUpSchedule()yFindWakeUpSchedule()[YWakeUpSchedule FindWakeUpSchedule: ]yFindWakeUpSchedule()yFindWakeUpSchedule()YWakeUpSchedule.FindWakeUpSchedule()YWakeUpSchedule.FindWakeUpSchedule()YWakeUpSchedule.FindWakeUpSchedule()

Retrieves a wake up schedule for a given identifier.

The identifier can be specified using several formats:

• FunctionLogicalName
• ModuleSerialNumber.FunctionIdentifier
• ModuleSerialNumber.FunctionLogicalName
• ModuleLogicalName.FunctionIdentifier
• ModuleLogicalName.FunctionLogicalName

This function does not require that the wake up schedule is online at the time it is invoked. The returned object is nevertheless valid. Use the method YWakeUpSchedule.isOnline() to test if the wake up schedule is indeed online at a given time. In case of ambiguity when looking for a wake up schedule by logical name, no error is notified: the first instance found is returned. The search is performed first by hardware name, then by logical name.

Parameters :

Returns :

a YWakeUpSchedule object allowing you to drive the wake up schedule.

YWakeUpSchedule.FirstWakeUpSchedule()
yFirstWakeUpSchedule()yFirstWakeUpSchedule()YWakeUpSchedule.FirstWakeUpSchedule()yFirstWakeUpSchedule()yFirstWakeUpSchedule()[YWakeUpSchedule FirstWakeUpSchedule]yFirstWakeUpSchedule()yFirstWakeUpSchedule()YWakeUpSchedule.FirstWakeUpSchedule()YWakeUpSchedule.FirstWakeUpSchedule()YWakeUpSchedule.FirstWakeUpSchedule()

Starts the enumeration of wake up schedules currently accessible.

Use the method YWakeUpSchedule.nextWakeUpSchedule() to iterate on next wake up schedules.

Returns :

a pointer to a YWakeUpSchedule object, corresponding to the first wake up schedule currently online, or a null pointer if there are none.

wakeupschedule→describe()wakeupschedule.describe()wakeupschedule.describe()wakeupschedule→describe()wakeupschedule→describe()[wakeupschedule describe]wakeupschedule.describe()wakeupschedule.describe()wakeupschedule.describe()wakeupschedule.describe()wakeupschedule.describe()

Returns a short text that describes unambiguously the instance of the wake up schedule in the form TYPE(NAME)=SERIAL.FUNCTIONID.

More precisely, TYPE is the type of the function, NAME it the name used for the first access to the function, SERIAL is the serial number of the module if the module is connected or "unresolved", and FUNCTIONID is the hardware identifier of the function if the module is connected. For example, this method returns Relay(MyCustomName.relay1)=RELAYLO1-123456.relay1 if the module is already connected or Relay(BadCustomeName.relay1)=unresolved if the module has not yet been connected. This method does not trigger any USB or TCP transaction and can therefore be used in a debugger.

Returns :

a string that describes the wake up schedule (ex: Relay(MyCustomName.relay1)=RELAYLO1-123456.relay1)

wakeupschedule→get_advertisedValue()
wakeupschedule→advertisedValue()wakeupschedule.get_advertisedValue()wakeupschedule.get_advertisedValue()wakeupschedule→get_advertisedValue()wakeupschedule→get_advertisedValue()[wakeupschedule advertisedValue]wakeupschedule.get_advertisedValue()wakeupschedule.get_advertisedValue()wakeupschedule.get_advertisedValue()wakeupschedule.get_advertisedValue()wakeupschedule.get_advertisedValue()YWakeUpSchedule get_advertisedValue

Returns the current value of the wake up schedule (no more than 6 characters).

Returns :

a string corresponding to the current value of the wake up schedule (no more than 6 characters).

On failure, throws an exception or returns Y_ADVERTISEDVALUE_INVALID.

wakeupschedule→get_errorMessage()
wakeupschedule→errorMessage()wakeupschedule.get_errorMessage()wakeupschedule.get_errorMessage()wakeupschedule→get_errorMessage()wakeupschedule→get_errorMessage()[wakeupschedule errorMessage]wakeupschedule.get_errorMessage()wakeupschedule.get_errorMessage()wakeupschedule.get_errorMessage()wakeupschedule.get_errorMessage()wakeupschedule.get_errorMessage()

Returns the error message of the latest error with the wake up schedule.

This method is mostly useful when using the Yoctopuce library with exceptions disabled.

Returns :

a string corresponding to the latest error message that occured while using the wake up schedule object

wakeupschedule→get_errorType()
wakeupschedule→errorType()wakeupschedule.get_errorType()wakeupschedule.get_errorType()wakeupschedule→get_errorType()wakeupschedule→get_errorType()wakeupschedule.get_errorType()wakeupschedule.get_errorType()wakeupschedule.get_errorType()wakeupschedule.get_errorType()wakeupschedule.get_errorType()

Returns the numerical error code of the latest error with the wake up schedule.

This method is mostly useful when using the Yoctopuce library with exceptions disabled.

Returns :

a number corresponding to the code of the latest error that occured while using the wake up schedule object

wakeupschedule→get_friendlyName()
wakeupschedule→friendlyName()wakeupschedule.get_friendlyName()wakeupschedule.get_friendlyName()wakeupschedule→get_friendlyName()wakeupschedule→get_friendlyName()[wakeupschedule friendlyName]wakeupschedule.get_friendlyName()wakeupschedule.get_friendlyName()wakeupschedule.get_friendlyName()

Returns a global identifier of the wake up schedule in the format MODULE_NAME.FUNCTION_NAME.

The returned string uses the logical names of the module and of the wake up schedule if they are defined, otherwise the serial number of the module and the hardware identifier of the wake up schedule (for exemple: MyCustomName.relay1)

Returns :

a string that uniquely identifies the wake up schedule using logical names (ex: MyCustomName.relay1)

On failure, throws an exception or returns Y_FRIENDLYNAME_INVALID.

wakeupschedule→get_functionDescriptor()
wakeupschedule→functionDescriptor()wakeupschedule.get_functionDescriptor()wakeupschedule.get_functionDescriptor()wakeupschedule→get_functionDescriptor()wakeupschedule→get_functionDescriptor()[wakeupschedule functionDescriptor]wakeupschedule.get_functionDescriptor()wakeupschedule.get_functionDescriptor()wakeupschedule.get_functionDescriptor()wakeupschedule.get_functionDescriptor()wakeupschedule.get_functionDescriptor()

Returns a unique identifier of type YFUN_DESCR corresponding to the function.

This identifier can be used to test if two instances of YFunction reference the same physical function on the same physical device.

Returns :

an identifier of type YFUN_DESCR.

If the function has never been contacted, the returned value is Y_FUNCTIONDESCRIPTOR_INVALID.

wakeupschedule→get_functionId()
wakeupschedule→functionId()wakeupschedule.get_functionId()wakeupschedule.get_functionId()wakeupschedule→get_functionId()wakeupschedule→get_functionId()[wakeupschedule functionId]wakeupschedule.get_functionId()wakeupschedule.get_functionId()wakeupschedule.get_functionId()wakeupschedule.get_functionId()

Returns the hardware identifier of the wake up schedule, without reference to the module.

For example relay1

Returns :

a string that identifies the wake up schedule (ex: relay1)

On failure, throws an exception or returns Y_FUNCTIONID_INVALID.

wakeupschedule→get_hardwareId()
wakeupschedule→hardwareId()wakeupschedule.get_hardwareId()wakeupschedule.get_hardwareId()wakeupschedule→get_hardwareId()wakeupschedule→get_hardwareId()[wakeupschedule hardwareId]wakeupschedule.get_hardwareId()wakeupschedule.get_hardwareId()wakeupschedule.get_hardwareId()wakeupschedule.get_hardwareId()

Returns the unique hardware identifier of the wake up schedule in the form SERIAL.FUNCTIONID.

The unique hardware identifier is composed of the device serial number and of the hardware identifier of the wake up schedule (for example RELAYLO1-123456.relay1).

Returns :

a string that uniquely identifies the wake up schedule (ex: RELAYLO1-123456.relay1)

On failure, throws an exception or returns Y_HARDWAREID_INVALID.

wakeupschedule→get_hours()
wakeupschedule→hours()wakeupschedule.get_hours()wakeupschedule.get_hours()wakeupschedule→get_hours()wakeupschedule→get_hours()[wakeupschedule hours]wakeupschedule.get_hours()wakeupschedule.get_hours()wakeupschedule.get_hours()wakeupschedule.get_hours()wakeupschedule.get_hours()YWakeUpSchedule get_hours

Returns the hours scheduled for wake up.

Returns :

an integer corresponding to the hours scheduled for wake up

On failure, throws an exception or returns Y_HOURS_INVALID.

wakeupschedule→get_logicalName()
wakeupschedule→logicalName()wakeupschedule.get_logicalName()wakeupschedule.get_logicalName()wakeupschedule→get_logicalName()wakeupschedule→get_logicalName()[wakeupschedule logicalName]wakeupschedule.get_logicalName()wakeupschedule.get_logicalName()wakeupschedule.get_logicalName()wakeupschedule.get_logicalName()wakeupschedule.get_logicalName()YWakeUpSchedule get_logicalName

Returns the logical name of the wake up schedule.

Returns :

a string corresponding to the logical name of the wake up schedule.

On failure, throws an exception or returns Y_LOGICALNAME_INVALID.

wakeupschedule→get_minutes()
wakeupschedule→minutes()wakeupschedule.get_minutes()wakeupschedule.get_minutes()wakeupschedule→get_minutes()wakeupschedule→get_minutes()[wakeupschedule minutes]wakeupschedule.get_minutes()wakeupschedule.get_minutes()wakeupschedule.get_minutes()wakeupschedule.get_minutes()wakeupschedule.get_minutes()YWakeUpSchedule get_minutes

Returns all the minutes of each hour that are scheduled for wake up.

wakeupschedule→get_minutesA()
wakeupschedule→minutesA()wakeupschedule.get_minutesA()wakeupschedule.get_minutesA()wakeupschedule→get_minutesA()wakeupschedule→get_minutesA()[wakeupschedule minutesA]wakeupschedule.get_minutesA()wakeupschedule.get_minutesA()wakeupschedule.get_minutesA()wakeupschedule.get_minutesA()wakeupschedule.get_minutesA()YWakeUpSchedule get_minutesA

Returns the minutes in the 00-29 interval of each hour scheduled for wake up.

Returns :

an integer corresponding to the minutes in the 00-29 interval of each hour scheduled for wake up

On failure, throws an exception or returns Y_MINUTESA_INVALID.

wakeupschedule→get_minutesB()
wakeupschedule→minutesB()wakeupschedule.get_minutesB()wakeupschedule.get_minutesB()wakeupschedule→get_minutesB()wakeupschedule→get_minutesB()[wakeupschedule minutesB]wakeupschedule.get_minutesB()wakeupschedule.get_minutesB()wakeupschedule.get_minutesB()wakeupschedule.get_minutesB()wakeupschedule.get_minutesB()YWakeUpSchedule get_minutesB

Returns the minutes in the 30-59 intervalof each hour scheduled for wake up.

Returns :

an integer corresponding to the minutes in the 30-59 intervalof each hour scheduled for wake up

On failure, throws an exception or returns Y_MINUTESB_INVALID.

wakeupschedule→get_module()
wakeupschedule→module()wakeupschedule.get_module()wakeupschedule.get_module()wakeupschedule→get_module()wakeupschedule→get_module()[wakeupschedule module]wakeupschedule.get_module()wakeupschedule.get_module()wakeupschedule.get_module()wakeupschedule.get_module()wakeupschedule.get_module()

Gets the YModule object for the device on which the function is located.

If the function cannot be located on any module, the returned instance of YModule is not shown as on-line.

Returns :

an instance of YModule

wakeupschedule→get_module_async()
wakeupschedule→module_async()wakeupschedule.get_module_async()wakeupschedule.get_module_async()

Gets the YModule object for the device on which the function is located (asynchronous version).

If the function cannot be located on any module, the returned YModule object does not show as on-line.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking Firefox javascript VM that does not implement context switching during blocking I/O calls. See the documentation section on asynchronous Javascript calls for more details.

Parameters :

Returns :

nothing : the result is provided to the callback.

wakeupschedule→get_monthDays()
wakeupschedule→monthDays()wakeupschedule.get_monthDays()wakeupschedule.get_monthDays()wakeupschedule→get_monthDays()wakeupschedule→get_monthDays()[wakeupschedule monthDays]wakeupschedule.get_monthDays()wakeupschedule.get_monthDays()wakeupschedule.get_monthDays()wakeupschedule.get_monthDays()wakeupschedule.get_monthDays()YWakeUpSchedule get_monthDays

Returns the days of the month scheduled for wake up.

Returns :

an integer corresponding to the days of the month scheduled for wake up

On failure, throws an exception or returns Y_MONTHDAYS_INVALID.

wakeupschedule→get_months()
wakeupschedule→months()wakeupschedule.get_months()wakeupschedule.get_months()wakeupschedule→get_months()wakeupschedule→get_months()[wakeupschedule months]wakeupschedule.get_months()wakeupschedule.get_months()wakeupschedule.get_months()wakeupschedule.get_months()wakeupschedule.get_months()YWakeUpSchedule get_months

Returns the months scheduled for wake up.

Returns :

an integer corresponding to the months scheduled for wake up

On failure, throws an exception or returns Y_MONTHS_INVALID.

wakeupschedule→get_nextOccurence()
wakeupschedule→nextOccurence()wakeupschedule.get_nextOccurence()wakeupschedule.get_nextOccurence()wakeupschedule→get_nextOccurence()wakeupschedule→get_nextOccurence()[wakeupschedule nextOccurence]wakeupschedule.get_nextOccurence()wakeupschedule.get_nextOccurence()wakeupschedule.get_nextOccurence()wakeupschedule.get_nextOccurence()wakeupschedule.get_nextOccurence()

Returns the date/time (seconds) of the next wake up occurence

Returns :

an integer corresponding to the date/time (seconds) of the next wake up occurence

On failure, throws an exception or returns Y_NEXTOCCURENCE_INVALID.

wakeupschedule→get_userData()
wakeupschedule→userData()wakeupschedule.get_userData()wakeupschedule.get_userData()wakeupschedule→get_userData()wakeupschedule→get_userData()[wakeupschedule userData]wakeupschedule.get_userData()wakeupschedule.get_userData()wakeupschedule.get_userData()wakeupschedule.get_userData()wakeupschedule.get_userData()

Returns the value of the userData attribute, as previously stored using method set_userData.

This attribute is never touched directly by the API, and is at disposal of the caller to store a context.

Returns :

the object stored previously by the caller.

wakeupschedule→get_weekDays()
wakeupschedule→weekDays()wakeupschedule.get_weekDays()wakeupschedule.get_weekDays()wakeupschedule→get_weekDays()wakeupschedule→get_weekDays()[wakeupschedule weekDays]wakeupschedule.get_weekDays()wakeupschedule.get_weekDays()wakeupschedule.get_weekDays()wakeupschedule.get_weekDays()wakeupschedule.get_weekDays()YWakeUpSchedule get_weekDays

Returns the days of the week scheduled for wake up.

Returns :

an integer corresponding to the days of the week scheduled for wake up

On failure, throws an exception or returns Y_WEEKDAYS_INVALID.

wakeupschedule→isOnline()wakeupschedule.isOnline()wakeupschedule.isOnline()wakeupschedule→isOnline()wakeupschedule→isOnline()[wakeupschedule isOnline]wakeupschedule.isOnline()wakeupschedule.isOnline()wakeupschedule.isOnline()wakeupschedule.isOnline()wakeupschedule.isOnline()

Checks if the wake up schedule is currently reachable, without raising any error.

If there is a cached value for the wake up schedule in cache, that has not yet expired, the device is considered reachable. No exception is raised if there is an error while trying to contact the device hosting the wake up schedule.

Returns :

true if the wake up schedule can be reached, and false otherwise

wakeupschedule→isOnline_async()wakeupschedule.isOnline_async()wakeupschedule.isOnline_async()

Checks if the wake up schedule is currently reachable, without raising any error (asynchronous version).

If there is a cached value for the wake up schedule in cache, that has not yet expired, the device is considered reachable. No exception is raised if there is an error while trying to contact the device hosting the requested function.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking the Javascript virtual machine.

Parameters :

Returns :

nothing : the result is provided to the callback.

wakeupschedule→load()wakeupschedule.load()wakeupschedule.load()wakeupschedule→load()wakeupschedule→load()[wakeupschedule load: ]wakeupschedule.load()wakeupschedule.load()wakeupschedule.load()wakeupschedule.load()wakeupschedule.load()

Preloads the wake up schedule cache with a specified validity duration.

By default, whenever accessing a device, all function attributes are kept in cache for the standard duration (5 ms). This method can be used to temporarily mark the cache as valid for a longer period, in order to reduce network trafic for instance.

Parameters :

Returns :

YAPI_SUCCESS when the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupschedule→load_async()wakeupschedule.load_async()wakeupschedule.load_async()

Preloads the wake up schedule cache with a specified validity duration (asynchronous version).

By default, whenever accessing a device, all function attributes are kept in cache for the standard duration (5 ms). This method can be used to temporarily mark the cache as valid for a longer period, in order to reduce network trafic for instance.

This asynchronous version exists only in Javascript. It uses a callback instead of a return value in order to avoid blocking the Javascript virtual machine.

Parameters :

Returns :

nothing : the result is provided to the callback.

wakeupschedule→nextWakeUpSchedule()wakeupschedule.nextWakeUpSchedule()wakeupschedule.nextWakeUpSchedule()wakeupschedule→nextWakeUpSchedule()wakeupschedule→nextWakeUpSchedule()[wakeupschedule nextWakeUpSchedule]wakeupschedule.nextWakeUpSchedule()wakeupschedule.nextWakeUpSchedule()wakeupschedule.nextWakeUpSchedule()wakeupschedule.nextWakeUpSchedule()wakeupschedule.nextWakeUpSchedule()

Continues the enumeration of wake up schedules started using yFirstWakeUpSchedule().

Returns :

a pointer to a YWakeUpSchedule object, corresponding to a wake up schedule currently online, or a null pointer if there are no more wake up schedules to enumerate.

wakeupschedule→registerValueCallback()wakeupschedule.registerValueCallback()wakeupschedule.registerValueCallback()wakeupschedule→registerValueCallback()wakeupschedule→registerValueCallback()[wakeupschedule registerValueCallback: ]wakeupschedule.registerValueCallback()wakeupschedule.registerValueCallback()wakeupschedule.registerValueCallback()wakeupschedule.registerValueCallback()wakeupschedule.registerValueCallback()

Registers the callback function that is invoked on every change of advertised value.

The callback is invoked only during the execution of ySleep or yHandleEvents. This provides control over the time when the callback is triggered. For good responsiveness, remember to call one of these two functions periodically. To unregister a callback, pass a null pointer as argument.

Parameters :

wakeupschedule→set_hours()
wakeupschedule→setHours()wakeupschedule.set_hours()wakeupschedule.set_hours()wakeupschedule→set_hours()wakeupschedule→set_hours()[wakeupschedule setHours: ]wakeupschedule.set_hours()wakeupschedule.set_hours()wakeupschedule.set_hours()wakeupschedule.set_hours()wakeupschedule.set_hours()YWakeUpSchedule set_hours

Changes the hours when a wake up must take place.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupschedule→set_logicalName()
wakeupschedule→setLogicalName()wakeupschedule.set_logicalName()wakeupschedule.set_logicalName()wakeupschedule→set_logicalName()wakeupschedule→set_logicalName()[wakeupschedule setLogicalName: ]wakeupschedule.set_logicalName()wakeupschedule.set_logicalName()wakeupschedule.set_logicalName()wakeupschedule.set_logicalName()wakeupschedule.set_logicalName()YWakeUpSchedule set_logicalName

Changes the logical name of the wake up schedule.

You can use yCheckLogicalName() prior to this call to make sure that your parameter is valid. Remember to call the saveToFlash() method of the module if the modification must be kept.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupschedule→set_minutes()
wakeupschedule→setMinutes()wakeupschedule.set_minutes()wakeupschedule.set_minutes()wakeupschedule→set_minutes()wakeupschedule→set_minutes()[wakeupschedule setMinutes: ]wakeupschedule.set_minutes()wakeupschedule.set_minutes()wakeupschedule.set_minutes()wakeupschedule.set_minutes()wakeupschedule.set_minutes()YWakeUpSchedule set_minutes

Changes all the minutes where a wake up must take place.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupschedule→set_minutesA()
wakeupschedule→setMinutesA()wakeupschedule.set_minutesA()wakeupschedule.set_minutesA()wakeupschedule→set_minutesA()wakeupschedule→set_minutesA()[wakeupschedule setMinutesA: ]wakeupschedule.set_minutesA()wakeupschedule.set_minutesA()wakeupschedule.set_minutesA()wakeupschedule.set_minutesA()wakeupschedule.set_minutesA()YWakeUpSchedule set_minutesA

Changes the minutes in the 00-29 interval when a wake up must take place.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupschedule→set_minutesB()
wakeupschedule→setMinutesB()wakeupschedule.set_minutesB()wakeupschedule.set_minutesB()wakeupschedule→set_minutesB()wakeupschedule→set_minutesB()[wakeupschedule setMinutesB: ]wakeupschedule.set_minutesB()wakeupschedule.set_minutesB()wakeupschedule.set_minutesB()wakeupschedule.set_minutesB()wakeupschedule.set_minutesB()YWakeUpSchedule set_minutesB

Changes the minutes in the 30-59 interval when a wake up must take place.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupschedule→set_monthDays()
wakeupschedule→setMonthDays()wakeupschedule.set_monthDays()wakeupschedule.set_monthDays()wakeupschedule→set_monthDays()wakeupschedule→set_monthDays()[wakeupschedule setMonthDays: ]wakeupschedule.set_monthDays()wakeupschedule.set_monthDays()wakeupschedule.set_monthDays()wakeupschedule.set_monthDays()wakeupschedule.set_monthDays()YWakeUpSchedule set_monthDays

Changes the days of the month when a wake up must take place.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupschedule→set_months()
wakeupschedule→setMonths()wakeupschedule.set_months()wakeupschedule.set_months()wakeupschedule→set_months()wakeupschedule→set_months()[wakeupschedule setMonths: ]wakeupschedule.set_months()wakeupschedule.set_months()wakeupschedule.set_months()wakeupschedule.set_months()wakeupschedule.set_months()YWakeUpSchedule set_months

Changes the months when a wake up must take place.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupschedule→set_userData()
wakeupschedule→setUserData()wakeupschedule.set_userData()wakeupschedule.set_userData()wakeupschedule→set_userData()wakeupschedule→set_userData()[wakeupschedule setUserData: ]wakeupschedule.set_userData()wakeupschedule.set_userData()wakeupschedule.set_userData()wakeupschedule.set_userData()wakeupschedule.set_userData()

Stores a user context provided as argument in the userData attribute of the function.

This attribute is never touched by the API, and is at disposal of the caller to store a context.

Parameters :

wakeupschedule→set_weekDays()
wakeupschedule→setWeekDays()wakeupschedule.set_weekDays()wakeupschedule.set_weekDays()wakeupschedule→set_weekDays()wakeupschedule→set_weekDays()[wakeupschedule setWeekDays: ]wakeupschedule.set_weekDays()wakeupschedule.set_weekDays()wakeupschedule.set_weekDays()wakeupschedule.set_weekDays()wakeupschedule.set_weekDays()YWakeUpSchedule set_weekDays

Changes the days of the week when a wake up must take place.

Parameters :

Returns :

YAPI_SUCCESS if the call succeeds.

On failure, throws an exception or returns a negative error code.

wakeupschedule→wait_async()wakeupschedule.wait_async()wakeupschedule.wait_async()

Waits for all pending asynchronous commands on the module to complete, and invoke the user-provided callback function.

The callback function can therefore freely issue synchronous or asynchronous commands, without risking to block the Javascript VM.

Parameters :

Returns :

nothing.

12. Characteristics

You can find below a summary of the main technical characteristics of your YoctoHub-Wireless module.

Thickness	8.1 mm
Width	58 mm
Length	60 mm
Weight	30.1 g
USB connector	micro-B
Channels	3 ports
Max Current (continuous)	2 A
USB consumption	110 mA
Supported Operating Systems	Windows, Linux (Intel + ARM), Mac OS X, Android
Network connection	802.11b
Drivers	no driver needed
API / SDK / Libraries (USB+TCP)	C++, Objective-C, C#, VB .NET, Delphi, Python, Java/Android
API / SDK / Libraries (TCP only)	Javascript, Node.js, PHP, Java
RoHS	yes
USB Vendor ID	0x24E0
USB Device ID	0x0023
Suggested enclosure	YoctoBox-HubWlan-Transp

13. Index

A
adhocNetwork
API
C
callbackLogin
D
describe
download
download_async
F
FindFiles
FindHubPort
FindNetwork
FindWakeUpMonitor
FindWakeUpSchedule
FindWireless
FirstFiles
FirstHubPort
FirstNetwork
FirstWakeUpMonitor
FirstWakeUpSchedule
FirstWireless
format_fs
G
get_adminPassword
get_advertisedValue
get_baudRate
get_callbackCredentials
get_callbackEncoding
get_callbackMaxDelay
get_callbackMethod
get_callbackMinDelay
get_callbackUrl
get_channel
get_detectedWlans
get_discoverable
get_enabled
get_errorMessage
get_errorType
get_filesCount
get_freeSpace
get_friendlyName
get_functionDescriptor
get_functionId
get_hardwareId
get_hours
get_ipAddress
get_linkQuality
get_list
get_logicalName
get_macAddress
get_message
get_minutes
get_minutesA
get_minutesB
get_module
get_module_async
get_monthDays
get_months
get_nextOccurence
get_nextWakeUp
get_poeCurrent
get_portState
get_powerDuration
get_primaryDNS
get_readiness
get_router
get_secondaryDNS
get_security
get_sleepCountdown
get_ssid
get_subnetMask
get_userData
get_userPassword
get_wakeUpReason
get_wakeUpState
get_weekDays
get_wwwWatchdogDelay
I
isOnline
isOnline_async
J
joinNetwork
L
load
load_async
N
nextFiles
nextHubPort
nextNetwork
nextWakeUpMonitor
nextWakeUpSchedule
nextWireless
P
ping
R
registerValueCallback
remove
resetSleepCountDown
S
set_adminPassword
set_callbackCredentials
set_callbackEncoding
set_callbackMaxDelay
set_callbackMethod
set_callbackMinDelay
set_callbackUrl
set_discoverable
set_enabled
set_hours
set_logicalName
set_minutes
set_minutesA
set_minutesB
set_monthDays
set_months
set_nextWakeUp
set_powerDuration
set_primaryDNS
set_secondaryDNS
set_sleepCountdown
set_userData
set_userPassword
set_weekDays
set_wwwWatchdogDelay
sleep
sleepFor
sleepUntil
T
techspec
U
upload
useDHCP
useStaticIP
W
wait_async
wakeUp
Y
YFiles
YHubPort
YNetwork
YWakeUpMonitor
YWakeUpSchedule
YWireless

---

1. http://www.yoctopuce.com/EN/virtualhub.php ←
2. support@yoctopuce.com ←
3. short-short-short long-long-long short-short-short ←
4. support@yoctopuce.com ←
5. The Yoctopuce Micro-USB-Hub is a standard USB hub and does not work either. ←
6. www.yoctopuce.com/FR/products/yoctohub-shield ←
7. http://www.yoctopuce.com/EN/virtualhub.php ←
8. Except Opera ←
9. http://www.yoctopuce.com/EN/libraries.php ←
10. http://www.yoctopuce.com/EN/products/accessories-and-connectors/fix-2-5mm ←
11. http://www.yoctopuce.com/EN/products/accessories-and-connectors/board2board-127 ←
12. The YoctoHub-Wireless interface is regularly tested with Internet Explorer 6+, Firefox 3.5+, Chrome, and Safari. It does not work with Opera. ←
13. The YoctoHub-Wireless does not need to be more recent than the module you want to test and configure: all the elements specific to the module interfaces are kept in the module ROM, and not in the YoctoHub-Wireless. ←
14. Never trust people telling you that their software does not have bugs :-) ←
15. www.yoctopuce.com ←
16. On the condition that the interface could access the Yoctopuce web site. ←
17. http://www.yoctopuce.com/EN/virtualhub.php ←
18. Advertised values are the ones you can see on the YoctoHub-Wireless main interface when you click on the show functions button. ←
19. www.xively.com ←
20. http://www.yoctopuce.com/EN/article/connect-your-sensors-to-the-cloud ←
21. www.thingspeak.com ←
22. http://www.yoctopuce.com/EN/article/cosm-alternatives-to-record-sensor-measurements ←