AltSoftSerial uses these pins on the Arduino UNO, according to AltSoftSerial_Boards.h (included with the AIS NB-IoT libs):
My BLE module sketch (taken from an ArduinoBlue example sketch) uses pins:
So, not yet more more than an Arduino noob, my first guess is that I should move the Arduino UNO pins for the HM-10 BLE module to some supported SoftwareSerial pins which are different than the AltSoftSerial pins (8,9) above.
Seems the conflict is pin 8 being used by both SoftwareSerial (used in the BLE code) and AltSoftSerial (used in the NB-IoT code).
Will try different pins tomorrow and see how far that get me.
I just moved away from a T3 line back to a dial up I just wanted to know would a P200 with 64meg and a 4 gig hard drive be ok for a linux server for an additional 3 pcs all running win98. I will be dialing into an isp using a 56k v90 modem.
Any support or help will be great. (3 Replies)
Hello all
this is general question , if i have web server installed in my local pc and i have client that connecting to that web server
can i force it always to go via the internet network ?
the reason im asking is .. that im noticed when i close my internet connection i still can connect to my... (2 Replies)
hi i have linux server connected to internet through a switch/router. i have opened a port on the router and i am able to connect to the server if iptables is off. but when it is on i cant.
i want to create a rule in iptables so that it accepts packets coming from a particular datacard. it... (7 Replies)
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)
My favorite projects are always related to the "latest" tech in command and control, networking and network communications. This Elecrow GSM/GPRS/EDGE SIM5360E 3G Shield seems to be the "latest and the greatest" as far as 3G and GPS, as far as I can see so far, but I has it drawbacks for sure.... (6 Replies)
Today I received my NB-IoT Arduino Shield for AIS (Thailand). Here is a "pinout" photo of the shield.
My shield looks just like the one above, for the most part. I'll post another photo of the actual device later.
When I received the shield in the mail, I went immediately to a local... (8 Replies)
Normally I have very good experiences buying from AliExpress, but in this case with Elecrow, I'm disappointed.
After confirming with Elecrow on AliExpress that their Elecrow GSM/GPRS/EDGE SIM5360E 3G Shield for Arduino would work with 3G SIM cards in Thailand, I purchased one. My plan was to... (1 Reply)
Here is a sketch to do basic testing for the Arduino UNO and the MLT-BT04.
This BLE module works with IOS (iPhone) and I'll add some details on my IOS testing with an iPhone in a follow-up post.
For now, here is the basic BLE (HM-10) sketch for the Arduino UNO:
/*
Arduino test-code... (7 Replies)
With a little bit of work, was able to build a nice "Wuhan Coronavirus Status" app using MQTT and the IoT-OnOff app. More on this technique here:
ESP32 (ESP-WROOM-32) as an MQTT Client Subscribed to Linux Server Load Average Messages
The result turned out nice, I think. I like the look and... (10 Replies)
Normally I'm not into kits, but I thought my wife would enjoy this one since she is a big fan of robots and droids on StarWars!
We are done with the basic mechanical assembly and starting on the electronics assembly today.
The robot's "brain" consists of three levels. The Arduino board, on... (5 Replies)
Discussion started by: Neo
5 Replies
LEARN ABOUT NETBSD
gpio
GPIO(4) BSD Kernel Interfaces Manual GPIO(4)NAME
gpio -- General Purpose Input/Output
SYNOPSIS
gpio* at elansc?
gpio* at epgpio?
gpio* at gcscpcib?
gpio* at gpiosim?
gpio* at gscpcib?
gpio* at ichlpcib?
gpio* at nsclpcsio?
gpio* at ppbus?
#include <sys/types.h>
#include <sys/gpio.h>
#include <sys/ioctl.h>
DESCRIPTION
The gpio device attaches to the GPIO controller and provides a uniform programming interface to its pins.
Each GPIO controller with an attached gpio device has an associated device file under the /dev directory, e.g. /dev/gpio0. Access from user-
land is performed through ioctl(2) calls on these devices.
Whether the layout of the GPIO device can be configured is subject to authorization by the kauth(9) framework.
If for example secmodel_securelevel(9) is active, the layout of the GPIO device is defined at a securelevel less than 1, i.e. typically dur-
ing system boot, and cannot be changed later. GPIO pins can be configured and given a symbolic name and device drivers that use GPIO pins
can be attached to the gpio device at a securelevel less than 1. All other pins will not be accessible once the runlevel has been raised.
IOCTL INTERFACE
The following structures and constants are defined in the <sys/gpio.h> header file:
GPIOINFO (struct gpio_info)
Returns information about the GPIO controller in the gpio_info structure:
struct gpio_info {
int gpio_npins; /* total number of pins available */
};
GPIOREAD (struct gpio_req)
Returns the input pin value in the gpio_pin_op structure:
#define GPIOMAXNAME 64
struct gpio_req {
char gp_name[GPIOMAXNAME]; /* pin name */
int gp_pin; /* pin number */
int gp_value; /* value */
};
The gp_name or gp_pin field must be set before calling.
GPIOWRITE (struct gpio_req)
Writes the output value to the pin. The value set in the gp_value field must be either GPIO_PIN_LOW (logical 0) or GPIO_PIN_HIGH (log-
ical 1). On return, the gp_value field contains the old pin state.
GPIOTOGGLE (struct gpio_req)
Toggles the pin output value, i.e. changes it to the opposite. gp_value field is ignored and on return contains the old pin state.
GPIOSET (struct gpio_set)
Changes pin configuration flags with the new ones provided in the gpio_set structure:
#define GPIOMAXNAME 64
struct gpio_set {
char gp_name[GPIOMAXNAME]; /* pin name */
int gp_pin; /* pin number */
int gp_caps; /* pin capabilities (ro) */
int gp_flags; /* pin configuration flags */
char gp_name2[GPIOMAXNAME]; /* new name */
};
The gp_flags field is a combination of the following flags:
GPIO_PIN_INPUT input direction
GPIO_PIN_OUTPUT output direction
GPIO_PIN_INOUT bi-directional
GPIO_PIN_OPENDRAIN open-drain output
GPIO_PIN_PUSHPULL push-pull output
GPIO_PIN_TRISTATE output disabled
GPIO_PIN_PULLUP internal pull-up enabled
GPIO_PIN_PULLDOWN internal pull-down enabled
GPIO_PIN_INVIN invert input
GPIO_PIN_INVOUT invert output
GPIO_PIN_PULSATE pulsate output
Note that the GPIO controller may not support all of these flags. On return the gp_caps field contains flags that are supported. If
no flags are specified, the pin configuration stays unchanged.
Only GPIO pins that have been set using GPIOSET will be accessible at securelevels greater than 0.
GPIOUNSET (struct gpio_set)
Unset the specified pin, i.e. clear its name and make it unaccessible at securelevels greater than 0.
GPIOATTACH (struct gpio_attach)
Attach the device described in the gpio_attach structure on this gpio device.
struct gpio_attach {
char ga_dvname[16]; /* device name */
int ga_offset; /* pin number */
uint32_t ga_mask; /* binary mask */
uint32_t ga_flags; /* driver dependent */
};
The drvctl(8) command can be used to detach a device from a gpio pin.
FILES
/dev/gpiou GPIO device unit u file.
SEE ALSO ioctl(2), drvctl(8), gpioctl(8)HISTORY
The gpio device first appeared in OpenBSD 3.6 and NetBSD 4.0.
AUTHORS
The gpio driver was written by Alexander Yurchenko <grange@openbsd.org>. gpio and was ported to NetBSD by Jared D. McNeill
<jmcneill@NetBSD.org>. Runtime device attachment was added by Marc Balmer <marc@msys.ch>.
BUGS
Event capabilities are not supported.
BSD November 13, 2011 BSD