Sponsored Content
Top Forums Programming Basic Arduino UNO Bluetooth Testing with the BLE 4.0 (CC2541, MLT-BT04 IC) Post 303043348 by Neo on Saturday 25th of January 2020 09:25:19 AM
Old 01-25-2020
Here is the chip.... as I find these kind of details matter and are often omitted on these kinds of Internet tutorials and discussions. I will replace this photo (taken quickly with my iPhone) with a screen shot from my computer when I find the USB cable to my little microscope.

In fact, the way I got this test to work (finding a starting point sketch) was to use my microscope to read the model number on the chip: the CC2541

A number of times recently, I received some modules with the model number of the chip "burned off" with a laser, which is really annoying.

Basic Arduino UNO Bluetooth Testing with the BLE 4.0 (CC2541, MLT-BT04 IC)-img_9039jpg


Update: Here is the same chip shot using the USB interface to my Mac Pro :

Basic Arduino UNO Bluetooth Testing with the BLE 4.0 (CC2541, MLT-BT04 IC)-s20200126_001jpg


Both "chip shots" were taken though the plastic wrapper around the BLE module... that is why the image is a bit blurry)
 

7 More Discussions You Might Find Interesting

1. OS X (Apple)

Semi-Automatic Arduino Detection.

I am working on a semi-auto detection idea for Arduino for the Scope project. It does require a little user intervention but minimal. It works by just responding to two on screen prompts to unplug and plug Arduino into a USB port. There are two versions and both work perfectly well and give... (3 Replies)
Discussion started by: wisecracker
3 Replies

2. Programming

Very Basic Arduino Uno Board Testing

