Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - Wayne

Pages: [1]
1
Support / Tilt Sensor
« on: September 05, 2017, 12:13:14 PM »
Ok all,  I need to put in a tilt sensor (not mercury type or the roller ball)
I was thinking adxl335..  Use 2 lines to check up vs down.  If I recall, the values will pulse when the condition is hit. 
Like if I rotated upside down, X will lets say raise while Y lowers. and vis versa for the opposite.
Need to do this if the product FootSwitch flips over and presses any of the X-Ray foot pedals.

Thinking of getting the ADXL335 to try..  Thoughts..

Wayne

2
Support / SimbleeOff
« on: August 22, 2017, 09:18:04 AM »
Ok, I'm trying to achieve something that maybe I can not.

What I have found out that the use of SimbleeOff() does not really require the Simblee_pinWakeCallback() to work.
Providing you have Simblee_pinWake setup, the SystemOff() still functions.  I have tested this and it works just fine.

I'm using the old if(digitalRead(button)) with a normal callback function.
In the callback function I send my bluetooth stuff and when the button goes LOW, reset the pinWake and do the SystemOff() (My test is Normal LOW and HIGH is active.

I have no SystemOff() in the loop..  Only in the voids. 
In the loop I have the if statements to test the digital inputs as stated above.

Now I need to test 2 buttons at once and perform 2 BT signals.
One of the buttons is ,, well let me explain the buttons I have
buttonA is Save  This send just a simple character lets say S
buttonB is Mode and this lets say is M
buttonC is High Level X-Ray and just say its H
And buttonD is X-ray and lets just say X

These buttons can function as a singular item  Press Save, sends S, Press Mode and Mode and sends M and the others the same, HLF (HLX) send H and likewise X-Ray sends X.
This all works and it works well.  When the buttons are release, the current draw goes to 400na...4ma 

One feature that is needed is to do a Save while doing an X-ray.  So while X-ray is press, pressing the Save will need to send S along with X.
Likewise, if doing the High Level one, pressing Save I need to send the S as well as H.

I'm working currently with the H and S part and I see I can have the S sent, but it is not every time.

The 400na is the plus I do not want to loose it.
I can if requested post the complete program if needed. or parts.

Like I said its a WIP for me with my very limited knowledge of programming (just enough to get in trouble).

3
Support / Reading Battery with out DC-DC converter.. (Battery use only)
« on: August 18, 2017, 08:08:41 AM »
Figured I asked after looking over the forum.
I have decided to drop the DC-DC converter that is used to supply the Simblee with 3.3v while on batteries...  Used it for powering LEDs etc.
But the trade off of being in ULP and the device proved that it would draw around 10ma or more in idle and goes up as the batteries sour.

So I'm now using just using batteries (2 AA's) to power the Simblee and knowing that the Simble stops around 1.8volts, I need to do a warning (LED) to have batteries replaced (2.2v or so).
The warning will be a red led on the sender (Footswitch) and on the receiver.  The receiver will store the  last condition to display if power off and on again and will update when fresh batteries are installed.

The one option I'm using is the one posted long ago.. by mkay

Quote
analogReference(VBG); // Sets the Reference to 1.2V band gap           
analogSelection(VDD_1_3_PS);  //Selects VDD with 1/3 prescaling as the analog source
int sensorValue = analogRead(1); // the pin has no meaning, it uses VDD pin
float batteryVoltage = sensorValue * (3.6 / 1023.0); // convert value to voltage
Serial.println(batteryVoltage);

But the data differs as it is reporting.

If not, I will stay with this and just trigger the LED using it.

I do like the 400na draw in Simblee OFF .. And the fast response when active.

And I see that if you have the serial connected, it causes resets..

4
Support / Switch Case vs IF's
« on: August 09, 2017, 01:30:24 PM »
With the help of Patty, Aaron and all here, Thanks.. I have basically finish the Wireless Foot Switch 1st phase with demo boards and software.

Using the Simblee under SimbleeCOM, I have pairing, Pulse, Battery tests, and even WDT on the receiver side.

Now to the question.. I'm trying not to have lots of stuff like LED's on or having a Solid State Relay active via the loop function.  Like in the IF statement, if some == this, do a HIGH..

So I have create the switch case whereas case 51  if passthru == 0, void to turn on led and pasthru =1.
I do a timeout if I loose BT signal or an end of action sent via the Foot Switch as endsend which is 69.

