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 DEBIAN
dlys
DLYS(5) File Formats Manual DLYS(5)NAME
dlys - format of .dlys files read by the SCALD simulator and timing verifier
DESCRIPTION
The SCALD simulator and timing verifier can accept information about the actual delays of wires in a circuit. This delay information is
described in a .dlys file, which consists of a sequence of records, one for each electrical net. Each record begins with the signal name
for the net (note that this is the SCALD signal name, i.e, the name given by the user to the entire net, and not usually the name of one of
the pins in the net), followed by an =, then a comma-separated list of the terminals in the net and their associated delay, with the list
terminated by a semicolon. The end of the file is marked with a second semicolon.
The elements of the comma-separated list for each net take the form
location [min:max]
where location is the full hierarchical SCALD name of the physical pin to which the delay is computed, and min and max are the best-case
and worst-case wire delay in nanoseconds (both are floating-point numbers). The assumption is that only a single driver exists per net, so
all delays are computed from this driver. If a net has multiple drivers, then the interpretation of delays is up to the program reading
this file (e.g, min delays are taken from the fastest driver, max from the slowest).
Here is an example .dlys file:
(APS )ALU STATUS BITS I1<0> =
(APS MR 3V6 R1 1P )IN#63[ 0.3 : 0.4 ],
(APS APS 4RI RFC RF )OUT[ 0.5 : 0.7 ];
(APS )ALU STATUS BITS I1<1> =
(APS APS 4ALUD DCD )AN#12[ 1.4 : 1.6 ],
(APS APS 4ALUD DCD )AN#8[ 1.1 : 1.3 ],
(APS APS 4ALUD DCD )AN#9[ 1.1 : 1.3 ],
(APS APS 4ALUD DCD )AN#10[ 1.1 : 1.3 ],
(APS APS 4ALUD DCD )AN#11[ 1.1 : 1.3 ],
(APS MR 3V2 R1 1P )#23[ 0.6 : 0.8 ],
(APS MR 3V6 R1 1P )#62[ 0.3 : 0.4 ],
(APS APS 4ALUD DCD )[ 0.4 : 0.6 ],
(APS APS 4ALUD DCD )#1[ 0.4 : 0.6 ],
(APS APS 4ALUD DCD )#2[ 0.4 : 0.6 ],
(APS APS 4ALUD DCD )#3[ 0.4 : 0.6 ],
(APS APS 4ALUD DCD )#4[ 0.7 : 0.8 ],
(APS APS 4ALUD DCD )#5[ 0.7 : 0.8 ];
;
Although it is not good practice, it is possible to omit the actual pin names from the location names and only give the path to the part;
the example above shows several cases where the final pin name is missing. Since the timing verifier and simulator have the original SCALD
netlist available, they are usually able to use the signal name to determine the net, and then use the part's path to identify which pin of
the net is meant. This is accurate when a net connects to at most one pin per part; if it connects to more than one pin per part then
there is ambiguity over which pin is meant. Usually, though, this ambiguity results in only a small inaccuracy, since the delay to differ-
ent pins on the same part is usually similar. Also, if delay is capacitive, the delay to all pins in a net will be the same anyway, so
there is no inaccuracy.
SEE ALSO ext2dlys(1), ext(5), sim(5)BUGS
There should be some way to specify which pins are drivers and which are receivers in a net.
The ability to omit pin names is dangerous; although it usually works it can introduce large inaccuracies when the parts are large compared
to the sizes of the wires used to connect them, as might be the case on a silicon PCB.
DLYS(5)