A very simple Arduino board test... LOL Here is some very easy code to test a cheap Arduino board I just got from China via Aliexpress. I am still waiting on a about 30 more orders from Aliexpress for more Arduino stuff. This was the first order which made it here. /* Arduino test-code... (18 Replies)
Discussion started by: Neo
18 Replies

3. Programming

Arduino-cli - Uploading to Unknown Chinese Arduino Boards using the Arduino Command Line Interface

In my further exploration of Arduino, today I decided to install the arduino-cli on my mac today. https://github.com/arduino/arduino-cli I followed the instructions for macOS but when I got to this part: arduino-cli board list I got the dreaded "Unknown" Fully Qualified Board Name... (1 Reply)
Discussion started by: Neo
1 Replies

4. Programming

More Arduino Stuff...

HI all... (Apologies for any typos.) To add to Neo's Arduino subject matter I have decided to upload this in ".zip" format. Ignore "*.info" files these are AMIGA icons only and also the "HAM" drawer as these are photos in ancient AMIGA HAM modes. I have noticed that there are current... (6 Replies)
Discussion started by: wisecracker
6 Replies

5. Programming

Chinese Arduino UNO Clones - The Wavgat versus the generic UNO R3 Clone - The Winner Is?

Waiting for more fun Ardunio parts from AliExpress, I decided to test two cheap Chinese Arduino UNO clones. The Arduino UNO R3 (CH340G) MEGA328P The Wavgat UNO R3 (CH340G) MEGA328P Both of these Chinese Ardunio clones sell for about $3 USD, delivered to your door. The bottom line is... (0 Replies)
Discussion started by: Neo
0 Replies

6. Programming

Arduino UNIX Time - Syncing Computer UNIX Time to Arduino Time with Python

Just finished a quick Python script to send the current unix time over to the Arduino from macOS, so in the absence of GPS or some other way to get the unix timestamp (epoch time) to the Arduino, I can get my macOS and Arduino UNO synced to within a second. Normally, when the Arduino starts... (9 Replies)
Discussion started by: Neo
9 Replies

7. Programming

Arduino Project: iPhone to HM-10 BLE to NB-IoT Shield to NB-IoT Network to Internet to Linux Server

This post describes a "work in progress" project I started today. Here is the High Level Overview: Currently, this project sits on my desk as an Arduino UNO (on the bottom), an NB-IoT Shield (sandwiched in the middle), a Sensor Shield (on top) with a HM-10 BLE Module (in the little... (13 Replies)
Discussion started by: Neo
13 Replies
libsensors(3)						     Linux Programmer's Manual						     libsensors(3)

NAME
libsensors - publically accessible functions provided by the sensors library SYNOPSIS
#include <sensors.h> int sensors_init(FILE *input); void sensors_cleanup(void); int sensors_parse_chip_name(const char *orig_name, sensors_chip_name *res); int sensors_match_chip(sensors_chip_name chip1, sensors_chip_name chip2); int sensors_chip_name_has_wildcards(sensors_chip_name chip); const char *sensors_get_adapter_name(int bus_nr); const char *sensors_get_algorithm_name(int bus_nr); int sensors_get_label(sensors_chip_name name, int feature, char **result); int sensors_get_feature(sensors_chip_name name, int feature, double *result); int sensors_set_feature(sensors_chip_name name, int feature, double value); int sensors_do_chip_sets(sensors_chip_name name); extern int sensors_do_all_sets(void); const sensors_chip_name *sensors_get_detected_chips(int *nr); const sensors_feature_data *sensors_get_all_features (sensors_chip_name name, int *nr1,int *nr2); DESCRIPTION
int sensors_init(FILE *input); (Re)load the configuration file and the detected chips list. If this returns a value unequal to zero, you are in trouble; you can not assume anything will be initialized properly. void sensors_cleanup(void); Strictly optional clean-up function: You can't access anything after this, until the next sensors_init() call! int sensors_parse_chip_name(const char *orig_name, sensors_chip_name *res); Parse a chip name to the internal representation. Return 0 on succes, <0 on error. int sensors_match_chip(sensors_chip_name chip1, sensors_chip_name chip2); Compare two chips name descriptions, to see whether they could match. Return 0 if it does not match, return 1 if it does match. int sensors_chip_name_has_wildcards (sensors_chip_name chip); Check whether the chip name is an 'absolute' name, which can only match one chip, or whether it has wildcards. Returns 0 if it is absolute, 1 if there are wildcards. const char *sensors_get_adapter_name(int bus_nr); const char *sensors_get_algorithm_name(int bus_nr); These functions return the adapter and algorithm names of a bus number, as used within the sensors_chip_name structure. If it could not be found, it returns NULL int sensors_get_label(sensors_chip_name name, int feature, char **result); Look up the label which belongs to this chip. Note that chip should not contain wildcard values! *result is newly allocated (free it your- self). This function will return 0 on success, and <0 on failure. int sensors_get_feature(sensors_chip_name name, int feature, double *result); Read the value of a feature of a certain chip. Note that chip should not contain wildcard values! This function will return 0 on success, and <0 on failure. int sensors_set_feature(sensors_chip_name name, int feature, double value); Set the value of a feature of a certain chip. Note that chip should not contain wildcard values! This function will return 0 on success, and <0 on failure. int sensors_do_chip_sets(sensors_chip_name name); Execute all set statements for this particular chip. The chip may contain wildcards! This function will return 0 on success, and <0 on failure. int sensors_do_all_sets(void); Execute all set statements for all detected chips. This is the same as calling sensors_do_chip_sets with an all wildcards chip name const sensors_chip_name *sensors_get_detected_chips (int *nr); This function returns all detected chips, one by one. To start at the beginning of the list, use 0 for nr; NULL is returned if we are at the end of the list. Do not try to change these chip names, as they point to internal structures! Do not use nr for anything else. This structure is used when you want to get all features of a specific chip. typedef struct sensors_feature_data { int number; const char *name; int mapping; int unused; int mode; } sensors_feature_data; The field sensors_feature_data can be one of: SENSORS_MODE_NO_RW, SENSORS_MODE_R, SENSORS_MODE_W, SENSORS_MODE_RW or SENSORS_NO_MAPPING. const sensors_feature_data *sensors_get_all_features (sensors_chip_name name, int *nr1,int *nr2); This returns all features of a specific chip. They are returned in bunches: everything with the same mapping is returned just after each other, with the master feature in front (that feature does not map to itself, but has SENSORS_NO_MAPPING as mapping field). nr1 and nr2 are two internally used variables. Set both to zero to start again at the begin of the list. If no more features are found NULL is returned. Do not try to change the returned structure; you will corrupt internal data structures. CONFORMING TO
lm_sensors-2.x SEE ALSO
sensors.conf(5) December 30, 1998 libsensors(3)
All times are GMT -4. The time now is 01:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy