Firmware update issues

#1

Anyone have problems updating the firmware on the ultimate robot kit via an iPhone 6 plus running 8.1.3 iOS .
When I update it , there is a high pitch sound and when I try to connect to it via blue tooth it tells me I have to update the firmware

#2

If you check the posts you will find that flipping that little white switch will turn off the buzzing. So far it looks like the best way to upgrade the firmware is NOT by Bluetooth but by USB. Hint unplug the Bluetooth module before you do.

#3

I am also having issues with updating the firmware via IOS. I am brand new to Makeblock, but have some experience with Arduino IDE. However, I have not been able to get an update to work either via usb or Bluetooth. The update procedure looks like it would be rather simple if everything was working correctly, like bluetooth. Otherwise documentation seems limited.
Is there a detailed usb firmware update how-to anywhere? I haven’t been able to find one, and I’m starting to get a little bit frustrated. Right now I have a $250 doorstop that I’d like to see moving. Without the bluetooth, this build with this board is useless.
I attempted an update via Scratchbot, but it apparently didn’t take, as I still get the same message in the IOS app. It said it was updating, and the board did beep as if it had received the data, but no change otherwise.

Ultimate Robot Kit
Orion
Robotic Arm Tank build
IOS 7.1.2 on iPad 3 w/ Makeblock HD app
Arduino IDE in OSx 10.9.5 (Mavericks)
It is communicating with Arduino IDE via usb. I’ve gotten RGBs to test okay, but not much else.
There is limited communication between the main board and the iPad. It connects, but wants a firmware update and can’t find one.
Any help to get this up and running will be appreciated.

#4

I am a new member here, who just started with the BT starter robot kit with the Orion controller and had what seem like similar issues–trying to update the firmware, I have an Android-based tablet, but perhaps the details of my experiences might be helpful. See http://forum.makeblock.cc/t/code-update-not-working-for-orion-board/926 . Perhaps the steps I described will help you find a solution.
Steve

#5

PS: I think, but I am not sure, “firmware update” might refer to two different things: (1) running a sketch that alters how the Orion/Arduino handles programs and (2) running a sketch as a program itself. It seems to me that when the Android-based app asks to update the firmware by pressing the reset button, it is simply loading a sketch that supports the app.

This morning I powered down my Orion after having used the Arduino IDE and the micro-to-usb cable to upload the DC motor test. This evening,as expected, that sketch was still in the Orion’s memory; so it ran at power up.

I turned on my tablet, started BlueTooth, opened the Makeblock app., made the connection with the paired Orion, and was asked to update the firmware by pressing the reset button. It seems to me that pressing the reset button tells the app to upload the associated sketch which allows the app to control the robotic device. It seems to me that the sketch is either encoded in the app itself, or perhaps when I ran mbot_firmware yesterday, maybe some special code needed by the BT app was stored in the Orion.

Again, this is all new to me, but I am hoping that my experiences will help others solve related issue.

Steve

#6

On mine you have to update the firmware when you switch between USB cable connection and Bluetooth every time.

#7

Thanks for the quick replies.
iSteve, if your theory about “firmware update” is correct, that definitely sheds new light on the subject. Without parsing words, IMO “software update” would be more accurate and less confusing in this case. There might be some holes in that theory, but it’s worth looking into.
Your linked discussion also links to a firmware.zip file. In my experience with the Arduino platform, I’ve never had to update the board’s firmware. I’ve imported Arduino libraries via zip files and worked-out the related bugs. What I haven’t done, is to import a zip file for a firmware update. Does it work the same as a library? Do I simply download the zip, import it as a library, compile it in the IDE, then upload it like any other sketch? When I get links to unknown zip files, red flags go up, and I want to know now to use the zip before proceeding. That’s just common sense computing.

Thanks for the help.

#8

…and redkcir, a firmware update every time you go to Bluetooth from usb? Every time? Has that always been the case, or is it something recent? Sounds like something that the developers need to know about.

#9

It has always been the case. I fought it for a while before discovering this. It may have something to do with having to unplug the Bluetooth before the USB connection will even work. I must mention this is when I am using Scratch as a programming platform. I had to much trouble getting it to work with the Arduino software (I think I was trying to use the newest version 1.6.1, but when I down graded to 1.0.6 that I downloaded from Makeblocks site it worked better) and I use it to teach young kids so the Scratch program works better for me.

#10

Yeah, I agree about the hole–I am not sure if the mbot_firmware alters anything inside the Orion. It could be coincidence or something else I did or maybe some change in the android app that caused the reset button to successfully cause the sketch to be loaded.

I am pretty sure that each time I changed the program (or sketch) in the app, I had to upload it by pressing the reset button. I understand their logic in calling it firmware, but having played with an Arduino Mega 2560 a number of terms, I tend to use “sketch” and “upload.”

I am usually tired by the time I tinker with the robot, and have very little mind left to try to figure out what that firmware.zip file actually does.

My next task is to wire up 4 battery holders in parallel (16 AAs) to see if I can make the tank move without the wall-wart!

Steve

#11

Did anyone get the Bluetooth app to stop asking for updates ?

#12

If my theory is correct, the only way to have it stop asking for “firmware updates” is to leave it on and don’t change programs/sketches. (My experience is with the android app in a tablet.)

That being said, did you successfully have it “update”–as in go from 0% to 100% after pressing reset when directed? If my theory is correct, that simply uploads what I am calling a sketch.

