Hello.
I'm trying to get the following to work on the Crickit and I'm having problems. When I turn the Crickit on the Pixel 0 on the CPX starts flashing between red and green for a few seconds then stays green. The button plugged into the Crickit isn't pressed. The button works just fine when hooked straight into the CPX.
This happens with multiple buttons, on all the signal ports, with different CPXs, on battery power and wall wart.
The CPXs work fine on their own. I've updated the Crickit and CPXs.
I can control the Crickit Neopixel from the CPX just fine. The Crickit speaker works fine.
When I plug the CPX to the computer and the Crickit is off Pixel 0 on the CPX stays on like it's receiving signal from the Crickit.
The CPX is not loose and there isn't anything caught in the screws.
I can't think of anything else to try.
Any advice is welcome.
I'm hoping I don't have to return it, shipping it back might cost just as much as the Crickit itself.
Video
Thanks.
Crickit Signal Problem
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
- jorge77
- Posts: 18
- Joined: Sat Nov 25, 2017 3:21 am
Re: Crickit Signal Problem
A bit more info.
The Makecode signals demo makes the LED flash constantly. Doesn't matter what the button does.
The CircuitPython signals demo seems to work ok.
The Makecode signals demo makes the LED flash constantly. Doesn't matter what the button does.
The CircuitPython signals demo seems to work ok.
- adafruit_support_carter
- Posts: 29483
- Joined: Tue Nov 29, 2016 2:45 pm
Re: Crickit Signal Problem
Can you "share" your project and post the link back here? I'll test it and see if I can repeat the issue.
- jorge77
- Posts: 18
- Joined: Sat Nov 25, 2017 3:21 am
- adafruit_support_carter
- Posts: 29483
- Joined: Tue Nov 29, 2016 2:45 pm
Re: Crickit Signal Problem
I think this is an issue with having a floating input with your button. Can you post a photo showing how you have the button connected. Do you have any breadboard wire - like the short little lengths used for making wire connections on breadboards?
- jorge77
- Posts: 18
- Joined: Sat Nov 25, 2017 3:21 am
Re: Crickit Signal Problem
I will try some more CircuitPython demos tomorrow (1am now). The CP Signal demo worked fine but want to make sure. Also servo test. I think it might be a Makecode problem.
- jorge77
- Posts: 18
- Joined: Sat Nov 25, 2017 3:21 am
Re: Crickit Signal Problem
I tried with multiple buttons and it worked in CircuitPython. I will send some pictures of the connections tomorrow. It is 1am here.
Thank you for your help so far.
Thank you for your help so far.
- adafruit_support_carter
- Posts: 29483
- Joined: Tue Nov 29, 2016 2:45 pm
Re: Crickit Signal Problem
I can recreate your issue here. But also solve it by dealing with the floating input issue externally. If it's a Makecode issue, it's just a matter of figuring out how to enable internal pull ups.
- jorge77
- Posts: 18
- Joined: Sat Nov 25, 2017 3:21 am
- adafruit2
- Posts: 22200
- Joined: Fri Mar 11, 2005 7:36 pm
Re: Crickit Signal Problem
oof it looks like we forgot to add pullup support to makecode. we'll do that next week!
for now can you put a 1K-100K resistor from your signal pins to 3V?
i will have a slight warning that signal input on makecode with CPX is a little flaky because of a bug in a low level seesaw+i2c protocol thingy and if you can use arduino or circutpython for Crickit Signal input you'll be happier in the long run.
OR you can alligator clip to the CPX pads and use those as signals and they'll work perfectly in makecode
for now can you put a 1K-100K resistor from your signal pins to 3V?
i will have a slight warning that signal input on makecode with CPX is a little flaky because of a bug in a low level seesaw+i2c protocol thingy and if you can use arduino or circutpython for Crickit Signal input you'll be happier in the long run.
OR you can alligator clip to the CPX pads and use those as signals and they'll work perfectly in makecode
- jorge77
- Posts: 18
- Joined: Sat Nov 25, 2017 3:21 am
Re: Crickit Signal Problem
Yes, I can use a resistor or use the CPX pads instead.
Thanks for your help!
Thanks for your help!
- blinkentown
- Posts: 10
- Joined: Fri Oct 27, 2017 9:16 pm
Re: Crickit Signal Problem
"quote="adafruit2"]oof it looks like we forgot to add pullup support to makecode. we'll do that next week! "
is there any feedback on this ?
"i will have a slight warning that signal input on makecode with CPX is a little flaky because of a bug in a low level seesaw+i2c protocol thingy and if you can use arduino or circutpython for Crickit Signal input you'll be happier in the long run. "
does that mean the "i" side of the crickit i/o block is without function under makecode / cpx?
thanks for an update
cheers,
dhani
is there any feedback on this ?
"i will have a slight warning that signal input on makecode with CPX is a little flaky because of a bug in a low level seesaw+i2c protocol thingy and if you can use arduino or circutpython for Crickit Signal input you'll be happier in the long run. "
does that mean the "i" side of the crickit i/o block is without function under makecode / cpx?
thanks for an update
cheers,
dhani
- adafruit2
- Posts: 22200
- Joined: Fri Mar 11, 2005 7:36 pm
Re: Crickit Signal Problem
dhani, we didn't get to adding the pullup capability - and we're not sure when we'll get to it :( for now please use an external resistor!
makecode input block is not consistant right now - we don't have a fix yet but it is being worked on!
makecode input block is not consistant right now - we don't have a fix yet but it is being worked on!
- blinkentown
- Posts: 10
- Joined: Fri Oct 27, 2017 9:16 pm
Re: Crickit Signal Problem
hej ada2,
thanks for your reply... no good news...
so next step is circuit python if the i/o is needed?
cheers,
d
thanks for your reply... no good news...
so next step is circuit python if the i/o is needed?
cheers,
d
- adafruit2
- Posts: 22200
- Joined: Fri Mar 11, 2005 7:36 pm
Re: Crickit Signal Problem
yes! please try circuitpython or arduino!
Please be positive and constructive with your questions and comments.