I was thinking that once the case 51 and passthru == 0, it will skip and the void will still have the led on.  When either BT dies via a loss of BT or the case 69 recvd, I drop all stuff
via another void.

If it was under the if statements, it will have lots of workings going on in which in my thinking, slows the loop down somewhat.

I was hoping the speed of this will keep the SSR's on when required with lets say, no flicker.. Unlike a regular relay that is slower in reaction..
But as the systems go, they use micro switches originally which can jitter.  So maybe I'm safe..

Educated guess is I'm fine without having a tiny bit of chatter..

5
Support / Simblee_systenOff();
« on: June 12, 2017, 12:48:40 PM »
Does any know how fast wake up is on Simblee_systemOff(); is.. 
I thought it was over 100ms..  Like it to be around 30ms if possible.
Doing ULP delay now, but like to get into that DEEP SLEEP..

6
Support / Pulse output in receiver
« on: June 08, 2017, 07:36:34 AM »
Ok, I don't think it is possible, but, my knowledge is limited on this..
What I'm trying to do is using a device (footswitch button) in transmit to a receiver.
The receiver should only act once with a pulse of 350 ms and not to occur again during that current send of the footswitch, but if the button is released and pressed again, it should
pulse once more and not to do it again until a new send is sent.

I have tried doing toggles and all, but I get my pulse, but it repeats if I hold button closed.

I'm really do not want to do this on the send side, but if I need to, so be it..

So if anyone has a pointer, let me know please.
In the mean time, I will keep plugging at it..

Also, is their a simple debounce routine.. right now I'm just doing a woke option.. and HIGH tests on GPIO's
Working ok for testing.. 

Wayne

7
Support / Power cunsumption on 2 AA 2500mAh batteries.
« on: May 26, 2017, 01:45:48 PM »
Today is not my best day in math..  And I have tried to reason this out to find how long the 2 Alkaline Batteries will last as directly connected to a Simblee in ULP.

Scenario is:
SimbleCOM:
Pressing the button to wake up the Simblee from ULP, full rf power drawing 14mA.
Time is on a 8 hour day, the button will be pressed intermittently for a total of 18.4 mins. or 2.3 mins every hour. The no button pressed for 16 hours.
The batteries have a capacity of 2500mAh.
No Bucky in use, just straight to the Simblee for power. No LEDs'  Button and supported parts.


8
Simblee Libraries / Simblee_systemOff();
« on: April 19, 2017, 02:52:53 PM »
Ok, I'm playing around to see how fast Simblee_systemOff(); responds to a pinwake action, and can this be used in SimbleeCOM or is it just for SimbleeBLE?

Doing my elephant count, it is more than 1, but less than 2 .. 
I'm trying to get below ULP mode.. That draws around 1 ma, the systemOff is around 10ua

9
Hi,
I'm planning on using either of the 2 products in a new production of our current Wireless (Bluetooth RN42) product. Actually it is a 3rd version since introduction, but thats on the sales side.

What we do is mimic a medical footswitch and or handset unit using BT.
The actions are (depends of the x-ray system) Save or mode (save being a one time pulse per press) and or X-ray or Hi-Level x-ray (these use a security closure as well).
I have written code using arduino under the Teensy devices.  All pass are are out in the field.
Yes, we need to certify these, but in time. 

Reason the newer system is for battery use.  We want to get away from chargers and Li-Ion batteries which currently we need to go through hoops to qualify.
Also, the RN42 and current system kills batteries in less than 40 hrs.

Le can now use alkaline batteries and not worry over Fedex issues.  And low power is also a nice item (need less that 20ft.)
Our current BT module setup is 1 for FS, 1 for HS and 2 for the receiver.

If I understand correctly, I could make one unit Simblee or RFDuino a Master or central ?? and the other as slave or peripheral ??

Since the HS and FS mimic each other.

Since I do not have my stuff yet (kits and all), I like to find how to connect the units easily for production.
We program the FS/HS under one freescale and the recvr on another. The other programmers had selections for functions etc.
They can flip banks of switches to do certain functions, but most important is getting the BT modules to talk. When the link, the BT led lites.  They do FS first and then HS next to the recvr.

I'm hoping I can do this and lock out other BT devices. 

If someone can point me to where to look so I can start thinking on how to program it, be great.

And if I recall, the devices have AES security.. But if we lock it down, should be good too..

Pages: [1]
anything