 |
FAQ
Frequently Asked Questions HT32SX
|
|
FAQ
Frequently Asked Questions HT32SX
|
• How do I register a new user on the SigFox Backed?
• How do I register a new device on the SigFox Backed?
• How or where can I check if my device is sending the massages correctly?
• How should I set up my new device to operate in my current region?
• How many messagens can I send daily?
• How long should I wait between sending two messages?
• What is the Keil uVision set up for debug purpose?
• How to open the examples using STM32CubeIDE?
• What or which peripherals can I change using STM32CubeMX/CubeIDE graphical interface?
• Error: Invalid message sequence from Device #XXXXX: expected X, actual X
Answer:
• If you do not have an account and just received an Evaluation Board:
1 - Go to SigFox Buy and select your country.
2 - If you do not know the device ID and PAC, open a serial terminal and run one of our GitHub examples. That information should be shown as the image below:
3 - Fill all the spaces, follow the steps and an account shall be created with your device registered on it.
• On the other hand, if you already have an account:
1 - Go to SigFox Backend, access your account and click User:
2 - Click New, fill all spaces, select the group which this new user will participate and select the permissions. The following permissions are recommended for admin access:
Answer: If you already have an account, check the following steps below, otherwise check the Account Registration topic.
1 - Open the SigFox Backend website.
2 - Click Device:
3 - Then click New to register a new device:
3 - Select the group which your device will be part of:
4 - Fill the underlined fields with your device ID & PAC and choose a name for this new device.
5 - Finally, click Ok and your device will be registered.
Answer: If you do not have an account on SigFox Backend or haven't registered your device yet, check the Account Registration topic or the Device Registration topic. If It's already done, check the following steps:
1 - Open SigFox Backend website, where all your messages will be shown.
2 - Click Device:
3 - Look for your device ID and click on it:
4 - Then click Messages and all messages received by that device shall be shown:
Answer:
1 - Open the Generic_Push_Button example, provided on our GitHub repository.
2 - Open the main.c file and search for the main function.
3 - Change the configRegion parameter and select the region where you are currently working on:
Answer: The SigFox Network allows 140 per day. It's recommended to use the SigFox Dongle for messages debbuging purposes (when the user needs to send a lot of messages) and the Backend only to confirm your tests;
Answer: The SigFox Network recommends to respect a duty cycle of 1% between messages. This means that it is necessary to respect a 10 minutes delay between messages (this is also a rule usually required by your local Regulatory Agency responsible for radio communications), otherwise the cloud might reject the messages and generate that event alert.
1 - Open Keil uVision and go to Project -> Options for target -> Device and select STM32LO52T8Yx:
2 - Go to Debug and select ST-Link Debugger option:
2 - Click Settings and change the Connect option to connect with Pre-reset.
3 - Click Flash Download tab and check if the HT32SX MCU (STM32LO) is already listed.
Otherwise click Add and select the right MCU:
Answer:
1 - Install STM32CubeIDE.
2 - Clone the MASTER BRANCH of our GitHub Repository.
3 - Open the directory where you cloned the repository, click firmware_applications and select an example which you want to use in your project.
4 - Open the STM32CubeIDE directory and double-click the cproject file:
5 - To open the STM32CubeMX graphical interface, double-click the ioc file:
Answer: Looking at STM32CubeMX/CubeIDE .ioc file, you will se which paripherals are being used. You can change ONLY the UART set up, selecting another one or even deleting from your project, and the GPIO which the Evaluation Board button (PB0) is using (push button examples). ANY OTHER CHANGE will efect the chip functionality.
Answer: This is coused by the message counter. Both sides must to have the same counter, otherwise the message won't be received on SigFox Backed.
A simple way to fix it, is disengaging the sequence number.
1 - Open the SigFox Backend website..
2 - Click Device tab:
3 - Look for your device ID and click on it:
4 - Then click Disengage sequence number and the counter will be reseted: