Hi,

I’m quite new in EV3 programming and exploring it by building factory models.

Assembled the EV3RSTORM robot today (I use the code provided by LEGO in the EV3 Home app), which should seek for the IR Beacon. Instead it goes crazy when I turn on the IR Beacon: it goes backwards, then turns 90 degrees and moves away from the IR beacon. This behavior is not as in demo videos in EV3 Home app where it turns in IR beacon direction and chooses distance before shooting red balls. I’ve double checked connections, check the IR sensor readings - the sensor correctly identifies direction and distance of the IR beacon, but when I run the provided app EV3RSTORM goes crazy.

I’ve managed to grab the robot in my hand and manually adjusted distance and direction of the IR beacon (in other hand) - it identifies the IR beacon and shoots when there is the direct line of sight.

Maybe it’s because of reflections? There is no direct sun light in my room - windows are closed. Floors are quite regular (not extra glossy).
When I turn off the beacon, EV3RSTORM stops immediately which is the correct behavior based on the code in the app.

Any ideas how to fix?

Edited July 18, 2024Jul 18 by legoisfun

If it shoots and identifies IR signal correctly while lifted off the ground, my guess is either your program or physical wiring incorrectly drives the motors in reverse direction to expected.

I would try swapping the cables of the 2 driving motors with each others ports on the EV3

Edited July 13, 2024Jul 13 by Heppu

10 hours ago, Heppu said:

If it shoots and identifies IR signal correctly while lifted off the ground

Even lifted it takes a lot of time to properly position it, so something is wrong – I bet on IR light reflections.

Quote

my guess is either your program

I use the program provided by LEGO in EV3 Home app, so I wasn't making it or changing.

Quote

or physical wiring incorrectly drives the motors in reverse direction to expected

Not possible with EV3: connectors are physically won't fit, so messing with polarity is unlikely. Plus  motors are driven by a protocol, so with a wrong wiring motors won't work at all.

Here is the code supplied in EV3 Home:

 

It's also possible that there is an error in IR Target code: maybe LEGO made some changes to brick firmware or/and EV3 Home app and forgot to check default programs, which are provided in EV3 Home.

Edited July 14, 2024Jul 14 by legoisfun

I have only used python to drive my EV3, so cant really help with the native block programming language. If you feel something is wrong with the IR, maybe build a simple program that just measures and outputs the signal strenght to read? Then observed if there are major fluctuations in the readings while the sensor and source of IR are stationary. This would narrow down troubleshooting the actual issue or identify potential other sources of IR nearby.

For the motors, apologies if I was unclear. I meant to switch the ports the motors are connected to. So B to C and C to B in your case.

1 hour ago, Heppu said:

I have only used python to drive my EV3, so cant really help with the native block programming language. If you feel something is wrong with the IR, maybe build a simple program that just measures and outputs the signal strenght to read? Then observed if there are major fluctuations in the readings while the sensor and source of IR are stationary. This would narrow down troubleshooting the actual issue or identify potential other sources of IR nearby.

For the motors, apologies if I was unclear. I meant to switch the ports the motors are connected to. So B to C and C to B in your case.

I’ve connected EV3 brick to my PC via USB for debugging - IR sensor works as it should - i see correct readings (distance and heading) when IR beacon is ON. So, something is wrong in IR Target - it’s a special block, which includes some math under the hood.

Thanks, I’ve double checked all ports - connected properly.

Edited July 14, 2024Jul 14 by legoisfun

I’ve found the issue: connections for B and C motors should be crossed on the EV3 brick: left motor to B port and right motor to C port. And I’ve connected them straight: left to C and right to B. Have no clue why LEGO has chosen this variant of connection, which is a little bit more messy in my opinion.

On 7/14/2024 at 1:44 AM, Heppu said:

 or physical wiring incorrectly drives the motors in reverse direction to expected

You were absolutely right! Such a newbie mistake I’ve made.