Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
IR sensor doesn't respond to toggling off the "beacon" button
See original GitHub issue- ev3dev version: 4.14.58-ev3dev-2.2.1-ev3
- ev3dev-lang-python version: python3-ev3dev2
Code: https://gist.github.com/Uldiniad/2608aa8e4a152fe443b151f0d6c5e08b Output:
// Clicked beacon (runs medium_motor forever)
WARNING:root:State: True
WARNING:root:Running hand_motor forever
// Pressed touch sensor (stops medium_motor)
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
// Press any other button than beacon (runs large motor until released)
WARNING:root:State: False **//anomaly: large motors should not be in auto_home nor its internals**
// Clicked beacon again (runs medium_motor forever)
WARNING:root:State: True
WARNING:root:Running hand_motor forever
// Pressed touch sensor again (stops medium_motor)
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
WARNING:root:Touch sensor pressed. Stopping hand_motor
// Pressed beacon again, nothing happens **anomaly: every time beacon is pressed it should execute move(state)*. The only way to have beacon run the medium_motor forever again is to execute the sequence to trigger the first anomaly*
Issue Analytics
- State:
- Created 5 years ago
- Comments:17 (11 by maintainers)
Top Results From Across the Web
Strange IR sensor movement with default tracker code ... - Chief Delphi
The problem comes when I try and run the code. If the emitter is turned off, both servos turn in unison looking for...
Read more >Chapter 8. using the infrared sensor - WordPress.com
Remember to make the beacon transmit a signal continuously, either by keeping one of the buttons pressed or by toggling the button at...
Read more >experimenting with the EV3 infrared components
to be detected by the IR Sensor in Measure Beacon mode! To enable Beacon Mode, press button 9 on the Remote IR. Beacon....
Read more >The Infrared (IR) sensor on the TV does not appear to ... - Sony
Follow the steps below to troubleshoot this issue: Make sure the remote control is set properly to control the TV.
Read more >Using Sensors - EV3dev Python - Google Sites
It correctly returns 'beacon' if ONLY the beacon button is pressed but if the beacon button is pressed at the same time as...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, thanks for doing the initial investigation. FWIW until we release the package with this change the workaround above is still the best way to go.
Fix released in
2.0.0~beta2. To upgrade:The workaround posted above can be removed from user code.