HX19 Ultrasonic RF
PositioningHexamite
FEATURES
Device to device range up to
16 meters
High precision 1mm typically
Low RF power device to device
relay networking
Doppler Resolution 0.2m/s
RFID (Radio Frequency Id) no
limit on unique identities
Combination mode USID and RFID
Battery capable operation for
the entire system
USB and standard RS232C Serial
Interface for PC
Only three components serve
most positioning contingencies
Applications
cover both tracking and guidance (operation reversible)
Wireless
HX19 Introduction
The
HX19; is designed to satisfy most local positioning needs, with very
high precision using ultrasound. Both ultrasonic receivers, and
transmitters; are linked to the controlling computer, through a
2.4Ghz 250Kbaud RF network. This system combines: USID (ultrasonic
ID), RFID (radio frequency ID) and RF wireless network
communication. For synchronization, radio is used as a start signal.
After the tag receives a sync call, over an RF channel, the tag
emits RFID and 4mS later ultrasound. A flashing, a blue LED
indicates the emission cycle. Receivers report through a serial
port: the time elapsed, from RF synchronization call, until the
arrival of the airborne ultrasonic signal. Absolute distance; can be
computed from the transmitter, to every receiver in range. The
transmitter is equipped with a serial I/O; this serial pin can be
used to read information of the RF network. E.g. processed 3d
coordinates from previous cycle, can stream out the serial pin just
prior to the next cycle. I.e. the tag’s own coordinates is read
from its I/O pin, along with the position of all the other tags if
needed.
Users
can access, the hx19 device-to-device RF COM. network, using either
a transmitter/tag port-pin, or an hx19m USB / serial interface.
The Hx19 is not only a
synchronized system; it can operate asynchronously as well. RFID and
USID; can be utilized in combination by the programmer; for a very
reliable fail-safe positioning, of people and objects. The RFID can
be used for omni-directional, non-line of sight localization through
walls; while the boundary sensitive USID, is used for specific
localization within the confine.
HX19TX Ultrasonic
RF battery Transmitter Tag. Weight 22 g
Ultrasonic RF
Receiver. Weight 40g
HX19MS USB
Monitor Synchronizer
Weight 40g
HX19RX
Basic
HX19 communications
HX19
components utilize a powerful command structure, using both direct
commands and nested message features. All the commands; are read
from the first character to the last; each command is executed on
first come first serve basis. Operations requiring synchronized
action take place after the command line has been fully serviced.
Characters that are not valid commands are ignored, and therefore
free to use. Dots, commas, space and etc between commands bear no
consequence. Carriage return is a delimiter and shouldn’t be used
in the command line. Numeric values where required; must follow the
command immediately, and the value must remain unbroken. Spaces or
other characters will break up the numeric value.
Addressing
sequences; tolerate no numeric breakup, T1234& is transmitter
1234. The sequence T& addresses all transmitters. The first
alphanumeric character in a command string, represent a device
class.
The
character / is used by the hx19 communication protocol; to separate
data from checksum (not visible to the average user). CR or
carriage return, is used by the protocol as a delimiter. Within
brackets < > or [ ] the character | can be used to generate
carriage return and line feed Large alphabetic
letters, signify addresses. Small letters, are considered commands,
and are sometimes followed by a numeric value.
HX19
Communications Syntax Example:
Command string syntax: T21& i49 n90 ee
T21&
is the address portion of the command string. The first character
of the string must represent the class of the recipient, “T”
for tags, “R” for receivers and “M” for monitor.
Exclamation “!” gets the attention of all device regardless of
class. For private device addressing; the class character, must be
followed by unbroken numeric characters; terminated with “&”.
In the command line, unassigned characters are ignored, and can be
used to make the sequence more readable. Characters i, n, ee are
all commands recognized by the HX19TX. i: sets the ultrasonic
monotone period, n: sets the number of ultrasonic periods emitted
and ee: stores the operating parameters permanently on flash
memory.
T&i49n90ee sets all
transmitters to the (see above) T21 configuration
!&
p0 ee: this command sequence will force all devices, tags,
receivers, monitor and etc; to set RF transmitter at lowest power,
and store current operating parameters permanently on flash memory. Using
the “!” exclamation to configure all devices in a single
broadcast go can be dangerous.
For
example, “!& t111 r33” this command string will force all
devices to transmit on rf channel 111, and receive on channel 33.
The hx19m USB monitor is always inverted; it receives transmissions
from other devices, and transmits commands, which other devices
receive. In this case it should be set to receive on channel 111,
and transmit on channel 33. This can be corrected with the
following line command: M&r111t33, which corrects all hx19m
monitors within range.
The acquisition
interval or activity cycle must be the same for all devices within
the range of a single system. Command a# sets the interval in terms
of milliseconds, i.e. a32 sets the acquisition interval equal to
32mS this means that the sample rate will be 1/0.032 or 31.25
samples per second. At this rate care must be given to the time of
flight issue, the range allowable within this short time period is
limited given that the sonic wave travels at 344m/s roughly. Also
the sonic emission of the tags must be adjusted to reduce
reverberation and signal power, this can be done by reducing
ultrasonic signal train width by using the tag command n, the
default is n60. In case of high-speed needs at 32s/s this value
should be reduced to n10, or whatever results in reliable distance
measurements. A central controller can adjust these values on the
fly between cycles, to streamline operation. Battery duration
can be decreased, if devices are not all set at the same sample
rates, plus irregular operation.Continuous sample rates
The
Hx19tx USID RFID tag
HX19TX is battery powered; coin batteries size
2032 go into a holder on the back of the unit with minus facing the
PCB. Once a battery is inserted into the battery holder the tag
will enter idle mode. In idle mode the Hx19tx by default flashes a
blue LED at intervals between 4 and 8 seconds. During the flashes
it emits ultrasound and RFID by default. The randomized LED flashes
during emission can be shut down using RF link. During the activity
cycle; the tag also scans for incoming RF synchronization signal.
HX19TX
SIZE: 40 x 40 x 15 mm
If no such signal is detected, the device goes
to sleep to reserve battery power. Otherwise; the emission cycle is
synchronized, and driven by the synchronization signal from an
hx19ms. In synchronized mode (access program Sync selected); the
emission cycle is strobed 16 times per second (by default), and the
LED if enabled will be flashing rapidly. An Hx19ms (see below)
connected to a computer serial I/O, or a USB port; can be used to
synchronize, and monitor the hx19 network. It is also used to send
control, and configuration parameters to the hx19 devices
Unlike the hx19m and hx19r series, the hx19t
series can only accept commands and configuration while being
strobed (synchronized); with, if enabled the LED flashing rabidly.
Similarly if the hx19r is configured for battery savings, it
must also be strobed (synchronized) for communication. The hx19ms connected to serial or a USB port; at
a rate of 250k baud, can broadcast commands in range up to 30
meters, at full power. Hx19 devices scan for pertinent control
characters in the broadcasted serial stream. Large alphabetic
letters, signify addresses. Small letters, are considered commands,
and are sometimes followed by a numeric value. The characters “T”
and “!”, are interpreted as hx19t series addressing codes, i.e.
“T” means attention all tags and “!” attention all devices
(including tags).
Syntax
examples:
The
first character in a control string (line command); must correspond
to the device type (its class). Tags respond to the initial
characters “!” or “T” only. Characters between T and the
terminator &, e.g. “T1234&” represent the private ID of
the device. The default private ID of the device, in this case
(1234) is written on the enclosure. Strings following “&”;
are configuration commands and data. Following is a simple string;
broadcasted from an hx19ms (monitor synchronizer).
T& md0 d1 ee
If
received by a tag, the mode command above shuts down the LED. In
this case, all tags
within range of the hx19ms; will stop flashing the blue LED during
emission and they will stay asleep for a short time as commanded by
d1, only 0.25 seconds. Finally this configuration is permanently
stored on FLASH memory.
Example: pertinent to all
devices within the range of the hx19ms
T& md0 (all tags will shut
down the LED)
T31&md0 (only tag 31 will
shut down its LED)
R& md0 (all receivers will
shut down the LED)
!& md0 (all devices will
shut down the LED)
Another example: !& = ee
Characters
not listed for control are ignored, the dummy “=” is ignored.
All devices receiving this command: receivers, tags and repeaters
will store the current
control parameters
on EEPROM flash memory.
Given
that the tag (enclosure) is labeled 13, (this is the private
address of the transmitter). Then consider the following string
broadcasted from an hx19ms:
T13& mx0 d6 (This is
just as valid: T13&mx0d6 or T&mx0,,, d5)
Only
device labeled 13, will respond to the broadcasted string above.
Tag 13; will not emit RFID during activity cycle. It will set
downtime to 6 seconds average.
T13& mx0 mu0 md0 [T13 got
the message]
To
get an acknowledgement that the string was received, use the [ ] to
force hx19 members to broadcast a message. Tag 13 will shut down
US, RFID, the LED and then broadcast T13 got the message. “T13
got the message” should appear in an hx19Access textbox.
Tag
Commands Summery
These
following short commands, dictate the behavior of the hx19tx
ultrasonic RF tags. Below the # indicates, decimal numeric
characters need to follow the command. ? means specified ASCII
character.
Tag
Commands Summery ! Attention
all devices. Global call to all devices, including tags respond T& Public
transmitter call, all tags respond to this call
T#& Addresses
a specific tag privately where # is the tags specific numeric ID.
a#: Acquisition
interval (Sample rates) ee
The device stores current parameters on EEPROM p# RF
transmission power, used to control the range bubble (default 2,
range 0 through 3 ) r#
Select RF input channel range (1 to 125). (default
ch. 123 = 2.523GHZ) t# Select
RF output channel range (1 to 125) (default ch.
123 = 2.523GHZ) [ Everything
between the first opening “[“ and the last “]” closing
bracket is RF broadcasted m? Replace
the ? with a letter from the mode submenu followed by 1 for ON and
0 for OFF <
> Received data between the first and the last bracket is
placed on the serial wire I/O
d#
Downtime # is a decimal value controlling the sleep duration h
Deep sleep, the device essentially shuts off (sync strobing will
wake the device in 24-64s) ht
Shut off, device can be turned back on by grounding the
micromatch pin i#
Period of the monotone ultrasonic burst (default 49 corresponds
to 40khz) n# Number
of periods or length of the burst (default 60 periods) b get
battery status v get
device version w get
status of work registers x Change
the RFID of the tag
Mode Submenu:
d# “d1” disables LED, “d0” enables LED
(default d0)
x#: “x1” RFID is emitted “x0” no RFID is
emitted (default x1)
c#: “c1” enables record count insertion (default
c0)
n#: Enable Direct Network Access (default n0 DNA
disabled)
p#: Disable serial com pin (default p0 pin enabled)
b#: Continuous Supply or Battery Monitoring (default
b0 battery monitoring disabled) *
* Underscore is added
to the RFID followed by batter level, the numeric character 0-9
resents the power supply level. It should not be higher than 7 and
not lower than 3.
Mode
and submenu Example:
T23&md1 will
turn the LED ON for tag23, T23&md0 will turn the LED OFF for
tag23 Downtime
[d#] (# default 6)
If
the hx19t tag, finds the command d in the configuration string from
the hx19ms. Then it will use the first numeric value it finds, to
select the downtime. This parameter, controls how long the device
stays at sleep. The following table shows the time durations
available. If the [h] command is used to shut down the hx19tx,
downtime is multiplied by eight; until re-synchronization
Value
# following d 1 2 3 4 5 6 Sleep
duration (Seconds) 0.25 0.5 1 2 4 8 “T17&
d4” this string sets the sleep time for tag-17, at 2 seconds
nominally, the unit randomly selects either 1 or 2 seconds for
flashing the IDs. E.g. if sleep duration is set at 8 seconds, then
the device randomly executes 4 or 8 second sleep time.
Shutdown
[h]
When
the command “h” is found in the setup string, the hx19tx tag,
immediately shuts down, and the current sleep time is eight folded,
commands following “h” are ignored. The tag will wake up
periodically, and go through the activity cycle; if no airborne RF
is detected, it goes to sleep. There are two ways of waking the tag
from deep sleep: Broadcasting sync signal using the hx19ms; or
shunting the pin4 or pin5 to ground momentarily (see appendix 9
external connection).
“T&
m0 h” this sequence addresses all tags.  In this case there is no
feedback, to indicate any action, one cannot know if all the units
got the message. In deep sleep the hx19tx comes up at least once
every 64 seconds, to look for sync; if not found, it goes back to
sleep. The hx19ms series must strobe sync continuously for more
than 64 seconds to establish state of alertness. Sync duration for
70 seconds, wakes the tags with certainty.
EEPROM
(FLASH) save [ee]
If
the hx19tx finds the ee in the command string, the current
parameters under which the device is operating are stored on FLASH;
and will be restored in case the tag looses power.
If
micro USB pin 2 is shunted to ground while the device boots (starts
up) then the flash parameters are not restored, default parameters
are loaded into the work registers
Period
[i#] (# default 49 (40khz)): implemented
on next sync
The
value that follows the command i, sets the period of the monotone
ultrasonic burst (bit.3
of the mode byte must be set high). Pings
can be preceded by RFID, to identify its source. RFID and US ping
occur with 4 ms separation.
Number
of Periods [n#] (# default 60): implemented
on next sync
This
command controls the duration of the ultrasonic burst, and the
value that follows n is the total number of periods in the ping
that are emitted. Monotone contains no identifiable ultrasonic
signature, clearing the monotone bit, will reestablish identifiable
ultrasonic signal.
T13&=mm1 i49 n100
The
string above will select monotone and emit enabled RFID + sonic
ping. Since the i-value is 49, the hx19tx will transmit 100 periods
at 40khz (25μS each) to the ultrasonic sensor. The duration of the
burst is therefore 2.5mS.
Monotone
Frequency = 4Mhz / [2 x (# +1)] # is the alphanumeric following
the command-i. The acquisition interval or activity cycle must be
the same for all devices within the range of a single system.
Command a# sets the interval in terms of milliseconds, i.e. a32
sets the acquisition interval equal to 32mS this means that the
sample rate will be 1/0.032 or 31.25 samples per second. Battery life can
be decreased, if devices are not all set at the same sample rates
The ‘a#’ acquisition interval in
milliseconds for sample rate control (# default 60)
The ‘b’ command supply or battery level
(Version 2.2 and above)
To check on the
status of the battery or the level of the voltage supply the b
command can be used. Dividing the result value with approximately
37 will yield a reasonable approach to the actual voltage level
supplied to the tag. The voltage level should not be higher than
4.5V and not lower than 2.8V. If the value is not steady, your
supply source is inadequate.
Radio
Power Level [p#] (# default 3)
The
numeric value following the command p, dictates the power used to
transmit the RFID, and therefore the range of the RF bubble. Power
levels are shown in the following table.
Value
following p 0 1 2 3 Radio
transmission power -20dBm -10dBm -5dBm 0dBm Radio
Channel out [t#] (# default 123)
This
command; allows the user to change the RF channel, through which
the hx19t series broadcast.
Example: T245&=p0 t121
r122
The
string above will set transmitter 245, to broadcast on channel 121
using minimum power, and receive through channel r122.
Radio
Channel in [r#] (# default 123)
This
command; allows the user to change the RF channel, through which an
hx19t receives data.
Example: T& r111 ee The
string above will set all transmitters, to receive through channel
111. This setup will be stored on EEPROM (FLASH), and reloaded in
case the receiver looses power.
Terminate
Operation [ht] Syntax:
T&ht
This
command terminates operation, in this state, the only way to resume
operation is by shunting micro USB pin 3 to ground momentarily (see
appendix 10 connecting the Tag). Activity on the serial I/O pin
will also activate the Tag.
Change the RFID of a tag [x]
Syntax: T&xJohn#
To change the RFID specify the new ID between the command x and # (max 16 char), any valid ASCII characters are accepted. The syntax example will name all active tags in RF range “John”. Given that the default tag ID is 23 then T23&John# will change private address 23 to John.
Example: TJohn&x87# ee [acknowledge]
This example assigns a new address 87 to a tag previously named John, and stores the result on flash (permanent memory).
Omni Directional Example (assuming you have tags 20, 21, 22, 23, 24 and 25)
Example: T21&mx0 x20#
Shut down the RFID of tag 23 and rename it as tag 20. You now have two transmitters with the same RFID 20, one emits RFID the other is silent
Similarely: T22& mx0 x20# (T22 alias T20)
T23& mx0 x20# (T23 alias T20)
T24& mx0 x20# (T24 alias T20)
T25& mx0 x20# (T25 alias T20)
Only the original T20 is assumed to be emitting RFID, having more than one transmitter emitting RFID over the same channel simultaneously is not a good idea. Off course e.g. T24&t33 x20 is also acceptable since T24 “alias T20” will be emitting its RFID on channel 33 hopefully different from the original T20 emission channel. Extra hx19ms monitoring can be tuned to other RF channels, to pick up for example RFIDs on channel 33.
Finally: M1&q20 s1 $ (see hx19ms commands)
Here M1 calls only T20 at speeds up to 16s/s, all the T20 aliases will emit ultrasonic signal, and if they are mounted back to back on the six sides of a cube, a true omni-directional condition will exist.
NOTE
The tag must be strobing or under sync (see the sync select hx19access.exe) to change its parameters.
Serial
I/O Com-Pin Bi-directional Simplex operation A
port pin (com-pin), can be used to receive or transmit broadcast
(simplex); hx19t series are able to relay information from the RF
network, to the object it is attached to. When the com-pin is
transmitting, it is configured as output. Otherwise the com-pin is
at high impedance state (hi-z). Communication baud rate is
250kbaud. Both RX and TX utilize a single wire, and the signal
needs to be inverted for RS232 port.
If
bit five of the mode byte (see above) is set “direct access to RF
network” is enabled. All data received via the hx19tx com-pin, is
broadcasted as it becomes available; and all that is received from
the network, is dumped serially through the com-pin. Units used for
direct network access, are sensitive to pertinent commands,
arriving through both RF and own com-pin.
Commands
directed privately to an hx19 unit through own com-pins, are not
broadcasted.
Example:
T6& md1 <what goes around comes around> t123
If
this string is signaled through a com-pin on a tag other than tag
6, it is immediately broadcasted. Consequently if the string is
received by T6: then T6 will turn on its LED, and the string
between the brackets, “what goes around comes around” will be
signaled on T6 com-pin if enabled. And then T6 will set its RF
channel at 123.
If
T6 “Direct RF network access bit” is enabled, then the entire
received string, plus the string in the brackets is dumped through
an enabled T6 com-pin.
Own
address signaled through the com-pin If
T6& p0
[broadcast this] d1/888 is
signaled through the T6 com-pin then the string
“T6& p0 [broadcast
this] d1/888|T6#” is echoed back.
T6#
is appended by T6 to acknowledge receipt of the string. If correct
checksum is received with the CR delimiter, Hx19 T6 will process
the command, and when finished, issue acknowledge. This will be
“T6#”.
The
symbol | is here only to represent a carriage return, following the
hexadecimal checksum 888. This is the sum, of all the ASCII values
from the first character, to the / forwards slash. If
your addressing is not
private, e.g. like
this T&[testing]/430, then the following is echoed back.
T&[testing]/430|#
Notice
the private acknowledge is missing, but the # indicates the command
was processed i.e. it was broadcasted.
Com
Pin Startup Signals
After
either D or E is signaled, indicating what parameters, were loaded.
Then the enabled com-pin will signal < as main action cycle is
executed. Just before the unit goes to sleep; the com-pin signals >
closing bracket. Between the brackets, the device is active and
listening for a sync signal. In idle mode; the unit will wake up,
at the average interval of 6 seconds, if no sync is detected, it
goes back to sleep.
Control
Parameters:
All
parameters including the mode byte; can be modified while the
hx19tx is in synchronous mode, and on the fly. This can be done
using either RF or I/O com-pin on the tag. The parameters remain
unchanged, until either re-modified, or the battery is removed from
the holder for more than approx. ten seconds, (it varies depending
on operating state). To ensure; parameters remain unchanged when
the battery is removed, these must have been stored on the hx19tx
EEPROM flash, prior to supply power removal. Installing
the Battery
After
a new battery is placed in the holder, the transmitter LED blinks 3
times, this indicates all is well. If the com-pin is enabled;
character D, will be signaled through the com-pin when the battery
is installed. In this case the transmitter has been started with
its default parameters. If parameters are at some point, stored on
EEPROM (flash), the pin will signal E when a new battery is
installed. This means: parameters stored are reentered into the
system.
The
Hx19r v2 the receiver
The
hx19r receiver can operate in two basic modes, alert mode, and low
power battery mode.
Continuous
mode (mp0 or bit.2 clear)[default]
In
continuous active mode the hx19rx is always alert, any tag within
radio frequency range is processed without delay. Current
consumption in this mode is continous approx. 25mA.
Battery
mode (mp1 or bit.2 set)
In
this mode, if no synchronizing RF activity is detected, the hx19rx
goes to sleep to preserve energy. It wakes up periodically, to look
for RF activity. When a synchronizing RF signal is found, it enters
active mode, and remains there until the RF sync is no longer
detected. Current consumption in this mode at 3V, is under 8mA at
full synchronous sampling rate of 16 samples per second. And
20microAmp during no RF activity idle mode.
The
Hx19rx output string.
In
active mode the Hx19rx, waits for the reception of either RFID, or
a special RF synchronization signal. Upon arrival of the RF signal,
it clears its timer and initiates a stopwatch. It logs, the first
ultrasonic wave front’s time of arrival, and prefixes time of
flight with the character A. If the device is set up for noise
recovery, then the prefix can be any letter from A to P where
ascending letters indicate environmental noise levels. The
full output format broadcasted by the Hx19rx
[Receiver
ID] [RFID_Record#] [(prefix)+Time of sonic flight_Doppler value] /
[checksum]
Typical
Output: given the receiver ID is 6 RF
Output String Syntax: R6 P5_34 A6850_2000
Wire
Output String Syntax: R6 P5_34 A6850_2000 If
both Doppler mode of the receiver and Record ID of the transmitter
are disabled then the output is as follows. Default: RF
Output String Syntax: R6 P5 A6850
Wire
Output String Syntax: R6 P5 A6850
Output
String Analysis
Please
refer to the string shown above (output string syntax). P5 is the
RFID of tag marked 5. The string indicates that tag 5 is 6850 mm
away from receiver 6. If
there is no valid ultrasound present, the string will contain the
receiver ID and the RFID only.
No
ultrasound, example: R7
P5. Tag 5 RFID,
was received by receiver 7
The
function, of the hx19r series can be modified, using the 2.4-2.5Ghz
radio connection at 250baud. USB port of most computers can be
used to that end; other options exist like direct serial
communication using RS232 or RS485/422, and the Ethernet. Hexamite
can provide a bridge to the hx19 for most interface preferences.
Doppler The
Doppler value from the receiver is converted into velocity in terms
of meters/second as follows. Vdoppler
= speed of sound * ((reference period/measured period) – 1) Given
that the emitted signal period from the transmitter, is select i49
then the reference period is computed by. Reference
period = periods *100 (default periods = 20) And Measured
period = (displayed after the position) Example: R6
P5_34 A6850_2000 (object is not moving) In
the above the object is not moving when it moves the value after
underscore changes, e.g. R6
P5_34 A6850_1998 (object is moving towards the receiver) Vdoppler
= 344m/s ((2000/1998) – 1) = 0.344m/s
Parameters:
If
the hx19r series is set for battery savings mode, then parameters
can be modified only, while the unit is in synchronization with the
strobing hx19ms. Parameters
remain unchanged, until either re-modified, or the unit looses
power. To remain unchanged, in the event of a power loss at start
up, parameters must be stored on the hx19r series EEPROM (flash).
Lower
case alphabetic characters, are recognized as commands by the hx19
system, the command may or may not have a control numeric value
referred to as #. A control value is the numeric string, following
the command identifier. The syntax of the control string is shown
below.
! Attention
all devices. Global call to all devices, receivers included R& Public
transmitter call, all tags respond to this call
R#& Addresses
a specific receiver privately, # is the specific numeric ID.
a#: Acquisition
interval (Sample rates) ee
The device stores current operating parameters on EEPROM p# Select
RF transmission power, used to control the range bubble (default 3,
range 0 through 3) r#
Select RF input channel range (1 to 125). (default
ch. 123 = 2.523GHZ) t# Select
RF output channel range (1 to 125) (default ch.
123 = 2.523GHZ) [ Everything
between the first opening “[“ and the last “]” closing
bracket is RF broadcasted m? Mode
# is a decimal value setting and clearing the mode bits <
> ASCII data between the first and the last bracket is relayed
to the serial I/O (RS485/RS232) b Receiver
looks for ^# between broadcast brackets and replaces with #
characters from memory bt receiver
battery status h
Deep sleep, the device essentially shuts off (sync strobing will
wake the device in 24-64s) q# Sets
up a receiver output result queue
v Gets
the device version w gets
the status of the work registers.
Mode Submenu:
d# The LED is on during the
activity cycle
s#: Activate Doppler Reading
p#: power savings ON, battery
mode
n#: noise recovery mode
Receiver
Commands Summery
The acquisition
interval or activity cycle must be the same for all devices within
the range of a single system. Command a# sets the interval in terms
of milliseconds, i.e. a32 sets the acquisition interval equal to
32mS this means that the sample rate will be 1/0.032 or 31.25
samples per second. Battery life can
be decreased, if devices are not all set at the same sample rates EEPROM
save [ee]
If
the hx19rx finds the command e in the setup string, the current
parameters under which the device is operating get transferred to
EEPROM (flash). These parameters will install during startup. Radio
Power Level [p#] (default 2)
The
numeric value, following the command p, dictates the RF power used
to transmit the receiver output string. Power levels are shown in
the following table. The power levels affect the range of the
receiver RF range bubble from 5 to 40 meters
Value
following p 0 1 2 3 Radio
transmission power -20dBm -10dBm -5dBm 0dBm Radio
Channel out [t#] (default 123)
This
command, allows the user to change the RF channel, through which
the hx19rx broadcasts its result.
Example: R12345&=p0
t121 r122
Command
line shown above will configure receiver 12345, to broadcast on
channel 121, using minimum power, and receive through channel 122.
Radio
Channel in [r#] (default 123)
This
command allows the user to change the RF channel, through which it
receives broadcasts.
Example: R& r111 ee The
string shown above will set all receivers, to receive RF through
channel 111. This configuration will be stored on EEPROM (flash),
and reloaded in case the receiver looses power.
The ‘a#’ acquisition interval in
milliseconds for sample rate control (# default 60)
Mode Submenu:
d# The LED is on during the
activity cycle
s#: Activate Doppler Reading
p#: power savings ON, battery
mode
n#: noise recovery mode Mode
parameters:
Doppler
switch (s) The
subcommand s switch sets up Doppler evaluation and measured Doppler
value is displayed, the Doppler value can be used to compute
instantaneous speed. This is done in the following manner.
Hx19 Doppler reference value is 2000.
Given that object Velocity = speed of sound *
(reference/measured – 1)
Velocity graduation per increment of the measurement
value
Example: V=344m/S (2000/1999 –1) = 0.172m/S
Example2: V=344m/S (2000/1900 –1) = 18m/S
Noise
recovery switch (n) The
subcommand noise recovery n forces the receiver to double check the
signal; if it isn’t valid it doesn’t act on it, but waits for a
new signal. Every time it gets a false start it increments the
prefix of the distance measurement, e.g. A becomes a B. It is at
the users discretion to learn how noisy the environment can be for
acceptable performance.
Queue order [q#]
For high-speed operation synchronization is required.
The receivers operate like a stopwatch, and the tag’s emitted
wave is like the runner to be timed, but there is room for only one
runner on the track. Hence each runner must be called out one after
another. On sync (start gun) the receiver starts timing and the tag
emits a wave. When the wave hits the finish line the watch is
stopped the receiver waits out its wave flight allowance time, then
broadcasts the timing results. If many receivers call out the time
result simultaneously over the same RF channel, the signal gets
scrambled and the hx19ms connected to a PC USB will not understand
any message. So the receivers must broadcast their result one
following another. This is controlled with the q command in terms
of ¼ milliseconds.
Timing (refer to the a user variable default a62)
Acquisition time = overhead + flight allowance + queue
time + tag emission delay
Flight allowance = acquisition time – receiver
overhead – tag emission delay – queue time
Acquisition time is a user variable, receiver overhead
is around 7mS, and tag emission delay is precisely 4.096mS.
Given:
acquisition time is 62mS as selected using the a command or “a62”
and queue time is selected q9 then
Flight allowance = 62 - 7 - 4 - 9/4 = 48mS
Maximum Range = Flight allowance * speed of sound
Maximum Range = 0.048s * 344m/s = 16.5m
If another receiver
is added to the system it should be separated by roughly 2 mS from
the first receiver in the system. The separation time depends on
how much data the receiver is going to broadcast after each time of
flight measurement. Assuming the maximum output data length we have
to double the 9/4 interval for receiver 2 therefore q18 or 18/4 mS
must be applied. Therefore with two receivers the maximum range for
the second receiver will be Flight
allowance = 62 – 7 – 4 – 18/4 = 46mS Maximum
Range for the second receiver = 0.046 * 344 = 15.8m
If high speed and
many receivers are required, more hx19ms devices should be added to
the system, and receivers set up to broadcast results
simultaneously on multiple frequencies.
Using
the Serial Output pin HX19R version 2.4 and above Distance
data is available on a serial output wire from the hx19receiver.
This feature allows the user to read broadcasted data as it streams
directly from the receiver through a wire. The serial output has a
TTL format, i.e. inversed RS232 and the baud rate is 250Kbaud.
Identification of the receiver and tag, plus the distance from the
receiver to tag comes streaming through this port pin (wire). For
hx19 devices this wire is typically the fourth from the ground wire
on the ribbon cable. Many
devices are available that can utilize TTL serial data, FTDI serial
to USB is very common and available device that turns a USB port
into a COM port or a serial port. The hx19 devices interface
directly to this device. TTL-RS232R_PCB Mouser
part number: 895-TTL-232R-5V-PCB Farnell
part number: 1740366
The ground or
negative reference on the hx19receiver usually closest to the edge
of the micromatch plug connects directly to the GND pad (soldered
one). VCC pad is soldered to the third wire counting the ground
wire as number one. The fourth wire from the ground is the serial
output, and it is soldered directly to the RXD pad. FTDI devices are very
common and available, and will interface many operating systems to
COM I/O. Whatever devices used, make sure they are able to read
3.2V signals. Hx19access is really
just a simple terminal program; it can be used to read both data
that comes from the hx19ms through RF wireless and data coming
through hx19r wire simultaneously. The hx19ms uses FTDI drivers
too. E.g. plug the hx19ms into a USB port and set the port to COM5,
plug the hx19r wire interface into another USB port and set it to
COM3. Then put a hx19access.exe into a directory holding port.txt
file containing 5 (port number), and put another hx19access.exe
into a separate directory holding port.txt file containing 3 (port
number). Then run both hx19access.exe, and both privately wired and
wireless network data should be visible.
The
HX19MS monitor / synchronizer
This
device is the bridge, between the computer (programmer) and the
hx19 positioning system. Manipulating this device, is somewhat
similar to the hx19r and hx19t series. It will take command lines,
directly from the PC, through USB or serial I/O; process the line,
and if applicable broadcast onto the hx19 network. The hx19ms is
the master synchronizer for the whole network. It monitors
broadcasts from all other hx19 devices, receivers, tags and other
HX19MS units. Typical
range for the hx19ms device is about 40 meters. HX29MS-E has an
extended range and can synchronize devices to 100 meters radius.
Hx19ms-RS232
version has DB9 RS232 connection instead of USB. In this case RF
communication; is controlled using a RS232 or a TTL input.
HX19MS-USB on the right; enables access to the HX19 RF network via
USB port. Hexamite provides visual basic programs, with source code
to help the programmer understand the communication procedure. The
hx19ms accepts a few direct commands; its general address type is
M. Many
hx19ms devices can be connected to different computers to monitor
hx19 activities, but only one should control synchronization
! Attention
all devices. Global call to all devices, monitors included M& Public
monitor synchronizer call, every HX19MS responds to this call
M#& Addresses
a specific a HX19MS privately, # is the specific numeric device ID.
a#: Acquisition
interval (Sample rates) ee
The device stores current operating parameters on EEPROM px# Select
RF transmission power, used to control the range bubble (default 3,
range 0 through 3) r#
Select RF input channel range (1 to 125). (default
ch. 123 = 2.523GHZ) t# Select
RF output channel range (1 to 125) (default ch.
123 = 2.523GHZ) [ The
device broadcasts its Receive Buffers excluding first opening and
closing brackets <
> Received data between the first and the last bracket is
placed on the serial wire I/O
$ Enables
the synchronization strobe % Stops
the synchronization strobe f# first
tag called in a queue
s# number of tags called
v Gets
the device version w gets
the status of the work registers. md# if
# is 1 the blue LED will flash, if 0 the LED is of (# default 1) EEPROM
save [ee]
If
the hx19ms finds the command e in the setup string, the current
parameters, under which the device is operating, is stored on
EEPROM, and will be restored after the device loses power.
Radio
Channel out [t#] (default 123)
This
command, allows the user to change the RF channel, through which
the hx19ms broadcasts its result.
Example: M5&=p0 t121
r122
Command
line shown above will configure hx19ms-5, to broadcast on channel
121, and receive on channel 122.
Radio
Channel in [r#] (default 123)
Following
command “r” allows the user to change the RF channel, where
hx19ms receives broadcasts.
Example: M& r111 ee The
string shown above; will set all hx19ms devices in range, to
receive RF on channel 111. This configuration is stored on EEPROM
(flash), and reloaded in case of power loss.Monitor
Synchronizer Command Summery
Synchronize
command [$]
When
the hx19ms receives this command character, it broadcasts
synchronization signals periodically over the network. Every device
in range eventually enters synchronized activity cycle; timing
latency is within a microsecond.
Example:
M33&$ Sets M33 as the master synchronizer During
a synchronized cycle, command codes can be broadcasted to any hx19
device synchronized with the master hx19ms, but only through the
master hx19ms. This holds true, regardless of the battery settings
of hx19 devices.
 In this mode, network broadcast is repeated
on the serial lines (through the serial port). Here the hx19ms acts
as a passive RF monitor receiver only. Radio
Power Level [px] (default 3)
The
numeric value following the command “p”, controls the power,
used by the hx19ms to transmit to other devices on the RF network.
Power levels indicative of range, are shown in the following table.
Value
following p 0 1 2 3 Radio
transmission power -20dBm -10dBm -5dBm 0dBm The acquisition interval or activity cycle must be
the same for all devices within the range of a single system.
Command a# sets the interval in terms of milliseconds, i.e. a32
sets the acquisition interval equal to 32mS this means that the
sample rate will be 1/0.032 or 31.25 samples per second. Battery duration
can be decreased, if devices are not all set at the same sample
rates. This
command sets the first tag called in a calling cycle. This
command determines how many tags are called during the cycle
The ‘a#’ acquisition interval in
milliseconds for sample rate control (# default 60)
The first command [f#]
The scan command [s#]
Page www.hexamite.com


Simple Asteroids game using Ash Framework
Render the game using HTML5 Canvas with simple shapes
Render the game using CreateJS with simple shapes
Render the game using CreateJS and sprite sheet
Render the game in 3D using Three.js with simple shapes.
WebGL-enabled browser is required!


Lena
Modern Coast
Easy Coach
Our services are the best1
For holidays and vacations
Powered by Daystar Technobrains


Mysterious Wizard:
As I see it, you must capture a
Vampire Wizard
and bring back a Gem of Red Light. Correct?
You will find what you are looking for if you search
around here at night
.


The revolutionary LD System of learning to drive. this video explains the main hand controls of the car. The video is used in conjunction with LDC driving skills workbook to learn to drive. These resources together with guidance from an expert LDC driving instructor provide one of the most effective and efficient ways to learn to drive and become a safe driver for life.


SA runaway train investigation derailed
A runaway train rolled through the Whyalla Steelworks, passing eight level crossings and a track used to move molten iron - but the South Australian government has shut down an investigation into the incident after a funding agreement expired.
The driver involved was connecting an engine to wagons on the morning of July 31, when the train began to roll backwards towards the steelworks.
After a failed attempted to turn on the airbrakes and the exterior mechanical handbrake, the driver jumped from the moving cab and alerted controllers.
The train and empty wagons rolled for about six kilometres through the yard, reaching speeds of more than 50km/h on a track with a limit of 15km/h.
During its 11-minute run, it travelled about six kilometres and crossed eight level crossings and a railway track used to move wagons carrying molten iron.
"As the track levelled out, the train slowed by itself and stopped on the steelworks balloon loop," a report released this week by the Australian Transport Safety Bureau (ATSB) said.
Initial information from the train operator, Genesee & Wyoming Australia, indicated the incident was the result of a connection closing before a brake pipe had been exhausted.
"This condition, combined with an undetected fault on one locomotive, resulted in all brakes releasing and the subsequent train runaway," the report said.
But the ATSB revealed it had been instructed to discontinue the investigation. This was because a funding arrangement with the SA government had expired and the government did not see any value in continuing with the inquiry.
"The government of South Australia informed the ATSB that they considered additional investigatory effort would not provide any increased understanding of the root cause of the incident and had decided not to fund any ongoing activities," the report said.
Previously, the SA government has funded the bureau to undertake investigations into incidents on the state's rail networks through a charging agreement.
The government is committed to working with the ATSB to draft the terms of a future funding agreement.


The actions history represents the past actions a user made and is used by the Coveo Machine Learning service to suggest recommendations. It is generated by the page view script (https://github.com/coveo/coveo.analytics.js)
The advanced query expression.
This is the part of the query expression generated by code based on various rules.
eg: Selecting a facet value will cause an expression to be added to the advanced query expression.
Specifies an array of request to retrieve facet values for the CategoryFacet component
Specifies the childField when doing parent-child loading (See: Folding)
The commerce request to execute.
The context is a map of key_value that can be used in the Query pipeline in the Coveo platform.
The constant query expression.
This part of the expression is much alike the advanced query expression, but it is meant to hold expressions that are constant for all users of a search interface/widget.
The results of evaluating those expressions are kept in a special index cache, to avoid re-evaluating them on each query.
You must be careful to not include dynamic parts in this expression, otherwise you risk filling up the cache with useless data and this might have a negative impact on performance.
Expressions other than cq also benefit from caching in the index, but using cq allows to explicitly require that a part of the query be included in the cache.
Whether to include debug information from the Search API in the query response.
Note:
This debug information does not include ranking information.
Setting this property to true
can have an adverse effect on query performance, so it should always be left to
false
in a production environment.
The disjunction query expression.
This is the disjunctive part of the query expression that is merged with the other expression parts using an OR boolean operator.
When specified, the final expression evaluated by the index ends up being (q aq cq) OR (dq).
Whether the index should take collaborative rating in account when ranking result. See: ResultRating
This enables the query correction feature of the index.
By activating this, the index returns an array of {link IQueryCorrection} with suggested word corrections.
Whether to enable the special query syntax such as field references for the basic query expression (parameter q). It is equivalent to a No syntax block applied to the basic query expression. If not specified, the parameter defaults to false
Specifies the length (in number of characters) of the excerpts generated by the indexer based on the keywords present in the query.
The index includes the top most interesting sentences (in the order they appear in the item) that fit in the specified number of characters.
When not specified, the default value is 200.
A request to retrieve user actions in the query response.
Specifies an array of request to retrieve facet values for the DynamicFacet component.
Specifies an array of fields that should be excluded from the query results.
eg: ['@foo','@bar']
Specifies an array of fields that should be returned for each result.
eg: ['@foo','@bar']
Specifies a field on which Folding should be performed.
Folding is a kind of duplicate filtering where only the first result with any given value of the field is included in the result set.
It's typically used to return only one result in a conversation, for example when forum posts in a thread are indexed as separate items.
Number of results that should be folded, using the IQuery.filterField
This is the 0-based index of the first result to return.
If not specified, this parameter defaults to 0.
Specifies an array of Group By operations that can be performed on the query results to extract facets
Whether to enable the support for operator in lowercase (AND OR -> and or)
The contextual text.
This is the contextual text part of the query. It uses the Coveo Machine Learning service to pick key keywords from
the text and add them to the basic expression.
This field is mainly used to pass context such a case description, long textual query or any other form of text that might help in
refining the query.
The maximum age for cached query results, in milliseconds.
If results for the exact same request (including user identities) are available in the in-memory cache, they will be used if they are not older than the specified value.
Otherwise, the query will be sent to the index.
This is the number of results to return, starting from IQuery.firstResult.
If not specified, this parameter defaults to 10.
Specifies the parentField when doing parent-child loading (See: Folding)
Whether to enable partial matching of the basic expression keywords.
By activating this, when the basic expression contains at least IQuery.partialMatchKeywords, items containing only the number of keywords specified by IQuery.partialMatchThreshold will also match the query.
Without this option, items are required to contain all the keywords in order to match the query.
If not specified, this parameter defaults to false.
The minimum number of keywords needed to activate partial match.
Specifies the minimum number of keywords needed for the partial match feature to activate.
If the basic expression contains less than this number of keywords, no transformation is applied on the query.
If not specified, this parameter defaults to 5.
The threshold to use for matching items when partial match is enabled.
Specifies the minimum number of query keywords that an item must contain when partial match is enabled. This value can either be an absolute number or a percentage value based on the total number of keywords.
If not specified, this parameter defaults to 50%.
Name of the query pipeline to use.
Specifies the name of the query pipeline to use for the query. If not specified, the default value is default, which means the default query pipeline will be used.
The basic query expression.
This is typically the query expression entered by the user in a query box.
Since this part of the query is expected to come from user input, it is processed by the Did You Mean feature.
Specifies an array of Query Function operation that will be executed on the results.
Whether to enable question marks with wildcards.
This enables using the question mark ? character within wildcard expressions.
Specifies an array of Ranking Function operations that will be executed on the result
This is the id of the recommendation interface that generated the query.
Specifies whether the first sentences of the item should be included in the results.
The retrieveFirstSentences option is typically used instead of excerpts when displaying email items, where the first sentence of the email might be of more interest than a contextually generated excerpt.
The hub value set from the Analytics component.
Used for analytics reporting in the Coveo platform
Specifies the sort criterion(s) to use to sort results. If not specified, this parameter defaults to Relevancy.
Possible values are :
-- relevancy : This uses all the configured ranking weights as well as any specified ranking expressions to rank results.
-- dateascending / datedescending : Sort using the value of the @date field, which is typically the last modification date of an item in the index.
-- qre : Sort using only the weights applied through ranking expressions. This is much like using Relevancy except that automatic weights based on keyword proximity etc, are not computed.
-- nosort : Do not sort the results. The order in which items are returned is essentially random.
-- @field ascending / @field descending : Sort using the value of a custom field.
The tab value set from the Tab component.
The user ID or visitor ID whose item views should be tagged in the query results (see the isUserActionView property of the IQueryResult interface).
Examples:
Whether to enable wildcards on the basic expression keywords.
This enables the wildcard features of the index. Coveo Platform will expand keywords containing wildcard characters to the possible matching keywords to broaden the query.
See Using Wildcards in Queries.
If not specified, this parameter defaults to false.
The IQuery interface describes a query that can be performed on the Coveo REST Search API.
For basic usage, see the IQuery.q and IQuery.aq properties.
In a normal scenario, a query is built by the QueryBuilder class.


{%extends 'base.html'%} {% load bootstrap3 %} {% block content %} {{block.super}}
{{project.title}}
{{project.description}}
Created by By: {{project.user}}
Posted {{project.date_posted|timesince}} ago


Dengue is caused by an arthropod-borne flavivirus. Infection can be either primary or secondary based on serology, with each stage of the disease characterized by specific serological conversion and antibody formation. Further study is needed to fully identify the factors associated with and predisposing to dengue infection. The objective of this study was to identify socio-demographic factors associated with the prevalence of dengue serotypes in Kassala State in the eastern part of Sudan in 2011.
This was a cross-sectional community-based study with 530 participants who were randomly selected through multi-stage cluster sampling. Dengue serotype prevalence was determined using capture Enzyme-linked immunosorbent assay (ELISA). ELISA IgG. A multivariate logistic regression model was designed to measure the strength of associations between socio-demographic factors and dengue serotype prevalence. All participants who tested negative for dengue were used as the statistical reference group.
From this study, the prevalence of dengue in Kassala was estimated to be 9.4 % (95 % CI: 7.1–12.3). Lack of knowledge about dengue fever disease (OR 2.8, 95 % CI: 1.24–6.53) and a household density of more than 3 people per room (OR 2.1, 95 % CI: 1.06–4.09) were the most important factors associated with dengue infection among the study population.
Community-oriented interventions are needed to modify existing social behaviors to reduce the risk of dengue in the eastern part of Sudan. Additional studies are also required in this field.
Dengue is caused by an arthropod-borne flavivirus [ 1 ], and is currently endemic in several countries worldwide [ 2 ]. It is estimated that there are 390 million (95 % credible interval 284–528) dengue infections per year, of which 96 million (67–136) produce symptoms of varying levels of severity) [ 3 ]. Dengue virus has four known serotypes. Homotypic immunity (specific to the same serotype) is developed after infection with any one of the four serotypes, and is believed to be lifelong. There is also evidence of heterotypic immunity to all serotypes which decreases about 6 months after infection.
Improvements in laboratory tests allow dengue infections to be classified as either a primary or secondary infection, and either a recent or old infection. Primary dengue infection is defined as the first experience of a human host with dengue virus and can manifest in one of three clinical forms. In the majority of patients, it presents as an undifferentiated febrile illness, with cold-like symptoms. Other patients develop severe body pain and high fever, which is classic dengue fever. The remaining patients experience a severe form of dengue presenting as dengue hemorrhagic fever (DHF) or dengue shock syndrome (DSS) [ 4 ].
Secondary dengue is defined as contracting dengue virus after an initial exposure and symptoms, and carries an enhanced risk of DHF/DSS/severe dengue fever due to cross-immunity reactions. The eastern part of Sudan has experienced repeated outbreaks of dengue during the last couple of years particularly from 2005 onward. The areas most affected are Red Sea and Kassala states, which have dengue virus types 1 and 3 in circulation [ 5 , 6 ]. Moreover, DEN-1, DEN-2, and DEN-3 have been confirmed in the port city of Jeddah just across the Red Sea from Kassala, and with connections to the eastern part of the Sudan [ 7 ].
While some factors associated with dengue infections are well understood, others require further investigation. For example, age has an effect on dengue epidemiology, as the likelihood of being seropositive for dengue increases with age because of increased exposure to the viremic vector. Severe dengue virus infection causes higher fatality in very young and very old patients. Military-aged adults from dengue endemic countries are not usually at risk for developing severe dengue disease; however, studies of traveling populations from non-endemic US or Europe have demonstrated that similar-aged naïve populations can succumb to severe dengue disease [ 8 ]. Population movement or travel is also considered to be a risk factor because this increases the chance of being exposed to different dengue serotypes from those in the primary residence, and this is sometimes associated with the severe form of the disease, DHF/DSS. Around 80 % of patients with the severe form of dengue have secondary dengue. The odds of developing DHF on primary exposure to dengue is 0.5 %, which increases to around 5 % upon secondary exposure to a different serotype [ 9 ]. In addition, viremic travelers may contribute to spreading the disease and propagating disease-related outbreaks, particularly in areas that have competent vectors to transmit dengue. In addition, high dengue viremia titers correlate with a greater probability of DHF/DSS [ 10 ]. Knowledge of dengue and about protective measures to prevent infection are considerable tools to prevent both primary and secondary dengue infection [ 11 ].
Dengue is an endemic disease in the eastern part of Sudan, with repeated dengue outbreaks during recent years in 2005, 2008 and 2010. The aim of this study was to assess and define social and demographic risk factors for dengue infections in this region.
This analytical cross-sectional community-based study was performed in Kassala. Kassala is a border state of Sudan, with Eritrea and Ethiopia to the east and national borders with Red Sea state to the north, Khartoum, River Nile, and Gadarif states to the west and south west. The total population of Kassala over the age of 5 years was considered as a source population for this study. Exclusion criteria were those not resident in the state for the previous 6 months, patients with chronic debilitating diseases such as cancers, and those taking immunosuppressant medications.
A multi-stage cluster sampling technique [ 12 ] was used for this study. First, 27 out of the 97 popular administrative units in Kassala were randomly selected for sampling using the probability proportionate to size technique [ 13 ]. Second, households were selected using a systematic, random sampling technique. Within the household, one participant was selected from the eligible population who were present at the time of the data collector’s visit using a simple random sampling approach (random generating table).
A sample of 530 participants was needed to estimate the prevalence of dengue serotypes, and its association with socio-demographic factors with 90 % power and a 95 % confidence level, assuming the measure of association is greater than the null value (OR >1) and a design effect of 2 to adjust for the sampling technique. The formula for the calculation of sample size was applied using OpenEpi software [ 14 ].
A structured questionnaire was used by trained data collectors to collect socio-demographic variables. Venous blood samples were collected for dengue serotyping. A multivariate logistic regression model was designed to quantify the strength of association between study outcome and anticipated risk factors using SPSS-19 and STATA-12 software.
Blood samples were analyzed using Panbio ELISA kits (DF IgG capture) [ 15 ]. According to the manufacturer “the Panbio Dengue IgG Capture ELISA” is for the qualitative presumptive detection of elevated IgG antibodies to dengue virus (serotypes 1–4). The IgG Capture ELISA has a serological sensitivity of 97.9 % (CI: 92.5–99.7 %) and specificity (negatives) of 100 % (CI: 96.6–100.0 %) [ 16 ].
Ethical approval was granted from the ethical review committee of both the Sudan Medical Specialization Board in Khartoum and Kassala State Ministry of Health. Signed informed consent was obtained from all surveyed participants. Participation in the survey was voluntary; neither gifts nor financial incentives were offered.
Of the selected participants, 491 (91 %) agreed to take part, completed the administered questionnaire and gave blood sample. Overall, 60 % of participants were male and the mean age of the participants was 36.6 years, ranging from 13 to 85 years. Baseline characteristics of the study participants are summarized in Table 1 . The prevalence of serotyped dengue was estimated to be 9.4 % (95 % CI: 7.1–12.3). The statistical analysis considered all negative samples as the study control group.
Main individual characteristic of study participants, Kassala 2011
| Characteristics | Frequency | Percent (%) |
|---|---|---|
| Result of the HH interview ( n = 540) | ||
| Completed | 491 | 91 |
| Refuse | 49 | 9 |
| Age groups ( n = 524) | ||
| < 25 years | 106 | 20 |
| 25–35 years | 193 | 37 |
| 36–45 years | 100 | 19 |
| > 45 years | 125 | 24 |
| Mean age (95 % CI) | 36.59 | (35.4–37.8) |
| Age range (in years) Max – Min (SD) | 13–85 | (14) |
| Sex of the interviewee ( n = 525) | ||
| Male | 210 | 40 |
| Female | 315 | 60 |
| Highest level of school ( n = 493) | ||
| Never attended school | 88 | 18 |
| Informal education | 59 | 12 |
| Primary school | 162 | 33 |
| Intermediate school | 31 | 6 |
| Secondary school | 107 | 22 |
| College/certificate | 42 | 9 |
| Higher education | 4 | 1 |
| Relation of the respondent to household head ( n = 528) | ||
| Household head | 147 | 28 |
| Husband/wife | 195 | 37 |
| Son/daughter | 130 | 25 |
| Father/mother | 20 | 4 |
| Brother/sister | 18 | 3 |
| Others | 18 | 3 |
In the multivariate analysis, people who had never heard about dengue (adjusted OR 2.8, 95 % CI: 1.24–6.53), and households with a density of more than 3 people per room (adjusted OR 2.1, 95 % CI: 1.06–4.09) were found to be most likely to be dengue seropositive. The risk of developing dengue infection among people who have never heard about the disease is almost 3 times the risk of the disease among those who have heard about it, and the risk is 2 times more among the residents of crowded households compared with those living in less crowded dwellings. All other factors studied were found to have insignificant statistical association with the study outcome. The multivariate analysis model of factors associated with dengue sero-prevalence is summarized in Table 2 .
Logistic regression analysis for factors associated with dengue sero-prevalence among study Population, Kassala Locality 2011
| Characteristic | Positive/tested | Multivariate analysis | ||
|---|---|---|---|---|
| Adjusted OR | 95 % CI | P value | ||
| Age | ||||
| 35 years or less | 28/281 | 1.17 | 0.55–2.5 | 0.69 |
| > 35 years | 18/206 | |||
| Sex | ||||
| Males | 29/288 | 1.55 | 0.74–3.25 | 0.24 |
| Females | 17/199 | |||
| Education level | ||||
| No formal education | 16/144 | 0.84 | 0.38–1.86 | 0.67 |
| Formal education | 30/344 | |||
| Permanent residence | ||||
| Live outside Kassala | 1/12 | 1.31 | 0.14–11.82 | 0.81 |
| Live in Kassala | 45/472 | |||
| Travel to Red Sea in the last 6 months | ||||
| Yes | 4/42 | 1.36 | 0.34–5.52 | 0.66 |
| No | 42/442 | |||
| Had a guest from Red Sea in the last 6 months | ||||
| Yes | 9/129 | 0.86 | 0.35–2.08 | 0.73 |
| No | 37/354 | |||
| HH member travel to Red Sea in the last 6 months | ||||
| Yes | 4/92 | 0.37 | 0.10–1.38 | 0.14 |
| No | 42/392 | |||
| Had a yellow fever vaccine before | ||||
| Yes | 4/36 | 1.66 | 0.48–5.78 | 0.42 |
| No | 42/446 | |||
| Source of drinking water | 1.17 | 0.55–2.5 | 0.69 | |
| Not piped water | 6/47 | 1.35 | 0.49–3.72 | 0.56 |
| Piped water | 40/438 | |||
| Screens in the windows | ||||
| No intact screen | 40/411 | 0.84 | 0.31–2.25 | 0.73 |
| Intact screen | 6/70 | |||
| Using Bed net | ||||
| Not using bed net | 23/241 | 1.08 | 0.54–2.18 | 0.82 |
| Using bed net | 23/242 | |||
| Never heard about dengue | ||||
| No | 27/197 | 2.84 | 1.24–6.53 | 0.014 |
| Yes | 19/289 | |||
| Household density | ||||
| > 3 | 24/178 | 2.08 | 1.06–4.09 | 0.034 |
| 3 or less | 22/311 | |||
| Household inspection for adult Ae.aegypti | ||||
| Positive | 11/116 | 0.55 | 0.19–1.61 | 0.28 |
| Negative | 35/373 | |||
| Household inspection for Pupa Ae.aegypti | ||||
| Positive | 8/53 | 2.54 | 0.71–9.08 | 0.15 |
| Negative | 38/436 |
In this study, people who had never heard about dengue fever were found to be more at risk of getting dengue infection, with an adjusted OR of 2.8 (95 % CI: 1.24–6.53). This could be explained by a lack of knowledge regarding susceptibility to the disease and the appropriate protective measures. This lack of knowledge is directly exposing participants to a greater risk of contracting the disease compared with others who are well aware about dengue disease dynamics and take preventive measures [ 17 ]. Population knowledge is a vital social determinant of dengue disease epidemiology because community participation is believed to be a key element for current recommended dengue control and prevention strategies worldwide [ 18 ]. Household density, which refers to the number of people per room, was found to be a statistically significant predictor of dengue sero-prevalence amongst the study population, with an odds ratio of 2.1 (95 % CI: 1.06–4.09). This indicates that residents of a household with a density of greater than 3 people per room are more likely to get dengue infection compared with those who live in less crowded accommodation. This finding supports existing beliefs regarding dengue in different parts of the world-that human host density is considered one of the important social determinants of dengue infections. Furthermore, small household size is being confounded by overall human density in other studies [ 19 , 20 ]. This could be attributed to increased exposure of susceptible people to the dengue vector in overcrowded households. The responsible vector, the Aedes mosquito, feeds on multiple humans per day, facilitating transmission of the virus in an efficient manner [ 11 ]. In addition, household density itself is always associated with poverty and low socioeconomic status, particularly in developing countries, and this is another social predictor for dengue infections [ 19 ]. Age of participants in the current study was not statistically associated with dengue fever seropositivity (OR 1.17 (95 % CI: 0.55–2.5)). This is in contrast to a published study that found a higher prevalence of dengue seropositivity with increasing age, which may be due to the increased likelihood of being exposed to a mosquito bite and becoming dengue seropositive over a life span [ 19 ]. In this study, sex did not show a significant association with dengue infection (OR 1.55 (95 % CI: 0.74–3.25)). A similar study, conducted in the southern part of Sudan, had concluded females were at higher risk of developing dengue, which was explained by the fact that in such conservative communities, females usually spend the majority of their time at home and the dengue vector breeds inside homes [ 19 , 21 ]. Any association between dengue susceptibility and sex is debatable, as there are contradictions between the available studies to date [ 22 , 23 ].
Kassala is an urban area located on the highway connecting Khartoum, the capital of Sudan, with the main sea harbor of the country, Port-Sudan city on the Red Sea coast with large population movements and social connections between Kassala and Red Sea state. Families from Port-Sudan usually spend the hot humid months of summer in Kassala taking advantage of more pleasant weather during that season. Port-Sudan has been known as an endemic area for dengue since the 1980s, with repeated dengue outbreaks in recent years particularly since 2005 onward [ 5 , 6 , 24 – 27 ]. It was assumed that dengue disease was imported from Port-Sudan to Kassala; however, in this study, travel of a participant or one of his household members to Red Sea state in the last 6 months was not statistically significantly associated with dengue prevalence in Kassala. Movement of dengue viremic patients is believed to facilitate introduction of new dengue serotypes to other areas and sustain the circle of transmission and propagation [ 19 , 28 ]. Having a guest from Red Sea, storing water at home, the absence of window screens, the presence of Aedes aegypti pupa and adult mosquitos in the house or a history of yellow fever vaccination were all found not to be statistically associated with dengue infection in this study.
Although this is the first attempt to study factors associated with dengue sero-conversion in Kassala, the current study has its limitations, including the fact that it was carried out among community participants regardless of their symptomatic state; this makes it difficult to differentiate between primary and secondary dengue infections. Sometimes IgG levels wane below the IgG ELISA cut-off and this leads to missing cases (both primary and secondary) several years following exposure. Monotypic and polytypic plaque reduction neutralization tests (PRNT) responses could be assessed in the future for more accurate estimation of overall prevalence. Moreover, there is a possibility of cross reaction with other favivirus antibodies that may be circulating in the study area, particularly Yellow fever and Zika viruses that have been documented in other parts of the country, although there are no specific studies conducted in Kassala to date.
People who had never heard of dengue and those living in a household density of more than 3 people per room were those most likely to test seropositive for dengue in Kassala in 2011. Intensive social interventions are required to increase community awareness of dengue to minimize the risk of the severe complications of this infection. Further detailed studies and operational research with more advanced epidemiological methodologies are important to fill the existing knowledge gaps in terms of dengue dynamics in the region.
Competing interests
The authors declare that they have no competing interests.
Authors’ contributions
SH, OS, and MS were the principal investigators and drafted the manuscript. SO, MM and NS had coordinated and managed laboratory analyses for all study samples. KO, MB, KE and JK helped intellectually to design and prepare the study protocol and statistical analysis. All authors contributed and gave input for the final manuscript. All authors read and approved the final manuscript.
Authors would like to acknowledge the support that was received from all partners, particularly H.E Minister of Health in Kassala State and the Director General, field data collectors from Kassala State Epidemiology Department and other departments, the National Public Health Laboratory and Kassala State Public Health Laboratory.


In order to be irreplaceable one must always be different. Design and style should work toward making you look good and feel good without a lot of effort so you can get on with the things that matter. Elegance isn't solely defined by what you wear. It's how you carry yourself, how you speak, what you read.
I like the things around me to be beautiful and slightly dreamy, with a feeling of worldliness. Luxury will be always around, no matter what happens in the world. I love things that age well - things that don't date, that stand the test of time and that become living examples of the absolute best.
Even Michelangelo got paid for doing the Sistine Chapel. Everything I do is a matter of heart, body and soul.
The difference between style and fashion is quality.
Berenice Abbot
1989 - 1991
"Photography can only affect the present. Once photographed, it becomes part of the past."
Diane Arbus
1923 - 1971
"A photograph is a secret about a secret. The more it tells you the less you know."
Dorothea Lange
1895 - 1965
"To know ahead of time what you’re looking for means you’re then only photographing your own preconceptions, which is very limiting, and often false."
Ellen von Unwerth
1954 - present
"I like to photograph anyone before they know what their best angles are."
Eve Arnold
"If a photographer cares about the people before the lens and is compassionate, much is given. It is the photographer, not the camera, that is the instrument."
Imogen Cunningham
"Which of my photographs is my favourite? The one I’m going to take tomorrow."
Sally Mann
"Photographs open doors into the past, but they also allow a look into the future."


Glass jar decorations are very easy to make and look great. Simply grab a glass jar and put some decorations inside. Add some ribbons on the outside for a nice touch.
10-15mins


This is Parna Sarkar, currently a UX designer from Bangalore, India and natively from a beautiful small town in west bengal- Krishnanagar.
I enjoy making beautiful yet meaningful experiences which is one of the reasons I started my designing journey. It began with simple Android mobile customization and I broadened my horizons from there gathering specific skillset for my craft. Academically, I am currently pursuing my triple major in Psychology, Sociology and Economics, from Jyoti Nivas College, Bangalore. I believe the knowledge of human psychology is crucial to UX design and to self development. Hence combining my love for design with my knowledge of human psychology I strive to build meaningful experiences for the users of today.
At my leisure, I love learning new things be it professionally or just for fun, some of them include making handicrafts, doing embroidery, and gardening. I take delight in listening to old Bengali songs. My love for bong cuisine has led me to enjoy cooking at times too. I love illustrating about my interests, my journey and portray it for the world @parna.designs on Instagram.
Apart from that, I relax and unwind by reading on fantasy thriller novels and self development books.
I believing in giving back to the community and helping the needy, owing to this I am the Community Service Director of Rotaract JNC. I also have had the opportunity of being a speaker in the college Debate Club. I am also a actor in "Drammatica" the very fun-loving and welcoming cultural society - The College Drama Club


Army troops rescue octogenarian, others from Boko Haram in Borno
by The Eagle OnlineThe Nigerian Army troops deployed in Gwoza Local Government Area of Borno State has subdued Boko Haram terrorists and rescued an octogenarian, three women and four children held captive.
The Nigerian Army Operations Media Coordinator, Colonel Aminu Iliyasu, disclosed this in a statement on Sunday in Abuja.
Iliyasu said the rescued victims were evacuated, while the children among them were equally administered with polio vaccination by a Nigerian Army medical team.
He added that no causality was recorded by the army troops during the commando operations.
According to him, many of the Boko Haram criminal elements fled in disarray towards the summit of Mandara Mountains with gunshot wounds.
He said: “The troops’ resilience and doggedness are unwavering as further exploitation to complete the annihilation of the insurgents is being sustained in the mountainous environment.
“The Chief of Army Staff (COAS), Lieutenant General Tukur Buratai, wishes to reassure the public of the resolve of the Nigerian Army to continue to execute our constitutional mandate professionally and responsively for a better secured Nigeria.
“He also thanks all well-meaning Nigerians for their continued support, goodwill and understanding towards officers and men of the Nigerian Army as they sustain the conduct of various operations and routine exercises nationwide.”
Iliyasu said the army troops had continued to sustain the tempo of the counter-insurgency operations in the North East with a view to decimating and destroying the remnant of Boko Haram/Islamic State West Africa criminals.
He said the troops had also continued to extract credible intelligence report on the presence of some of the criminal insurgents in the areas.
Previous Post
Osinbajo says right virtues make Nations great
Next Post
Arthur Eze presents, Fayemi chairs The Sun MD's book launch


textOne
textOne
---textTwo---
~~~textTwo~~~
textThree
- ChildOne
- ChildTwo
- ChildThree
- ChildDouble
- ChildDouble
- ChildFour
- ChildFive
Test search child
not child
Test focus element (not implemented)
Execute test
javascript
Wait test
testWait
testClick_OneOf_SingleClick
NotClicked
NotClicked
Find All -> Find All
find-all-child-01
find-all-child-02
find-all-child-03
find-all-child-04
find-all-child-01
find-all-child-02
find-all-child-03
find-all-child-04
find-all-child-01
find-all-child-02
find-all-child-03
find-all-child-04
hidden layer
Checked checkbox:
Not Checked checkbox:
Condition_Attribute test
Condition_Attribute test
Condition_Attribute test
- Selenide here
- Selenide not found
- Selenide not found
- Selenide not found
- Selenide not found
- Selenide not found
- Selenide not found
- Selenide not found
- Selenide not found
- Selenide not found
any text here 123456789
fail
fixed size
BIG DIV
lower
Hello!
"""
'''
"quoted'text'with'quotes'1"
'quoted"text"with"quotes"2'
normal "quoted" text 1
normal 'quoted' text 2


About
Work
Contact
Julio Leonardo
Web Developer
Check it out...
Tribute Page for FCC
Form for FCC
Landing Page for FCC
Technical Documentation For FCC
You Project Here
FCC Profile


This package contains the central interfaces and abstractions of the MiniDraw framework.
For further details, please consult "Flexible, Reliable Software - Using Patterns and Agile Development", by Henrik Baerbak Christensen, CRC Press 2010.
Notes:
Copyright 2010 Henrik Baerbak Christensen Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.


Learning Backbone Marionette
Ch5: Object
How to run this example?
Open index.html in browser
Press F12, go to console tab
See the console logs to understand the flow


Resume
Education
- Associate of Science - Northern Oklahoma College 2009
- University of Oklahoma 2009-2012 - Social Sciences
Work Experience
Cleveland County Family YMCA - Sports Coordinator - 2012-Present
- Organize and staff all youth and adult sports programs
- Oversee all volunteers in the Sports Department
- Plan and implement the department's annual budget
- Collaborate with other local YMCA's and the school district to put on events
Land Services - Imager - 2009-2012
- Travel to rural court houses in Oklahoma and Texas and take photographs of legal documents
- Edit pictures and send them to Landmen
Norman Public Schools - Basketball Coach - 2010 - 2013
- Plan and execute daily basketball practices
- Assist during varsity basketball practice with drills and teaching
- Record statistics during varsity basketball games
Skills
- Ruby(Basics)
- HTML/CSS(Basics)
- People Management Skills
- Organizational Skills


Hi guys,
I am contacting you because I am having some issues with the emonTxV3. I am connecting 3 current clamps to the same cable and I am getting very strange readings (they are all different). This are (some) my readings: (note that CT1 is connected in the oposite direction)
OK 10 201 55 20 65 42 62 0 0 3 126 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-74)
OK 10 203 55 24 65 38 62 0 0 16 126 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-75)
OK 10 202 55 27 65 46 62 0 0 31 126 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-72)
OK 10 230 55 56 65 47 62 0 0 43 126 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-78)
OK 10 90 58 77 62 15 65 0 0 123 128 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-75)
OK 10 226 55 55 65 72 62 0 0 66 126 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-76)
OK 10 91 58 104 62 11 65 0 0 117 128 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-76)
OK 10 93 58 77 62 244 64 0 0 91 128 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-74)
OK 10 96 58 90 62 253 64 0 0 153 128 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-76)
OK 10 88 58 103 62 20 65 0 0 153 128 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-79)
OK 10 90 58 111 62 21 65 0 0 168 128 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-73)
OK 10 97 58 76 62 247 64 0 0 143 128 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-74)
OK 10 115 58 82 62 28 65 0 0 184 128 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-77)
If we take the last line the data would be:
CT1: 58*255+115 = 14,945 W
CT2: 62*255+82 = 15,982 W
CT3: 65*255+28 = 16,603 W
Voltage: 128*255+184 = 32,824*3.3/1024 = 105V (Here we have 220V which is strange.
I even disconnected a clamp from the cable and I was still getting reading like 12,000 W, I live in a small apartment so those reading don't make any sense. Could you please help me I have tried everything.
Re: [SOLVED] Current Reading Issues
The power readings cannot be correct until they get a correct voltage signal to calculate from.
"Voltage: 128*255+184 = 32,824*3.3/1024 = 105V (Here we have 220V which is strange."
I'm not sure where this comes from, the "voltage" integer from the emonTx is calculated to an actual voltage reading but scaled by 100 to give accuracy to 2 decimal places. It is also a signed integer so the result actually reports -325.83v which is even stranger !!
What power supplies are you using ? Just a AC/AC or a combination of AC/AC and Battery or AC/DC ?
Are you using a "stock" sketch in the emonTx?
Paul
edit - Plus if using a AC/AC is it definitely linear NOT switched mode ?
Re: [SOLVED] Current Reading Issues
Thanks pb66 for your answer. I am using just AC/AC power. I am uploading emonTX firmware through the arduino IDE, the firmware that I am uploading is emotxV3_4_Discrete_Sampling with RF12. The AC adapter that I am using is the one that I bought from Open Energy. Any ideas?
Re: [SOLVED] Current Reading Issues
What do you see on a serial monitor connected to the emonTx?
Re: [SOLVED] Current Reading Issues
Hi Robert, I see the following:
emonTx V3.4 Discrete Sampling V1.80 RFM12B
OpenEnergyMonitor.org
POST.....wait 10s
CT 1 Cal 90.90
CT 2 Cal 90.90
CT 3 Cal 90.90
CT 4 Cal 16.67
RMS Voltage on AC-AC is: ~245V
AC-AC detected - Real Power measure enabled
assuming pwr from AC-AC (jumper closed)
Vcal: 245.53
Phase Shift: 1.70
CT 1 detected
No temperature sensor
RFM12B
Node: 10 Freq: 433Mhz Network: 210
CT1 CT2 CT3 CT4 VRMS/BATT PULSE
14333 0 0 0 29727 1
14353 0 0 0 29782 1
14973 0 0 0 30288 1
Regards,
NK
---
Re: [SOLVED] Current Reading Issues
I'm puzzled by the voltage you're measuring. You've said the nominal voltage is 220 V, yet it is showing as about 300 V. What is the exact type of ac adapter that you have? (It should be either 77DB-06-09 or 77DE-06-09. If it is a 77DA-10-09, STOP USING IT IMMEDIATELY - it is a 120 V version.)
Can you measure the no-load voltage from the adapter? It should be about 11 V ac.
Re: [SOLVED] Current Reading Issues
What is also puzzling is why the Vac appears to be escalating (or at least fluctuating wildly), reported as "RMS Voltage on AC-AC is: ~245V" early in the serial print then 297-302v, the original post shows a voltage consistently in the region of 322-329v (ignoring roll-over to signed) presumably after it has been on for a while.
A previous thread (EmonTx RF12 Data Format Doubt) shows values 250-251v has anything changed since then ?
The "Vcal: 245.53" suggests you have calibrated, presumably for use at 220v (currently 268.97 in that sketch) ? although I'm not sure it would be totally necessary (or that different) for a 230v adapter as Vcal follows the AC/AC transformer ratio rather than the supply voltage. Did you change anything else in the sketch?
Paul
Re: [SOLVED] Current Reading Issues
Paul, don't worry too much about the first voltage report in the header - it is a quick only approximately calibrated measurement aimed at checking whether the supply is there or not.
Re: [SOLVED] Current Reading Issues
fair point - I wasn't concerned so much about the value for just that reason, but just thought the >20% jump in next to no time was odd considering I don't recall ever seeing any initial confirmations in the region of 180v for a normal 230v system
Re: [SOLVED] Current Reading Issues
I hadn't linked that other thread to this, something is definitely not the same, yet the calibration values are not so far out as to give a voltage 36% high. There's something really wrong somewhere.
That initial voltage might include a dc offset so it's not totally reliable, it's the raw rms count times 0.87 So the rms count is 282, which gives an ADC input voltage of 0.91 V rms, so given a 10 kΩ : 120 kΩ divider, that's 11.83 V out of the adapter and almost exactly what I'd expect. If it's the Euro adapter, the ratio is 230 V in for 11.5 V out (±5%), hence 236.6 V supply - inside 220 V ±10% and entirely credible. So it looks as if I was wrong to suspect the adapter, and something has changed in the sketch.
Re: [SOLVED] Current Reading Issues
Thanks guys. There sure is something strange about this because we can't that voltage variations in the network. But again, everything is strange with the meassurements.
The answers to your questions below:
What is the exact type of ac adapter that you have?
06-09. I attach a picture of it just in case.
Can you measure the no-load voltage from the adapter?
11.33V
Did you change anything else in the sketch?
I changed two things in the sketch. I changed Vcal in a desperate way to see some changes, it was due only to my level of desperation by not seeing any progress in over 6 hours. The second thing that I changed is RF69_COMPAT value to 0, because I am using an RF12.
Re: [SOLVED] Current Reading Issues
Hi Paul,
Tha thread was on other issue that was solved thanks to Robert's answer.
Regards,
NK
---
Re: [SOLVED] Current Reading Issues
When I went to the other thread I noticed something different about the output of the info send to the RPI through the RF12B.
The lines at the other post are in the following form:
10 199 247 0 0 0 0 0 0 64 98 0 0
And in the sketch that I installed in this emonTX (it is a different one), the lines are in the following format:
OK 10 201 55 20 65 42 62 0 0 3 126 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-74)
The sketch that I installed is the one from this link https://github.com/openenergymonitor/emonTxFirmware/blob/master/emonTxV3/RFM/emonTxV3.4/emonTxV3_4_DiscreteSampling/emonTxV3_4_DiscreteSampling.ino obviously with the changes on RF69 and Vcal.
Re: [SOLVED] Current Reading Issues
NK - I wasn't suggesting it was the same issue, just referencing the voltage readings and asking if anything had changed. I can see the sketch has changed by the number of variables in the payload but we cannot tell if it's the same emonTx and/or power supply arrangements.
If the power supply is able to connect to the mains either way round can you also try reversing the connection to switch the phase of the ac adapter. if 180° out wouldn't the effect of the rectifier impact the waveform differently?
Paul
Re: [SOLVED] Current Reading Issues
Your ac adapter is the Euro version (DE-), the nominal input voltage is 230 V, the no-load output is 11.5 V (±5%), so this is OK. Your voltage calibration for that should be 260.0
The value you have is wrong by 6%, not 36%, so there is something else wrong also.
RF69_COMPAT = 0 is correct for the RFM12B. (The sketch would lock up and not run if that was wrong.)
The extra data in your sketch is for 6 × unused temperature sensors plus pulse count (also unused?), so that is not the problem - not this one [those have caused other problems recently, so beware!]
The data (following "OK 10") are all signed integers:
power1, power2, power3, power4, Vrms, temp[6], pulseCount sent LSB first.
None of this explains why you are seeing ~300 V, I think you need to attach your sketch as you have it now so that we can do a line-by-line comparison. I suspect something has been changed by accident.
[Edit] Paul, changing the phase of the AC adapter is equivalent to flipping the CT's - it reverses the direction of real power.
Re: [SOLVED] Current Reading Issues
"10 199 247 0 0 0 0 0 0 64 98 0 0"
Is a packet from a single temperature sensor sketch the latest has provision for 6
"OK 10 201 55 20 65 42 62 0 0 3 126 0 0 0 0 0 0 0 0 0 0 0 0 1 0 (-74)"
Also has a "OK" prefix and a trailing RSSI, this tells us the later was recieved on a rfm69 equiped RFM2Pi or RFM69Pi or emonPi whilst the former was probally recieved on a rfm12 RFM2Pi.
the important difference is the values in bold 251.52v in the first payload and 322.59v in the second,
Paul
Re: [SOLVED] Current Reading Issues
Thanks again for your help guys. I attach the sketch so you can take a look at it.
Regards,
Nicolas
---
Re: [SOLVED] Current Reading Issues
I don't believe it - except for the Vcal value (which does not explain all of the discrepancy), it is identical to my saved copy.
There has to be a fault or a wrong component in your emonTx. I'll refer this to Glyn.
Re: [SOLVED] Current Reading Issues
Thanks Robert, it is indeed very strange, I thought the same because I have another emontx that has been working perfect for more than 6 months. Thanks for your help and I hope that Glyn has some idea of what could be happening and if it could have a solution.
Regards,
Nicolás
---
Re: [SOLVED] Current Reading Issues
Hi Nicolás,
It sounds like you may have a faulty emonTx unit. I'm very sorry about this. Please could you email<EMAIL_ADDRESS>and quote your original order number. We will arrange for you to be sent a replacement.
Very sorry for the hassle.
Re: [SOLVED] Current Reading Issues
Hi guys,
Just writting to let you know that I received a replacement emontxv3 and it worked liked a charm at it's first connection. The board was faulty. Thanks for the help, I'm renaming this as solved.
Regards,
NK
---


About ReSpawn™
ReSpawn™ is a non profit organization aspiring to raise awareness about the ill effects of suicides which seem to be growing at exponential rates, especially among youth.
We are here to provide help for those who need and long for it. According to a statistic report about 800,000 deaths occur due to suicides, that means there is a person committing suicide every 40 seconds and thats why at Respawn we are gonna provide a helping hand to the victims so that they can feel secure and move on with life normally as they once used to.
If you are reading this, just know one thing ~ Your Story isn't over yet because we don't quit, we ReSpawn™


Chris Keathley /
@ChrisKeathley
Brett Wise /
@BrettWise
Don't check your brain at the door
Users wait ~6 seconds before they bounce
Users wait ~3 seconds before they bounce


Notice: This site is currently under construction. Rusty Palette will launch an alpha in mid-december early January.
An overlay for Rust to give you a tactical advantage and improve Quality of Life without hacks!
Currently in development pending an early january Alpha launch
We will be releasing several hundred licenses over prominent community platforms in early january. Contact me on our discord server if you are interested in distributing licenses or if you would just like a personal key for yourself.


Return value for the diff* methods. Has show, as.character, summmary, [, head, tail, and any methods.
diff*
show
as.character
summmary
[
head
tail
any


The Toughest Historical Reenactment in America
For The Appendix’s second issue, I had the pleasure of interviewing Jackie Sibblies Drury, a writer and friend, about her play, We Are Proud to Present a Presentation About the Herero of Namibia, Formerly Known as South West Africa, From the German Sudwestafrika, Between the Years 1884-1915. The self-consciously long title, like the play’s wicked sense of humor, masks an incredibly sharp critique of the racial history Americans carry with them, even when they’re trying to reenact the history of ‘other’ countries. We talked specifically about the play’s ending, in which six black and white actors’ attempt to put on their own play about the Herero genocide ends in horrific failure. Seriously, it kills. (And is now playing in LA, through the end of the week. Go see it.)
Without giving too much of that ending away, I was reminded of Jackie’s play when a friend, Thomas Frampton, forwarded me this post from the blog Northwest History, about an incredible historical reenactment that’s been going on for nine years in Monroe, GA.
It’s called the Moore’s Ford Bridge Lynching Reenactment.
Let that sink in for a moment.
Colonial Williamsburg this is not.
In 1946, a white KKK-led mob pulled two black Georgian couples from the car of their white employer. One of the black men, Roger Malcolm, had stabbed a white man in the stomach eleven days before. The mob tied the men, and their wives, to a tree and filled them with sixty bullets. Malcolm’s wife Dorothy was pregnant.
The FBI came up with a set of suspects—Georgia’s governor claimed that 15 to 20 mob members were known by name—but the grand jury but failed to convict any of them. Today, the Georgia Association of Black Elected Officials brings together a group of white and black Georgians who take on the role of the black couples, the white employer, and the mob that lynched them, to reenact the event in Monroe and at Moore’s Ford Bridge. They hold the event to bring attention to the unsolved murders, and to maintain awareness of the crime. (Pictures from the era were re-discovered three years ago.)
Videos of the event, from this year and years past, are below, and not for the faint of heart. I find them phenomenally brave, though, and think they should be an inspiration to other activists and historians. In an age where zombie flash-mobs and ‘Thriller’ parades are de rigueur, what other more horrific real-life events could be reenacted, to challenge our communities and awaken sympathy?
And for this year’s reenactment (from which the screencap at top is taken) click through to here and here.


Woman accidentally shot by her son in Vancouver’s Oppenheimer Park, police say
Everyone involved, including the woman, not cooperating with investigators, VPD says
by Ashley WadhwaniThe person who shot the 53-year-old woman at Vancouver’s Oppenheimer Park last month was the woman’s son, police say, in what was likely an accident.
Charges are not likely, police said in a news release Friday, because the 53-year-old mother and her 30-year-old son are being uncooperative with investigators.
The woman turned up at a local hospital on Oct. 26, claiming she had been shot in the arm while sitting in a vehicle near the Downtown Eastside park, which has been the site of a growing homeless camp.
The woman, who is from Powell River, underwent surgery and is now no longer in the area, police said.
Investigators had identified her son as the suspected shooter and believe he accidentally discharged the gun while speaking to her.
He is known to police and was arrested about a week after the incident for a separate offence. During his arrest, police said they seized a gun likely involved in the shooting.
“Investigators worked diligently for the past month to solve this crime, which caused significant concern in the community and drew more negative attention to the park,” Sgt. Steve Addison said in a statement.
“Although we now know what happened, unfortunately everyone involved, including the victim, has been unwilling to cooperate.”
Police and other first responders have suggested the tent city is the reason violence and crime have been getting worse in the neighbourhood recently, despite a partial clearing in late September.
READ MORE: Officer assault, shooting at Downtown Eastside park spark concerns by police


reference to the tunnel credential or ssh credential used by the ngrok agent to start this tunnel session
unique tunnel session resource identifier
source ip address of the tunnel session
arbitrary user-defined data specified in the metadata property in the ngrok configuration file. See the metadata configuration option
operating system of the host the ngrok agent is running on
the ngrok region identifier in which this tunnel session was started
time when the tunnel session first connected to the ngrok servers
the transport protocol used to start the tunnel session. Either ngrok/v2
or ssh
URI to the API resource of the tunnel session
Generated using TypeDoc
version of the ngrok agent that started this ngrok tunnel session


| Class | Description |
|---|---|
| ClosureSignatureHint |
A closure signature hint class is always used in conjunction with the
ClosureParams annotation. |
| FirstParam |
A hint used to instruct the type checker to pick the first parameter type.
|
| FirstParam.Component |
A hint used to instruct the type checker to pick the type of the component of the first parameter type, which is therefore
expected to be an array, like in this example:
|
| FirstParam.FirstGenericType |
A hint used to instruct the type checker to pick the first generic type of the first parameter type.
|
| FirstParam.SecondGenericType |
A hint used to instruct the type checker to pick the second generic type of the first parameter type.
|
| FirstParam.ThirdGenericType |
A hint used to instruct the type checker to pick the third generic type of the first parameter type.
|
| FromAbstractTypeMethods |
This signature hint uses abstract methods from some type (abstract class or interface) in order
to infer the expected parameter types.
|
| FromString |
A closure parameter hint class that is convenient if you want to use a String representation
of the signature.
|
| MapEntryOrKeyValue |
A special hint which handles a common use case in the Groovy methods that work on maps.
|
| PickAnyArgumentHint |
Base class for hints which use the type of a parameter of the annotated method as the signature.
|
| SecondParam |
A hint used to instruct the type checker to pick the second parameter type.
|
| SecondParam.Component |
A hint used to instruct the type checker to pick the type of the component of the second parameter type, which is therefore
expected to be an array, like in this example:
|
| SecondParam.FirstGenericType |
A hint used to instruct the type checker to pick the first generic type of the second parameter type.
|
| SecondParam.SecondGenericType |
A hint used to instruct the type checker to pick the second generic type of the second parameter type.
|
| SecondParam.ThirdGenericType |
A hint used to instruct the type checker to pick the second generic type of the second parameter type.
|
| SimpleType | |
| SingleSignatureClosureHint |
A simplified version of a
ClosureSignatureHint which is suitable
for monomorphic closures, that is to say closures which only respond to a single signature. |
| ThirdParam |
A hint used to instruct the type checker to pick the third parameter type.
|
| ThirdParam.Component |
A hint used to instruct the type checker to pick the type of the component of the third parameter type, which is therefore
expected to be an array, like in this example:
|
| ThirdParam.FirstGenericType |
A hint used to instruct the type checker to pick the first generic type of the third parameter type.
|
| ThirdParam.SecondGenericType |
A hint used to instruct the type checker to pick the second generic type of the third parameter type.
|
| ThirdParam.ThirdGenericType |
A hint used to instruct the type checker to pick the second generic type of the third parameter type.
|
| Exception | Description |
|---|---|
| IncorrectTypeHintException |
| Annotation Type | Description |
|---|---|
| ClosureParams |
Parameter annotation aimed at helping the IDEs or the static type checker to infer the
parameter types of a closure.
|