RobotHub anomalies and rae firmware update

MartinMotycka Once again, I much appreciate the help. I do have some followup questions, as I still have many points of confusion.

Before I get to the followup questions, I tried something new today, creating an app. I was moderately successful, but it was yet another rather painful experience. I thought it would be helpful for me, and perhaps others, to document what I did, discovered, failed at, etc. I humbly suggest that the level of detail I've tried to include could be helpful to those, like myself, that are just getting started. The document includes some more questions/mysteries, and also includes some helpful info (an appendix) on resetting and reconnection to the hub. I'd be willing to update/polish that if it would help "the cause". Sadly it is too big to attach; this is the Google drive link.

MartinMotycka 1. What is the proper version of the Default app to install; the candidates are 1.2.1 and 2.0.0; I have had 1.2.1 work, but I think I've tried twice to download 2.0.0 and it has failed both times

• I need a lot more help with the USB-C cable stuff. I connected the RAE to my macBook via USB-C and used ssh root@192.168.197.55 with no password and that worked. I can look at the file system But now what? How would I download an app? How would I run an app? I can see various processes running, but I would not know which to kill if the need arose.

• Regarding downloads, I have zero experience with Docker. How do I know if I have to download it? Would it be possible for the Hub to tell the user how big the download is going to be? Also, the Hub indicates my RAE only has 0.4 GB of "disk" available. There appears to be no way I could install an app several GB in size. Am I missing something? One thing I have found with RAE is patience is a must; everything seems to take a lot longer than one might expect.

• Regarding the RAE agent, if you notice in the document I posted, you will find that I again experienced the Hub trying to update the agent. Why is that happening?

• Regarding lag time, I started informally timing the lag, and it seems to be less than 2 seconds, so I guess my experience is expected.

• And finally, the Default app. I have spent the last 2 hours trying to achieve what you suggest is possible and so far I am not even close. I first had to install the Default app; I had to use 1.2.1 because I could not ever get 2.0.0 to install or even download. Using the Hub, I was able to assign the device to the Default app, and was able to successfully run the app. I noticed in your post that the app was stopped, so I stopped the app; I think, anyway, because the LEDs stayed on. I fired up the agent to https://192.168.1.69:9010 (the WIFI IP address of my RAE) and when I clicked "Perception Apps" I saw something similar to you image, though my Test app was on the left and the Default app was on the right. I clicked "Open Frontend" and got a black page; I waited for a few minutes and concluded it did not work. I shutdown the device and started again and the Default app started. I tried the agent again, with the app running, and got the same results -- a blank page for a few minutes. I tried again and again, but something changed and all I got was a "twirly circle pair". This happened over several power cycles, so I gave up. Can you give me the magic incantation to get to point where I can use the Default app to manipulate the motors, LEDs, etc?

Thanks for the help.

Luxonis-Vlad Thanks for the information. Reading between the lines, perhaps over-pessimistically, I see large changes in architecture, significant development, significant testing, and a significant documentation effort. Based on what I've experienced in my career as a SW and HW developer (tho I'm long retired), it could be many months before "the new RAE" is ready for those of us who want an underlying platform that is stable, works reliably with reasonable performance, facilitates fast iterative development, and is well-documented, so we can do what we want to do. Luxonis, in my opinion, achieved that quite well with the original OAK-D, which is why I was excited to get a RAE. Unfortunately, my experience with RAE so far has been quite frustrating. It is unstable, not well documented, and doing the simplest, mundane things is like paddling through molasses.

I first started trying to use RAE 5 months ago, and managed to get it into a state from which I recently found could be fixed only with a factory reset. Other tasks caused me to put RAE on the shelf. Now, 5 months later, I've spent over a week and have made almost no progress in terms of actually developing my own application. It seems to me I might be better off putting RAE back on the shelf for another 5 months, hoping the new architecture will be usable at that time. Does that make sense?

IvoGermann I thought I made the second link public. I am traveling with limited access so it could be Tuesday before I can investigate.

IvoGermann By some miracle I could get to Google Drive and check. I think the file is as public as I ca make it. Here is the like Let me know what happens.