So we have the new boot loader for the Kid working very well. I am not going to put the updater up live as it is only needed for these Betas and can actually brick the device if done wrong so I am going to ask for email requests and I will email out the boot loader.
This only works with windows 7. If you have any other windows we will need to RMA the Kid and update it for you.
ryan@midnitesolar.com
Here are the instructions:
procedure:
- Save the "bootloader_updater_512.out" to your pc where it is easy to find
- Go to our software tab and download the Kid firmware file "MNKID_firmware1709.fup" and save it to your pc where it is easy to find
- Connect your kid via USB to your pc
- Go to menu Firmware Update and select it
- When the kid connects to your pc grag and drop the bootloader_updater_512.out to the kid
- Wait until the top green led stops blinking (takes like 2 minutes)...(don't screw it up you only get one shot at this)
- Manually reboot kid and it should appear in the screen as BOOTLOADER 2.1
- The kid will appear again in your PC now Drag & Drop this new firmware "MNKID_firmware1709.fup".
- The kid will disconnect automatically from the PC and will decode the firmware
- Wait until it goes to 100% and disconnect the USB cable.
Ryan,
Email sent.
Damani
Ryan;
I am in. You have mail...
Thanks.
Tom
Just did this this AM on Win 7 Home Premium and it worked treat.
Just followed the directions above and it uploaded the firmware via Ubuntu 11.10 on my laptop after I uploaded the bootloader via Win 7.
Thanks, guys.
Tom
Ryan, for the betas do you expect another update soon or is this it for a while?
I expect very frequent updates. This will be the .FUP file that is off the website that just gets D&D into the kid. This particular one is a new boot loader and is basically a Must and then you use the .FUP file that you will find on the software tab on our website. So to be clear this step now is actually 2 steps, The new bootloader and then the new firmware. So this is a must "Before" you install the new firmware
To everyone,
This is what's new on firmware version 1709:
Version 1709:
- Added go to Main Status screen in 5 min of no operation.
- Added LCD power mode and key wake up
- LCD Power Setting Saved in EEprom
- Back-light and Contrast now under SETUP in LCD menu
- Added Manual EQ
- Settings for EQ are under SETUP in the EQ Menu
- Fixed negative temp display
- fixed the negative FET temp issue RFR 6
- added LED functionality
- added save functions for LED and LCD
- added BCM to count days without float for BCM LED function
Mario
A tip for these kind of critical software updates: A fully charged but unplugged, 100% known reliable laptop is the best. This gets around a number of (albeit rare) possible problems. Other than possible USB voltage issues, what you dont want is a computer that drops into hibernate, someone or something tripping over your power cord, power cut, brown out etc etc. Those would be, like, bad.
Well said!
Quote from: Halfcrazy on February 05, 2014, 06:43:15 AM
So we have the new boot loader for the Kid working very well. I am not going to put the updater up live as it is only needed for these Betas and can actually brick the device if done wrong so I am going to ask for email requests and I will email out the boot loader.
This only works with windows 7. If you have any other windows we will need to RMA the Kid and update it for you.
Ryan, will this work with 64 bit W7?
Quote from: onanparts on February 06, 2014, 12:41:26 PM
Quote from: Halfcrazy on February 05, 2014, 06:43:15 AM
So we have the new boot loader for the Kid working very well. I am not going to put the updater up live as it is only needed for these Betas and can actually brick the device if done wrong so I am going to ask for email requests and I will email out the boot loader.
This only works with windows 7. If you have any other windows we will need to RMA the Kid and update it for you.
Ryan, will this work with 64 bit W7?
Not Ryan, but yes it will work on W7 64 bits.
Actually that is what I was running when testing it.
Mario
Quote from: Mario on February 06, 2014, 01:17:13 PM
Quote from: onanparts on February 06, 2014, 12:41:26 PM
Quote from: Halfcrazy on February 05, 2014, 06:43:15 AM
So we have the new boot loader for the Kid working very well. I am not going to put the updater up live as it is only needed for these Betas and can actually brick the device if done wrong so I am going to ask for email requests and I will email out the boot loader.
This only works with windows 7. If you have any other windows we will need to RMA the Kid and update it for you.
Ryan, will this work with 64 bit W7?
Not Ryan, but yes it will work on W7 64 bits.
Actually that is what I was running when testing it.
Mario
Yup! 64 bit Win 7 worked fine with new BL and FW. :)
Just a note on the instructions: The BL only took a few seconds before the green light stopped blinking after a drag and drop. The FW is what took 1-2 minutes to update and get to 100%. Not sure if that's a typo or my PC is just really fast? :)
So do you have to install the new bootloader in order to get the update? Don't have a windows 7 machine currently. I would like to roll up to the latest beta revision due to some of the issues it corrects.
Yes the new bootloader is a must before any new firmware can be installed. We can always do an RMA and get it back if finding a windows 7 laptop is not an option. Please contact me via email for that
ryan@midnitesolar.com
Installed new bootloader via Windows 7 , then update . It all went according to plan - though I did need to reset the Kid when I first went to firmware update for the computer to see it.
Okay. I'll borrow a laptop.
I need to get an email off for the bootloader.
Okay next dumb question. Will only a windows 7 system be able to update firmware after the new Bootloader is installed or can other windows OS be used?
Quote from: Bunkie314 on February 07, 2014, 05:31:03 PM
Okay next dumb question. Will only a windows 7 system be able to update firmware after the new Bootloader is installed or can other windows OS be used?
The new Bootloader 2.1 (new) supports Windows XP/7/8/8.1 , and linux. Pretty much anything but Mac.
I even think Ryan has updated it with his Android device which supports USB Host. Right Ryan?
Mario
Quote from: Mario on February 05, 2014, 12:36:31 PM
To everyone,
This is what's new on firmware version 1709:
Version 1709:
..etc..
Some nice additions in 1709. Thanks.
Do you have a list of the new features that you are working on for the KID?
I would be interested in any AUX functions you will be adding.
dgd
Quote from: Mario on February 07, 2014, 06:17:10 PM
Quote from: Bunkie314 on February 07, 2014, 05:31:03 PM
Okay next dumb question. Will only a windows 7 system be able to update firmware after the new Bootloader is installed or can other windows OS be used?
The new Bootloader 2.1 (new) supports Windows XP/7/8/8.1 , and linux. Pretty much anything but Mac.
I even think Ryan has updated it with his Android device which supports USB Host. Right Ryan?
Mario
So I could potentially use a tablet or my note II phone? Now that is nice! ;D
Quote from: Mario on February 07, 2014, 06:17:10 PM
The new Bootloader 2.1 (new) supports Windows XP/7/8/8.1 , and linux. Pretty much anything but Mac.
Is that because you hate the mac and won't support it; because you haven't got around to it yet (but it's coming); or "it may work but I don't have a mac to try it with"?
If it works for linux, it should work for Mac, since Mac is basically FreeBSD under the hood.
Houston,
We have a problem. I was updating the kid and now it seems to be not responding. I actually got two betas. The first one went fine. Ok while I was doing the second I notice something strange but I continued anyway. The screen was flickering every so slightly. I uploaded the boot loader flashing green light stoped. Then I re-booted it and it did not display the "bootloader v2.1" thing. Instead all of the holiday led were light and the display showed nothing except an inked out first row and an dim back light. Please "doc" give it to me straight.
Cheers...
Damani
I just have to ask , more because I don't think this may be an issue, and , secondly because I am not familiar with the vagaries of the OS of the machine..
Will it work on a 32 bit Windows 7 LITE notebook machine?
Dapdan
Sounds like trouble but I will let Mario respond.
Westbranch
On windows I suspect it should work just fine on the 32bit windows 7
RossW
I am told Mac does something funny with there Drivers that causes it not to work. I will ask Andrew for a better definition though.
Ryan
Hi,
Yeah you would think OSX / BSD would work, but apparently the Mac version of BSD does something non-standard with USB devices. While I was working on the Bootloader I found that Linux and Windows dump the file and file system data as you would expect -- albeit in different orders. Mac did nothing. No data came down the wire even though the file showed up as being on the device on the OS-side. I tried ejecting the device -- again, no data came down the wire but the device showed up as ejected and removed. When I dug a little deeper I found that NXP -- the manufacturer of the chipset we use -- mentioned in their application notes that they did not support Mac for USB as they do something non-standard. I think the gist of it is you have to pay them cash money in order for them to either add your device to their list of "things that just work" with Mac so the OS will actually write to the device, or for them to tell you the sneaky trick required to trigger the data transfer.
That is my suspicion but I have not basis for this conclusion and don't want to get sued by Apple for spreading potential misinformation. I also don't want to pay them any extortion money.
Ryan,
Email sent a bit ago.
This boot loader and firmware update is real easy compared to firmware updating a Classic.
Followed the instructions but after getting to TECH menu and to firmware update and pressed ENTER as instructed then NOTHING. Supposed to go into update mode but it doesn't. Did this about 20 times, power off/on KID and checked the USB cable to WIN7 laptop.
Gave up to next day and started again, same process and NOTHING, I pressed that ENTER rubber button enough to push it out the back of the KID and halfway to USA but still nothing.
About to give up again when I started sneezing as I pushed the ENTER key and the KID went into update mode.
The laptop showed new F: drive
From there drag and drop went well
1712 loaded up good and it seems stable. Have not seen much battery voltage wandering away from actual voltage but need to load up inputs of KID and see what 'appens.
The stress and heat is too much, need some beersies :D
dgd
Quote from: Free Energy Freak on February 10, 2014, 04:56:47 PM
Ryan,
Email sent a bit ago.
Sorry If I missed anyone. I was out all week at a show. Hit me again via Email ryan@midnitesolar.com
I am still trying to go backwards through emails from last week
Ryan
Quote from: dgd on February 16, 2014, 11:19:30 PM
Gave up to next day and started again, same process and NOTHING, I pressed that ENTER rubber button enough to push it out the back of the KID and halfway to USA but still nothing.
About to give up again when I started sneezing as I pushed the ENTER key and the KID went into update mode.
dgd;
Not to beat a dead horse but I had noticed this anomaly with the buttons on The Kid. A key press needs to be firm and prolonged and not just a short tap.
I think this was addressed in another thread and longer buttons was the proposed "fix"?
On my Classic(s) if you hold the button down too long you might activate the next option selection so was spoiled by the quick jab selection method?
.
Tom
Quote from: TomW on February 17, 2014, 11:30:54 AM
dgd;
Not to beat a dead horse but I had noticed this anomaly with the buttons on The Kid. A key press needs to be firm and prolonged and not just a short tap.
I think this was addressed in another thread and longer buttons was the proposed "fix"?
On my Classic(s) if you hold the button down too long you might activate the next option selection so was spoiled by the quick jab selection method?
.
Tom
Thanks Tom. I had not noticed those messages about button sensitivity but now I am more careful and there is a definite technique to getting the button press just right.
The battery voltage reading drift is now definitely resolved with 1712.
5 days and the KID battery voltage is spot on with the Classics and Fluke.
Thanks Mario
dgd
Another way to force a firmware update is to Press and Hold the SETUP button then apply battery voltage, the kid will boot up in firmware update mode.
So, here is the link of the latest firmware update just released today.
Rev 1703 whats new:
-fix LCD going blank
-fix battery voltage drift over time
-added password protection
http://www.midnitesolar.com/firmwareReport.php?firmware_ID=8&firmwareProduct_ID=4&act=edit
Must have Bootloader 2.1 already installed in The Kid
Mario
I hate to be the Newb here and ask a really dumb question but; Does the Kid need to be powered up with an external power source before trying to update the Bootloader and Firmware? Or will the USB power form the Windows 7 box be enough to upload the new files.
I know, Newb.....
The problem is my setup is out at the farm and my only Win7 box is at the house. I guess I will use my truck batter (with fuse) to run the Kid if needed and then use the 7 box to upload the new files.
Can you please think about adding support for macs :)
Quote from: Highflyer on February 17, 2014, 08:08:57 PM
I hate to be the Newb here and ask a really dumb question but; Does the Kid need to be powered up with an external power source before trying to update the Bootloader and Firmware? Or will the USB power form the Windows 7 box be enough to upload the new files.
I know, Newb.....
The problem is my setup is out at the farm and my only Win7 box is at the house. I guess I will use my truck batter (with fuse) to run the Kid if needed and then use the 7 box to upload the new files.
Can you please think about adding support for macs :)
Flyer;
Not sure about The Kid but I updated my Classic with 2 9 volts in series. It should work on The Kid, too. Easier than lugging in the truck battery. Probably don't need fusing either.
No guarantees but easy to test.
Tom
The kid does need to get external power since the USB jack will not provide power, as Tom is suggesting a couple of 2x 9v batteries in series will do the trick as well. Even an old 12v modified wall wart can be used.
Remember that the Kid gets powered from the Battery terminals.
Mario
Tom, that is genius. I can do a pair of 9volts!!
Thanks for the help and idea. I finally got my W7 box updated, when I get back home, I'll do the updates!! I can't wait to get busy working with better power.
Mario, thought so, I also like the wall wart idea. I think I will set one up for just this kind of thing as I hope for several more firmware updates as features get added. Thanks for all your efforts.
Mario,
All these changes in 1713 (1712) are all good, the KID appears a lot more stable.
One question about the TIMER display.
This looks like it is a clock display but looks a bit weird with HH MM:SS That : looks odd by itself maybe a
HH:MM:SS would look better. Also if any of these is a single digit then a leading space is inserted. Again this may look better if a leading zero were inserted
eg 5 7:23 would become 05:07:23
Next question is how can this clock be set to a specific time? I cant find a setup section for it.
On the lower line is
0y 5d
What is this?
Last, if there is a clock counter then that would allow a daily Ah and KW/hr count and associated display to be included in KID. That would be very useful as presently there is no way of seeing how much energy has been produced.
I understand that without a real time clock circuit and associated battery in the KID that at every power on time the clock would have to me manually reset to current time (on 24 hour clock basis)
The same could be done with date although I cannot see the use for this until you have a method of dumping via serial port the various values. Date stamping them would be very useful for those wanting to develop some sort of reporting system.
dgd
Midnite,
Kid 1713 fw update has been successful. I had to use the force update method as the computer was not picking up the kid as a drive. So far so good. No comments as yet will monitor during the day when the sun come up.
Cheers...
Damani
Update 1713 went fine here - put it in firmware update mode, plugged it into computer and then dragged update into that drive - makes it so easy !
One question - will the WhizbangJr screen ever read negative amps ? It does show the battery draw tonight but always shows it as a positive value.
I know the LCD screen space is limited but if I had a choice I would rather see watts displayed on the WBJR screen rather than it's temperature
FW 1713 loaded in my first Kid straight by the numbers (thanks Mario!). From what I read, I too would like the colon between the hh:mm:ss. I would like to propose a compromise for the WBJr readout. I would like to be able to read both temp and draw. How about a toggling screen that waits two or three seconds between each reading? That way we could see both items in just a few seconds.
A new gremlin appeared with the FW 1713 update. Using the day light feature makes the screen go to solid squares and the bottom line blank. Charging appears to continue but requires a power cycle to bring the display back. I've verified this with both betas I have. I'm not running a light but rather connected to another 12 volt battery for charging. It worked excellent prior to this update. Tuning off this day light function prevents the display from doing this.
Where is this setting that messes up the display ? I was just looking for it but couldn't find it Nothing I did with LCD seemed to mess up mine.
Its under load menu in battery settings you have several options. I had been using the day light function to charge another battery.
Quote from: Bunkie314 on February 22, 2014, 10:49:17 PM
A new gremlin appI it is running up overared with the FW 1713 update. Using the day light feature makes the screen go to solid squares and the bottom line blank. Charging appears to continue but requires a power cycle to bring the display back. I've verified this with both betas I have. I'm not running a light but rather connected to another 12 volt battery for charging. It worked excellent prior to this update. Tuning off this day light function prevents the display from doing this.
Actually that is not it. I am not sure what is causing this as I found it this morning again.
Quote from: Bunkie314 on February 23, 2014, 12:22:49 PM
Quote from: Bunkie314 on February 22, 2014, 10:49:17 PM
A new gremlin appeared it is running up overared with the FW 1713 update. Using the day light feature makes the screen go to solid squares and the bottom line blank. Charging appears to continue but requires a power cycle to bring the display back. I've verified this with both betas I have. I'm not running a light but rather connected to another 12 volt battery for charging. It worked excellent prior to this update. Tuning off this day light function prevents the display from doing this.
Actually that is not it. I am not sure what is causing this as I found it this morning again.
Moved to report card thread.
Mario,
Would it be possible to add a feature to the load/clipper side allowing it to run a set of case fans while charging or if the temp was above a owner set limit? I have an outdoor setup that is encased and it has several fans which have very low draw, but they provide the necessary air flow to keep things cool and vented as needed.
I plan on adding a controller later(most likely a PI), but if they were the only extra I had in the case, it would be great if the Kid could run them (the fans).
So Rev 1714 is coming soon and It includes the reading of negative amps from the WBJR among other fixes.
I really want to finish adding the SOC for this next firmware rev.
We'll see....
Mario
Quote from: Mario on February 24, 2014, 09:08:16 PM
So Rev 1714 is coming soon and It includes the reading of negative amps from the WBJR among other fixes.
I really want to finish adding the SOC for this next firmware rev.
We'll see....
Mario
Thanks - will look forward to that.
I installed version 1713 this morning. Are you sure you want to make this software this easy to install? No installation problems at all.
The only way it could be made easier to install for non-computer crowd would be to use a USB. To do an upgrade, you copy the upgrade.exe file to a USB thumb, plug it into the port on the instrument. The front panel displays "upgrade firmware? Y/N" Push up button for yes and the system does the upgrade and says to remove the thumb when it's done.
Just an idea. ::)
1722 has been out for a while now. Is there any update on the horizon?
Thanks for all the hard work!!
Any news on the EA feature using the WBJR?
I'm still curious about what triggers a charging cycle. Seems every morning I can check the kid is in a charging cycle. I don't cycle down the batteries often since it's an RV. Only thing connected is the kid so very little draw. I'm worried about overcharging my agms.
Thanks for all the work put in. I can't wait to get all my panels installed and play with the bully mode.
Even if you don't use your batteries much they still have a self discharge and are going to charge up some. The setpoints determine if it is charging or not . It will go through the bulk cycle till it gets to Absorb and then adjust the current to hold the Absorb voltage for as long as you have Absorb time set for. Afer that it will go to Float setpoint. Ending amps when it gets implemented will stop Absorb time early if it gets to the Ending Amps setpoint before Absorb time and then go to Float. Figuring out the correct ending amps setting depends on what type of batteries you have and you would need the Whizbang installed too. But for now you just need to make sure you have the correct Absorb time set so the batteries get full but don't go too long. If you have flooded lead acid batteries you can check with the specific gravity of the batteries to help determine the exact setting for the ending amps. Otherwise you just kind of have to watch it in Absorb and watch for a point when the system amps shown by Whizbang gets to a point where the system amps doesn't change too much. It is a bit tricky to figure this ending amps point sometimes. Just using Absorb time can work okay too though . For example if your SOC goes down to 85 percent, in the morning watch the system amps and voltage when it gets to 100 percent SOC . If you had your Absorb time to 3 hours and it was filling up to 100 percent at 2 hours you could cut back the Absorb time .
Hope this makes sense . Took me awhile to figure out how all this works .