# AUTO\_READY does not transition to AUTO\_ACTIVE

**URL:** <https://discourse.farm-ng.com/t/auto-ready-does-not-transition-to-auto-active/222>\
**Category:** support\
**Created:** [July 7, 2023, 5:41pm UTC](https://discourse.farm-ng.com/t/auto-ready-does-not-transition-to-auto-active/222 "2023-07-07T17:41:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anb](https://avatars.discourse-cdn.com/v4/letter/a/e0b2c6/32.png) [@anb](https://discourse.farm-ng.com/u/anb)\
**Post date:** [July 7, 2023, 5:41pm UTC](https://discourse.farm-ng.com/t/auto-ready-does-not-transition-to-auto-active/222/1 "2023-07-07T17:41:12Z")

</div>

- What package and version are you using ?  
Dashboard v0.1.7  
Brain v1.3.0

- Please, describe the issues you are seeing ?  
Auto control is enabled on the dashboard, the virtual joystick app is launched on the brain, the brain UI reports that the Amiga state is AUTO\_READY but does not transition to AUTO\_ACTIVE. The brain is connected directly to the dashboard.

\*\* Any possible information will make the live of the community members easy to reply and provide a solution.

 ![20230707_133640](https://canada1.discourse-cdn.com/flex031/uploads/farm_ng/original/1X/5885e4bb3db9663b4e4ad2b63b5bef43ee0477b7.jpeg)

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![anb](https://avatars.discourse-cdn.com/v4/letter/a/e0b2c6/32.png) [@anb](https://discourse.farm-ng.com/u/anb)\
**Post date:** [July 7, 2023, 5:47pm UTC](https://discourse.farm-ng.com/t/auto-ready-does-not-transition-to-auto-active/222/2 "2023-07-07T17:47:35Z")

</div>

Is 0.1.7 the latest dashboard firmware? I tried updating earlier and it found no updates. I will try again.

---

<div class="post-metadata">

**Author:** ![anb](https://avatars.discourse-cdn.com/v4/letter/a/e0b2c6/32.png) [@anb](https://discourse.farm-ng.com/u/anb)\
**Post date:** [July 7, 2023, 6:09pm UTC](https://discourse.farm-ng.com/t/auto-ready-does-not-transition-to-auto-active/222/3 "2023-07-07T18:09:27Z")

</div>

Upgrading to firmware 0.1.9 fixed the issue.