If you did, were you able to then run that specific program/sketch before trying a different one? If so, in my very limited experience a number of things will require a sketch/program to be re-loaded. I haven’t sorted them all out, though. I think (not sure) that breaking the BT connection will require a sketch to be reloaded. As I said, I think changing the program in the app (e.g., Distance Display, Tank Controller, etc.) requires a new sketch to be uploaded. Not 100% sure on that. Once I get the tank off the wall-wart, I will try to double check this.

Hope this helps.

Steve

#13

I use an 8 pack AA battery holder (12VDC) I found at RadioShack before they went belly up that works well.

#14

JayP Not me. not yet.

iSteve, I agree. My preference is to use to terms sketch or program. I too can understand how the term firmware is not incorrect, in that we are dealing with a microcontroller. When we upload a program, we are programming the hardware, so technically it is firmware. My confusion was based in the fact that I forgot/overlooked that the Arduino is simply a microcontroller. I suppose that is why the term sketch was created in the first place.
As for the usb update via scratchbot, I am fairly sure that I was getting some type of progress bar during the update, and I do recall getting a completion-beep from the board. I have been able to run some test programs, but that’s the extent of it. My efforts have been geared towards getting my present build, the Robotic Arm Tank, up and running, so I haven’t tried much else. My only success so far has been testing the RGBs and the DCMotorDriver test. I do want to test more of the hardware soon, so I will write my own sketches to do so if I’m unable to get the BT remote/app to work.

redKcir, thanks for the tip about Arduino 1.0.6. I was able to actually test a motor when I uploaded a sketch from this IDE version. Unfortunately, that’s been the only real noticeable change.

Everything at this point is pointing towards app/bluetooth issues. I read on another thread where there seems to be an issue with the IOS app. I’ve had the same results on my iPad and iPhone. If I find a useful solution, I will post it here.

Hopefully I will be able to spend some more time on this in the next couple of days. Got a lot going on.

Thanks guys!

#15

Hello everybody, today I spent all day wandering over the internet reading several times everything in an effort to try and understand this orion baseboard. Today I love my arduinos even more haha.

I assembled my robotic arm tank and worked right away connecting the orion with my iphone app via bluetooth.

As soon as I tried to go deeper, using scratch and “upgrading” the firmware boom, orion in coma.

I couldn’t manage to get it to work again, receive any sketch, firmware however you want to call it.

In my case the reset button got unresponsive so now it doesn’t even take the firmware via bluetooth with the iphone app.

I wonder if there is a way to flash the baseboard orion as it came from the factory.

Today I upgraded Arduino IDE to the new version and it has the ability to burn a new firmware to the board.

Still trying…

#16

FINALLY !!! Got it working

After burning my head off I got to flash brand new the Makeblock Orion!

I will make a new post telling how.

I used a Arduino Uno REV 3 as a programmer.

#17

My woes just got a little deeper. After further tests, it seems that the 25mm motors that came with my kit are defective. They turn, but have minimal torque. I’ve left a message with MB support. Holding my breath.
Good news. The arm goes up and down, and the claws move. $250 for flailing arms and claws? Shoot, I’ve been married to that for 10 years.

Fernando, good going. I look forward to your new post.

#18

I have good news, too. It works! :smile: I redesigned the BT starter robot tank: (1) the center bar is now off-center so as not to totally block the rear motor motor connector and (2) the two platforms are not directly over one another so both the battery pack and the Orion are accessible. I used 6 brand new 1.5v AA batteries. I think the rechargeable batteries I had been using are no longer capable of maintaining a full change.

There are quirks, though, and I did have to upload the sketch/update the firmware from the android tablet several times. One time, I could not get the reset button to trigger the upload/update. (Sound familiar?) I think what finally get it uploading/updating again was turning everything off (not sure of the order) including powering down the tablet,re booting it, turning on the Orion, starting the app, etc. I believe there are delays, maybe some handshaking, and if something gets out of sync, it seems that shutting down and starting over is the only thing that helps.

Its been on for about 45 minutes (not moving, the whole time), and as long as I have the Orion on and the app on, I do not have to reload the sketch (aka upgrade the firmware).

Footnote: by default M1 and M2 drive the two tank motors, but I am using the Robotic Arm Tank program with one control also linked to M1 and another linked to M2. So, with the speeds adjusted properly, I can turn on the spot (e.g., M1 going forward and M2 going in reverse).

So, my advice: don’t give up just yet–there is hope for these robots!!!

#19

Your welcome. The 1.0.6 worked best for me and I had some success with it. I have yet to get the RGB LEDs working in any form other than to get some of them to turn on and again this is sporadic. Some times a few, some times all of them and lately none. Other than getting them to light no effects at all. I have gotten all the motors to work with Scratch and the Bluetooth Android App using the methods I have mentioned. I got my Raspberry Pi 2 the other day and the Arduino software in the latest Raspbian (Release date: 2015-02-16) is version 1.0.1 but I haven’t tried installing the library for Makeblock to see if it will work but I hope to in the near future.

#20

The LED sketch that I used is in Arduino IDE from the Makeblock master library. It’s a simple test program. On my system, within the IDE, File/Examples/makeblock/Me_RGBLed/xxxxx. There are 3 test sketches listed, and all worked for me.
The RGB is plugged into an RJ25 adapter, and the adapter is connected to port 3 of the Orion.
I uploaded each sketch directly to the board via usb.
I’d like to hear more about the Pi 2 when you get it set up. That’s a Pi project that I’d not considered.