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 / 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..

2
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..

3
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

4
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.


5
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

6
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