Recent Posts

Pages: [1] 2 3 ... 10
1
Support / Re: hand soldering Simblee module?
« Last post by Johnny1010 on July 26, 2017, 01:56:29 PM »
Guys a quick question, what temperature are you using for the hot air gun. When soldering from the top, for any other IC, I use 350 Celsius and a medium air flow. Is this fine for Simblee as well?
2
Bugs / Re: required SimbleeForMobile configuration
« Last post by tolson on July 25, 2017, 09:24:02 PM »
This happens when the cache is out of date.  Close the simblee app on the phone and restart
Not that simple. Been there, done that, didn't help. Often took several repeats including power off and on, etc.
And then worked until the next time. May or may not have been fixed since then.
3
Simblee For Mobile / Re: updateRect() causes Android App to Crash
« Last post by AKotowski on July 25, 2017, 08:31:52 PM »
Yes, adding the second color parameter allows the program to work
4
Bugs / Re: required SimbleeForMobile configuration
« Last post by AKotowski on July 25, 2017, 08:27:12 PM »
This happens when the cache is out of date.  Close the simblee app on the phone and restart
5
Simblee For Mobile / Re: updateRect() causes Android App to Crash
« Last post by RFD_Nelson on July 24, 2017, 05:25:38 AM »
Hi AKotowski,

Can you please try changing this line:
Code: [Select]
ss = SimbleeForMobile.drawRect(80, 300, 150, 50, RED); to this:
Code: [Select]
ss = SimbleeForMobile.drawRect(80, 300, 150, 50, RED, RED);
and then removing the updateColor() line from the loop()?

Thanks,

Nelson
6
Support / Erratic behaviour when connecting to device
« Last post by jetty on July 22, 2017, 11:56:43 AM »
If you're experiencing erratic behavior when connecting to the Simblee, here's something I found out the hard way.

ui(), ui_event are called from within SimbleeForMobile.process()

However SimbleeForMobile_onConnect() and SimbleeForMobile_onDisconnect are called asynchronously, presumably they're interrupts. (I couldn't find this documented anywhere).

If you're changing any variables for example in onConnect/onDisconnect, which you're also changing from loop(), you'll need to be aware they could change under you.

Also, it's common in the Simblee documentation to see this:
Code: [Select]
void SimbleeForMobile_onConnect()
{
  Serial.println("Mobile connected");
}

which will lead to random corruption of your serial stream.  It may effect other SimbleeForMobile callbacks too, I haven't verified all of them.
7
Simblee For Mobile / Re: updateRect() causes Android App to Crash
« Last post by AKotowski on July 20, 2017, 10:27:29 AM »
Yes, updateW() solves my problem.
The app crashes regardless of the update frequency, even if updateRect() is only called once.
Thanks for your help
8
Interesting Uses & Applications / Simblee Flash Read/Write wrapper library
« Last post by blieber on July 20, 2017, 09:22:11 AM »
I wrote a FIFO-ish interface to make it easy to write to and read from flash memory on Simblee - https://github.com/blieber/arduino-flash-queue
9
Support / Re: dualMode for BLE+COM
« Last post by Tim on July 19, 2017, 11:15:56 PM »
I have clarity on this, thanks for replies from RF Digital support. This supplements info at:

http://forum.rfduino.com/index.php?topic=1357.0

When Simblee is connected to a BLE central and is in dualMode, it gives 10 ms slices of time to COM. This is enough time to send a COM message in LOW_LATENCY mode (3 ms latency) and receive an immediate reply from a receiving Simblee. Therefore, dualMode works only for LOW_LATENCY COM.

The only configuration of Simblees that dualMode works for is where you have one Simblee acting as a gateway, and one or more as nodes. The gateway can be connected to a BLE central and, via dualMode, also do COM messaging with one or more nodes. The nodes must use straight COM; they cannot maintain BLE connection. AND, while a COM message sent from the gateway (in between calls to its SimbleeBLE_onDualModeStart() and SimbleeBLE_onDualModeStop() routines) is broadcast to all nearby Simblees with COM stack started, only a single node can reply to the gateway, and it must do so immediately so the reply message reaches the gateway before the end of the 10 ms COM slice in which the original message was sent from the gateway.

This limits the use cases for Simblee's dualMode, but I can imagine there are many where it is very useful.

Hope helpful ...

Tim
10
Simblee For Mobile / Re: updateRect() causes Android App to Crash
« Last post by AKotowski on July 19, 2017, 03:54:52 PM »
Thanks
Pages: [1] 2 3 ... 10
anything