Sparki routine begins on it's own?

Sparki
#1

I’m not sure of the language I need to use to describe this phenomenon, so for lack of search terms I’m posting here, perhaps someone can enlighten me. I opened my Sparki today, added batteries and tried out the remote. It works mostly, short of an odd bug that already has a thread on this board.

I was surprised when the Sparki, after sitting idle for a few minutes suddenly began the object avoidance routine - wandering about on it’s own. I didn’t press any button on the remote, it seemed to begin spontaneously. Is this expected behaviour?

Thanks!

#2

Hi Jake. No, shouldn’t just start on it’s own.

The default out-of-the-box program (or “sketch”) that’s loaded on Sparki is for the Remote & Wall Avoidance however, so hence why both programs ran for you. Not sure why the delay though. Has it happened that way since?

#3

Thanks Trevor. When I turn it on, it begins the wall avoidance routine. However, if I use the remote at all, it doesn’t begin the wall avoidance immediately, but does start after it’s been sitting idle for a while. Sounds like this is intended default behaviour?

#4

Hey Jake. I uploaded the “Default” sketch that was put into the github last week. Not sure if it’s exactly the same as what came pre-loaded on your Sparki, but I think it is. Anyway, I wasn’t able to replicate the issue you saw with the Wall Avoidance starting back up on it’s own after a period of being idle.

I looked through the code also (and though I’m definatley no expert) & I couldn’t see any time out or delay function to start Wall Avoidance when idle for a period. Sorry, I’ve got no answer for you.

#5

I appreciate the effort. I’m now wondering if perhaps power is being cycled somehow resulting in the sparki “rebooting” sporadically, as it does not seem to be a consistent amount of time after the last remote command before it starts the wall routine. I’ll have a close look at the connections, and if I don’t find a clue I guess I’ll have to sit and stare at it for a while to see if I can catch the LED going out.

#6

Ah. Maybe you have something there. Did you use new batteries? Think I saw some bit of code somewhere for a low voltage.

#7

Yep, new and freshly charged non-Alkaline rechargeables as per the instructions (NiMH). However I’m now reading on another post that there is no charging feature via the USB connection so I’m wondering why non-Alk rechargeables are specified in the first place. I’ll put some regular batts in and see what happens.

I did notice that if I turn the sparki over and back quickly it begins the wall routine, so I suspect something is loose or not properly soldered but again, it doesn’t happen every time. Intermittent bugs like this are very frustrating. The bluetooth board had to be hard up against the LCD when installed, hopefully I haven’t damaged something plugging the BT board in. I should bend the pins to give it an offset.

#8

Just found out that the Sparki IR Remote has the same key codes as my Nixie clock that I built as a kit. The clock also has an Atmega “Arduino” chip. Wondering if in your case there is a similar remote nearby that triggered Sparki to start the programmed routine.

#9

With “Restore_Default” uploaded into Sparki, I also tried some of the IR remotes I have here at home and found that majority of the keys on my OPPO Digital Bluray player also triggers most of the functions on the Sparki. Again, it could be another IR remote in your home that’s triggering your Sparki.

#10

Aha. Yes there’s a good possibility that’s part of the problem. I was wondering about that too but hadn’t had a chance to test yet.

#11

There is a solution Jake…stop everybody watching TV while your playing with Sparki :smiley:

#12

Haha. I guess I’ll have to supe up sparki’s entertainment potential!