so we just bought a new coffe machine and we were about to throw the old one out and I thought it would be fun to see if I could automate it with my pi pico or rpi 4. the five springs correspond to the five icons shown in the last picture and by just touching the spring it is able to detect the input. I have no idea how this works and just tried hooking a gpio pin to the spring and turning the pin on and off but that ofc didnt work. So I was wondering if somebody could please explain how that works, I would be really interested to know. and if anybody has an idea how to simulate that input with a pico it would also be greatly appreciated! Thank you so much in advance! [
Related
I have a problem with my new bluetooth HC-05 module. In AT-mode it works perfectly with all commands that I need... exept INQ.
I have tried to send whole bunch of other commands beforehand:
AT+INIT
OK
AT+ORGL
OK
AT+ROLE=1
OK
AT+CLASS=0
OK
They all are working just fine. I tried to change IAC and INQM settings as well... but the answer from module is always the same:
AT+INQ
ERROR:(1F)
I read related topic here and tried to push the button at HC-05, as it recommended there, but -- no result either.
I have three modules from the same shop, and they all are working the same way
I have a HC-05 with 3.0-20170601 that I managed to bind to a slave last night. It turns out that the v3 has two AT-modes.
The first is when you hold the button while you connect power. The led will blink slowly and you can connect at 38400 baud. But this is like a configuration mode, where AT+INQ is not available.
In this mode I did these commands:
AT
AT+UART
AT+RMAAD
AT+ROLE=1
(Press and hold the button)
AT+RESET
(Release the button after device restarts and led is slowly blinking)
AT+CMODE=1
AT+INQM=0,5,5
AT+PSWD="9999"
AT should give OK as answer to know connection is working
AT+UART will show configured baudrate. Default is 9600.
AT+RMAAD clears all saved connections
AT+ROLE=1 sets it as master
AT+RESET restarts the device to change to master
AT+CMODE=1 accepts all kinds of devices
AT+INQM=0,5,5 inquires in standard mode, with 5 max connections or 5 secs
AT+PSWD="9999" sets the pin code 9999, change to the pin you need
After this it is time to update the arudino code so that it connects to the configured baud rate. It will be something like
BTSerial.begin(9600);
...or what ever value you might have set the baud rate to. Then reflash your arduino.
Now enter the very irritating second AT command mode.
Power up without holding the button. You will get the fast blink speed. When its powered up, press and hold the button. The led will continue blinking fast, but while the button is pressed you can now connect to the device on the configured baud rate. So open the serial monitor and type AT to verify.
Remember that the mode is only active while the button is pressed. So keep it pressed. I had a small clamp I put on there.
Then I entered these commands:
AT+STATE
AT+STATE will show current state, should be inquiring
Then power up the slave device and the adress should start popping up. It will be something like xyz:xy:xyzw,931F00,7FFF
The first part is the address you want (xyz:xy:xyzw)
Change : to , and get xyz,xy,xyzw
Check that you connecting to the correct device
AT+RNAME?xyz,xy,xyzw
Then bind
AT+PAIR=xyz,xy,xyzw,5
AT+BIND=xyz,xy,xyzw
AT+LINK=xyz,xy,xyzw
The AT+LINK command gave me FAIL as output. But it did not matter.
I restarted and did not press any button before or after. Just normal start.
After 5-10s serial data showed up in my serial monitor.
Modules are bound. And will automatically connect at power up. If not you might have the wrong pincode. Make sure to change 9999 above to 0000 or 1234 or what ever it may be. When I hade the wrong pin I still got OK from the AT+PAIR and AT+BIND commands... It didnt work for me until I entered the correct pin.
Sorry for long post, but I wanted to be thorough since info about HC-05 v3 is very scarce on the internet right now.
A reference to all commands can be found here:
http://www.electronicaestudio.com/docs/istd016A.pdf
(Link valid 2018-08-13)
We have same problem and you can see the answer in here.
The conclusion of problem is about the firmware on HC-05 you use. If you use firmware version 3.0, you will get error 1F in AT+INQ. Maybe HC-05 with firmware version 3.0 has different parameters to run AT+INQ. Now I'm confused about how to find HC-05 with firmware version 2.0. That HC-05 have push button or not.
In short, the answer is: The (B) module with firmware version 2.0-20100601 works ok with the following commands (set PIN34 high at power-up, or press button on module and keep pressed during commands).
So HC-05 with version 2.0 use push button or not, it's the same.
If you have some information about the different between HC-05 version 3.0 and version 2.0, please let me know.
I need to make screenshot of BIOS Award 1984-2009 F8 setup for my Project without using devices like camera. Is there any way to do it? I tried some emulators, but they won't work.
In some UEFI putting an USB key and pressing F12 works. Hope it helps one person at least.
First off, I hope this is the right place to post this. I am new, and Stack Exchange was the first site I thought of for this question. After reading the "How to Ask" page here, I don't see a better place. Let me know if I'm missing something and there's a place more suited for this question.
My question here, with background info below: Does anyone know how to use only pitch and roll for a mouse in GlovePIE, without yaw and IR?
Background: basically, I want to use my wiimote for mouse + WASD for PC gaming, but I cannot use an IR sensor bar. (I am CADding around the wiimote for a project and this material will end up obstructing the signal.) I have at my disposal: an RVL-036 wiimote and a broadcomm bluetooth dongle with a hacked Toshiba stack, a used RVL-003 wiimote I bought when the 036 didn't pan out, Wiinremote, and GlovePIE.
GlovePIE doesn't work with the 036 wiimote, and neither does Wiinremote even though I expected it to. With the 003, Wiinremote gives me perfect mouse movement using pitch and roll (I hear yaw needs an IR sensor). The problem is: I can set keys in Wiinremote such as Up on the D-pad to W on the keyboard, Left to A, and Down to S, but they only work in web browsers and such and not in-game.
My focus is now on GlovePIE scripts because I hear it does a good job in-game getting wiimote buttons to act as keyboard keys. (I first tried lednerg's motionplus script, but obviously I get "motion plus NOT DETECTED" in the debug field. I can click with the script running, but I just can't pan the cursor around.) I have looked around for mouse scripts so that I can add my own WASD key assignments, but every script I have found uses an IR sensor bar. I know it must be possible to use only roll and pitch for a mouse in GlovePIE--because Wiinremote handles it beautifully--but I have unsuccessfully tried looking for wii-specific GlovePIE tutorials and I don't understand the general syntax or how to call on the wiimote in GlovePIE.
I basically want to do exactly what Wiinremote does but in GlovePIE in the hopes of getting keys to work in-game.
My question: does anyone know how to use only pitch and roll for a mouse or know how I can familiarize myself with GlovePIE's language to do it myself?
Thanks.
Thanks, nwk and Tim. I posted on Super User. But I think I just answered my own question anyway. I found a stupidly simple solution: run GlovePIE and Wiinremote simultaneously, GlovePIE for buttons and Wiinremote for the mouse. facepalm
GlovePIE's syntax seems simple enough from others' button assignment scripts, as long as I stay away from mouse scripting.
A question that I have been asked by a professor? Not looking for someone to give me a direct answer but more an idea of how to answer as im quite confused by the Question?
Thanks
Assuming you're talking about the common Computer Pointing Device, not the rodent:
Imagine grabbing a brand new mouse hot off the factory assembly line. You want to test this sample mouse to make sure it functions correctly to the full satisfaction/expectation of whoever's grandma is gonna buy it.
How exactly would you test it? After doing what exactly would you conclude with 100% confidence that "OK, this mouse is perfectly good, no problems at all in any situation!" ?
You might plug it into a computer and see; does it get detected right away? Does it automatically setup the driver? Does it move around well? Does it click well? What if you're using Windows XP? What about Linux? What about inside virtual machines? What about with a USB extension wire? All of these "What If"s are called test cases; cases / situations that you'd want to test for to make sure the mouse works as expected even in that case / situation.
You can also test through..
1) which is the manufacturer company of that mouse
2) Is it required mouse pad ?
3) Is it wired/wireless mouse
4) maximum distance between mouse & device(Wireless mouse)
5) you can also check that "mouse can connect with more than one device same time.."
6) apple's mouse doesn't work in windows device...
I want to know based on kinect for windows SDK 1.7, which have grab function under the InteractionFrame.
Is it possible to only use one hand only eg: right hand only grab?
I had try to make it only 1 hand detect (right hand), but it seems that there is some sort of ghost mouse when i move my left hand.
this is what i had tried:
playerInfo.HandPointers[1].HandEventType == InteractionHandEventType.Grip
but stil there is another pointer merely visible.
thank you very much.
Tlga, I am having major problems setting up the interaction events in my program. Is there anyway you could help me since it seems as though you already have these in place.
I am about to pull my hair out
Ben
Chefbennyj at gmail dot com