search

LinkItONEDevGroup / LASS

Location Aware Sensor System by Linkit ONE
https://www.facebook.com/groups/1607718702812067/
MIT License
157 stars 77 forks source link

Blynk seamless integration #3

Open vshymanskyy opened 8 years ago

vshymanskyy commented 8 years ago

I see that you include a workaround for Blynk library:

#define ARDUINO 150 // to avoid Blynk library use yield() in function run(), without this. system will crash!

We at Blynk could integrate it into our library, but I need to now if there is a specific #define that is set only for LinkIt ONE, to detect this situation. Also, it would be good for us to get a device sample to do testing on our side. Whom can we contact regarding this question? Thx.

wuulong commented 8 years ago

Volodymyr Shymanskyy,

It's me, wuulong. Sorry for wait so long time to verify your new version. As current my understand, Blynk only need to avoid to use yield() when device type as LinkItONE. This work around should be able to remove, and others LinkItONE user will not get this trouble.

Personally, I agree that if you get one device and can be maintain this device in Blynk, that will be perfect. But I can't sent you device because I don't have more. I will post your request into the group in FB to see if someone can send you device. Let see if this work first.

10/3, The LASS demo Blynk interface in the Mini Maker Faire Hsinchu. Thanks your great job to make this possible.

Wuulong ps: this is the FB group, https://www.facebook.com/groups/1641811569367039/

On Tue, Oct 6, 2015 at 5:58 AM, Volodymyr Shymanskyy < notifications@github.com> wrote:

I see that you include a workaround for Blynk library:

define ARDUINO 150 // to avoid Blynk library use yield() in function run(), without this. system will crash!

We at Blynk could integrate it into our library, but I need to now if there is a specific #define that is set only for LinkIt ONE, to detect this situation. Also, it would be good for us to get a device sample to do testing on our side. Whom can we contact regarding this question? Thx.

— Reply to this email directly or view it on GitHub https://github.com/LinkItONEDevGroup/LASS/issues/3.

許武龍 ( wuulong ) 專業認證：IBM Certificated Linux Trainer for LPIC, Security Engineer(TWCERT/CC), JAVA Programmer(SCJP) Interest: Maker, Embedded System, Robotics

kg6hxm commented 8 years ago

I could send one from Denver. Where would it be going?

On Mon, Oct 5, 2015, 4:56 PM wuulong notifications@github.com wrote:

Volodymyr Shymanskyy,

It's me, wuulong. Sorry for wait so long time to verify your new version. As current my understand, Blynk only need to avoid to use yield() when device type as LinkItONE. This work around should be able to remove, and others LinkItONE user will not get this trouble.

Personally, I agree that if you get one device and can be maintain this device in Blynk, that will be perfect. But I can't sent you device because I don't have more. I will post your request into the group in FB to see if someone can send you device. Let see if this work first.

10/3, The LASS demo Blynk interface in the Mini Maker Faire Hsinchu. Thanks your great job to make this possible.

Wuulong ps: this is the FB group, https://www.facebook.com/groups/1641811569367039/

On Tue, Oct 6, 2015 at 5:58 AM, Volodymyr Shymanskyy < notifications@github.com> wrote:

I see that you include a workaround for Blynk library:

define ARDUINO 150 // to avoid Blynk library use yield() in function

run(), without this. system will crash!

We at Blynk could integrate it into our library, but I need to now if there is a specific #define that is set only for LinkIt ONE, to detect this situation. Also, it would be good for us to get a device sample to do testing on our side. Whom can we contact regarding this question? Thx.

— Reply to this email directly or view it on GitHub https://github.com/LinkItONEDevGroup/LASS/issues/3.

許武龍 ( wuulong ) 專業認證：IBM Certificated Linux Trainer for LPIC, Security Engineer(TWCERT/CC), JAVA Programmer(SCJP) Interest: Maker, Embedded System, Robotics

— Reply to this email directly or view it on GitHub https://github.com/LinkItONEDevGroup/LASS/issues/3#issuecomment-145692255 .

wuulong commented 8 years ago

Volodymyr Shymanskyy,

Great news! You got MTK Lab's donation. LinktITONE*1( at least ).
Please provide your delivery information ( Maybe send to

wuulong@gmail.com )

To make better support to you, I will provide the contact of MTK Lab to you.

This is my FB, you can add friend if you like. https://www.facebook.com/wuulong.hsu

I can feel we all thanks your work and hope you can continue to support LinkItONE.

Best Regards, Wuulong.

On Tue, Oct 6, 2015 at 6:56 AM, wuulong wuulong@gmail.com wrote:

Volodymyr Shymanskyy,

It's me, wuulong. Sorry for wait so long time to verify your new version. As current my understand, Blynk only need to avoid to use yield() when device type as LinkItONE. This work around should be able to remove, and others LinkItONE user will not get this trouble.

Personally, I agree that if you get one device and can be maintain this device in Blynk, that will be perfect. But I can't sent you device because I don't have more. I will post your request into the group in FB to see if someone can send you device. Let see if this work first.

10/3, The LASS demo Blynk interface in the Mini Maker Faire Hsinchu. Thanks your great job to make this possible.

Wuulong ps: this is the FB group, https://www.facebook.com/groups/1641811569367039/

On Tue, Oct 6, 2015 at 5:58 AM, Volodymyr Shymanskyy < notifications@github.com> wrote:

I see that you include a workaround for Blynk library:

define ARDUINO 150 // to avoid Blynk library use yield() in function run(), without this. system will crash!

We at Blynk could integrate it into our library, but I need to now if there is a specific #define that is set only for LinkIt ONE, to detect this situation. Also, it would be good for us to get a device sample to do testing on our side. Whom can we contact regarding this question? Thx.

— Reply to this email directly or view it on GitHub https://github.com/LinkItONEDevGroup/LASS/issues/3.

許武龍 ( wuulong ) 專業認證：IBM Certificated Linux Trainer for LPIC, Security Engineer(TWCERT/CC), JAVA Programmer(SCJP) Interest: Maker, Embedded System, Robotics

許武龍 ( wuulong ) 專業認證：IBM Certificated Linux Trainer for LPIC, Security Engineer(TWCERT/CC), JAVA Programmer(SCJP) Interest: Maker, Embedded System, Robotics