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.

Messages - Wayne

Pages: [1] 2 3
Getting Started / Just a little info about Sparkfun
« on: October 17, 2017, 01:37:22 PM »
Hi all,

Sparkfun had a limited supply of RFD77101 a few weeks back.  I needed some to do some demo boards and thought I get 10.
I had 6 boards made and 4  are bad.  Some will report back the PID and all but not program
1 Gets hot and the other is shorted.

These cam package in clear plastic sealed bags that did not look anti static.
Fortunately, I have 3 from Digikey that I can get 3 out of boards repaired.

Support / Re: An observation on Simblee power consumption
« on: September 25, 2017, 06:54:23 AM »
I have worked with ULP and systemoff options a lot.

During the 100ms delay, you will draw 16ma.. That is normal for full power.
Since you are not doing any sleep, the simple will idle at a higher rate.

In the android world, I have learned that delay() is a no no.  It stops all programming routines until done.  I use elapsemillis (exact name?) to delay.

With systemoff, I do see 400nA when in the lower power.

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


I was curious about the 1.8.7 stuff. As it turns out it is an Windows App Store store app.  It shows up as 1.8.4 when launched.

I rather do the desktop one, much quicker to load and no windows hassle.

I suggest killing the windows app one and get the original from

Is GPIO pins 0,1 for serial programming.. They connect to the USB program module that way?
I never used GPIO 0 nor GPIO 1 at all.. I Leave em alone..

Support / Re: OTA upload hang with IOS-Pods-DFU-Library
« on: August 28, 2017, 02:41:29 PM »
Dunno if this makes any sense, but the start of the 2 are different..
A states Wire in folder the SimbleeBLE in folder while
B states SimbleeBLE in folder then Wire in folder..

Thats the difference is see..

But I don't do this, just looking at what you posted..

Support / Re: SimbleeOff
« on: August 25, 2017, 12:53:25 PM »
Ok, I had Aaron's help and found that I have a digitalRead on a pin checking LOW condition in the HIGH test. If the button went LOW, it will most likely miss the LOW test routine.
In other words, I had to place the check in the loop where it will get caught.

Everything is working.  Also solved the button issues.  If the button is depress (HIGH), no other button will try to take control.  No blanking out or anything.

Project has moved to Release Candidate and in a demo for next week.

And now another project doing the same.. This time it will be easier except need to add an accelerometer to detect if the foot switch is upside down or right side up.

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

For IDE, use the latest..  Arduino IDE
Follow the online or PDF instruction. or look up 
Special characters I don't understand.. But you could get an answer.
The product is new.. just a few years old and I'm sure it will last for sometime.  I think they have put some effort into the product to not to have it go away in a year or so. The RFDUINO is still here.
I'm in the mist of prototyping as well but has come to the point that we had to get outside engineers to help with my workload.
No royalties as far as I know.  The IDE and libs are for the product and are free.
Maybe the FCC ID might be needed to be somewhere. My product will not only be used in the US, but Canada, Europe, Australia and Japan off hand.  So we will be doing FDA and UL stuff.

People here will help you out greatly on the project you are doing.
I'm not the best programmer for Arduino, so I look here for help and from Simblee as well.

Support / Re: Simblee getting input voltage
« on: August 18, 2017, 12:43:45 PM »
Hi Tolson,

Yup exactly what I'm getting..  Depends on what the simblee is doing.. My case, I read the values and lite an led if the voltage is around 2.1 volts or less (1.8 is the min for simblee) and I
send this date divided by 4 to the receiver and multiply it by 4.. So a little difference here.

I'm using Simblee Off routine.. So the current draw is 4na (confirmed when asleep) and wakes up pretty fast.

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

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

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

Support / Re: Simblee getting input voltage
« on: August 18, 2017, 07:46:52 AM »
Has anyone fix the wide range of differences?

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

Support / Re: Pulse output in receiver
« on: June 22, 2017, 08:37:33 AM »

I'm sure I can do this on the footswitch (send) side, but I have it working on the receiver side at the moment.

Aaron helped me with the sample, then I was able to insert it with changes to accomplish the goal.
I'm not to sure about the timing, but it looks close to what I need.

The Objective is to receive the signal (button send from the footswitch) and enable a relay (led) for x seconds (200ms roughly).
Do this once and not to repeat until the next signal was received.
Make sure the pulse is equal to 200ms no matter what length of the trigger.

Here is the code in the loop area of the receiver for the foot switch.
Code: [Select]

if (modeRecvd == 0 && button == 50) //case 50:
    // mode
    modeRecvd = 1;
    lastRecvd = millis();
    digitalWrite(mode_led, HIGH);
    digitalWrite(save_led, LOW);
    digitalWrite(xray_led, LOW);
    digitalWrite(HLF_led, LOW);
    digitalWrite(security_led, LOW);
  } else {
    if (modeRecvd == 1 && millis() - lastRecvd >= 130)
      digitalWrite(mode_led, LOW);
      lastRecvd = millis();
      if (button == 69)
        modeRecvd = 0;

It also works as a send (foot switch)

I had a hard time trying different ways of doing this.

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

Pages: [1] 2 3