User avatar
evnow
Moderator
Posts: 11480
Joined: Thu Apr 22, 2010 11:41 am
Delivery Date: 25 Feb 2011
Leaf Number: 303
Location: Seattle, WA

Re: New Firmware Pushed : L2R.1.5A

Mon May 02, 2011 6:02 pm

wwhitney wrote:
EVDRIVER wrote:I don't see why anyone would use a Blink timer. Besides that the update added a last charge screen at the main menu but it is almost useless as it omits kwh used at last charge which is all I care about since the cost estimates are pointless and inaccurate on my plan and I don't care about times or % at peak etc. Having kwh used one does not have to note and subtract each time. Duh Blink. :idea:
Just set your cost to charge at a flat $0.10/kwh or $1/kwh, and then you'll get kwh used from the last charge cost.
Last charge is not reliable i.e. it could be the small cell balancing charge after the main overnight charge. I always note the cumulative charge everyday to get daily charges.
1st Leaf : 2/28/2011 to 5/6/2013
2nd Leaf : 5/4/2013 to 3/21/2017
Volt : 3/25/2017 to 5/25/2018
Model 3 : 5/10/2018 to ?

GroundLoop
Posts: 1725
Joined: Mon Sep 13, 2010 9:31 pm

Re: New Firmware Pushed : L2R.1.5A

Tue May 10, 2011 10:33 pm

With firmware L2R.1.5A, is anyone able to get the correct auto-set time?

Mine is one hour FAST (Pacific DST). I have to set it manually to get the correct time.
(via web interface)

GroundLoop
Posts: 1725
Joined: Mon Sep 13, 2010 9:31 pm

Re: New Firmware Pushed : L2R.1.5A

Tue May 10, 2011 11:30 pm

Okay, this is a little confusing.. the web interface is "one hour ahead" of the front-panel interface.

Which means if I want charging to start a midnight, I need to set it for 1AM?
WTF?

DarkStar
Posts: 2066
Joined: Sat Jul 17, 2010 10:06 am
Delivery Date: 25 Mar 2011
Leaf Number: 568
Location: Hillsboro, Oregon, USA
Contact: Website

Re: New Firmware Pushed : L2R.1.5A

Wed May 11, 2011 9:18 am

GroundLoop wrote:Okay, this is a little confusing.. the web interface is "one hour ahead" of the front-panel interface.

Which means if I want charging to start a midnight, I need to set it for 1AM?
WTF?
If the time zone is set properly, the front of the Blink will display the correct time. The Intranet page always displays the incorrect "current time," but all timers are for your local time. No need to adjust how you schedule, just set the time you want it to start/stop.
Mikiko (2011 Nissan LEAF ETEC) Status:
Reserved: 04/20/10 | Ordered: 10/01/10 | EV Project Blink Installed: 03/22/11 | Delivered: 03/25/11 | VIN: 568

Oregon Electric Vehicle Association | Electric Auto Association

User avatar
walterbays
Forum Supporter
Posts: 1209
Joined: Wed Sep 01, 2010 2:41 pm
Delivery Date: 26 Jun 2015
Location: San Diego, CA

Re: New Firmware Pushed : L2R.1.5A

Sat May 14, 2011 3:40 pm

Though I have no car yet, I turned on my Blink so that it could update the firmware. This happened within an hour or two, not waiting for midnight as the manual warned it might, and it went to L2R.1.5A. The only change I saw was that it changed the date to November 6, 2011. (Maybe they know something about my car delivery that my dashboard doesn't, eh? :-)

I was a bit surprised when I turned on the Blink for the first time that it, unlike nearly every other network device, was unable to automatically set date and time from an ntp server. No problem, I thought as I manually set them. But forcing an incorrect setting with a firmware update doesn't give me a lot of confidence. I see why most people set their Blink as a "dumb" EVSE and rely on the LEAF's own charge timers instead.

This also means that all the Blink's reports on cost of charging may be useless. And charging data transmitted to the EV Project might also be useless, unless the date/time errors remain constant, and they timestamp the network transmissions so that EV Project can calculate the actual dates and times based on the relative errors in the transmissions.

Sigh. But "free" was a very good price for the unit!

Update 5/16:

Besides setting the date/time wrong the other thing the firmware update did was to undo my screen calibration. This problem manifested as the unit seeming to lock up every time I went a couple of screens in any direction - as in attempting to adjust the date/time. Turning the Blink off/on "fixed" it temporarily. Also leaving it frozen "fixed" it, as after an hour (or maybe less) it would go back to the home screen; but still it was unable to do anything. I couldn't find a setting to recalibrate the screen because it would always lock up before I could explore for that screen.

The answer was to turn it on and watch and wait, wait, wait. It takes it maybe 5 minutes to boot up and I always walked away to come back later when it was ready. But just after it boots up it goes through the screen calibration screen, and if you aren't standing there waiting for it, you'll miss it - and miss your chance to fix it. Once I recalibrated the touch screen began working again.
Last edited by walterbays on Mon May 16, 2011 10:56 pm, edited 1 time in total.

GroundLoop
Posts: 1725
Joined: Mon Sep 13, 2010 9:31 pm

Re: New Firmware Pushed : L2R.1.5A

Sat May 14, 2011 10:49 pm

DarkStar wrote:
GroundLoop wrote:Okay, this is a little confusing.. the web interface is "one hour ahead" of the front-panel interface.

Which means if I want charging to start a midnight, I need to set it for 1AM?
WTF?
If the time zone is set properly, the front of the Blink will display the correct time. The Intranet page always displays the incorrect "current time," but all timers are for your local time. No need to adjust how you schedule, just set the time you want it to start/stop.
The blinknetwork site also has incorrect times. (or rather, times that don't match the front-panel display or observed timer behavior.) The timer values showing on the intranet page are incorrect.. 1AM and it starts at Midnight instead.

I have my Blink on Ethernet LAN, and it kept dropping off the network. I switched it from DHCP to Static configuration and it seems better now. Strange.

User avatar
EVDRIVER
Moderator
Posts: 6689
Joined: Sat Apr 24, 2010 7:51 am

Re: New Firmware Pushed : L2R.1.5A

Sat May 14, 2011 10:54 pm

GroundLoop wrote:
DarkStar wrote:
GroundLoop wrote:Okay, this is a little confusing.. the web interface is "one hour ahead" of the front-panel interface.

Which means if I want charging to start a midnight, I need to set it for 1AM?
WTF?
If the time zone is set properly, the front of the Blink will display the correct time. The Intranet page always displays the incorrect "current time," but all timers are for your local time. No need to adjust how you schedule, just set the time you want it to start/stop.
The blinknetwork site also has incorrect times. (or rather, times that don't match the front-panel display or observed timer behavior.) The timer values showing on the intranet page are incorrect.. 1AM and it starts at Midnight instead.

I have my Blink on Ethernet LAN, and it kept dropping off the network. I switched it from DHCP to Static configuration and it seems better now. Strange.

IP conflict.

GroundLoop
Posts: 1725
Joined: Mon Sep 13, 2010 9:31 pm

Re: New Firmware Pushed : L2R.1.5A

Sat May 14, 2011 11:19 pm

EVDRIVER wrote:
GroundLoop wrote: I have my Blink on Ethernet LAN, and it kept dropping off the network. I switched it from DHCP to Static configuration and it seems better now. Strange.
IP conflict.
Not likely. I assign each device a fixed IP number on my LAN, and configure DHCP to hand out only that number to that MAC address. Unrecognized devices get numbers from a different pool.

I've recorded every packet sent or received by the Blink ("trust, but verify"), and I'm certain there is no ambiguity in what is assigned or anyone else using that address.

Over 150 devices have worked fine with my DHCP server.. just the Blink is failing to keep its lease.

scm6079
Posts: 9
Joined: Thu Apr 07, 2011 11:02 am
Delivery Date: 26 Jun 2015
Location: Phoenix, AZ

Re: New Firmware Pushed : L2R.1.5A

Sun May 22, 2011 2:12 am

The blink unit is chatty on it's dhcp requests. Locking your blink to a Mac address is a VERY good idea. If you know how, everyone should do that or better run the unit in static ip mode. Frankly, the Blink installers should probably start doing this for users so that the intranet address stays the same.

The way that the blink unit drops/restarts linux networking in the current release makes static ip addressing better than dhcp for the unit as well. Wired networking is also far more reliable with these units than wireless as well. On top of the well commented on antenna issues, the wireless driver for the chipset chosen in the embedded Linux world is sub par, IMO. I have a wireless gaming adapter connected to my blink unit which is more reliable than the internal wireless connection. It may work well for some, but this solution has been far better for me.

-Scott
Scott M.
Battery technology fanatic

GroundLoop
Posts: 1725
Joined: Mon Sep 13, 2010 9:31 pm

Re: New Firmware Pushed : L2R.1.5A

Sun May 22, 2011 9:52 pm

My Blink also seems to reset itself (software) during charging.

Curiously, the charging is NOT interrupted. The Leaf gets continuous power, even as the Blink goes spontaneously through the startup screen, and instructs me to "plug in", and eventually detects that the car is charging.

I have had ZERO networking failures since I hardwired the ethernet and assigned it a static IP address.

There is a bug in the timer handling I haven't seen discussed here:
If you enable an "All Day" timer, to allow charging anytime during Saturday & Sunday, for example, it seems to create a midnight-to-midnight timer schedule.

Exactly at Midnight, the Blink will initiate a new charge to the Leaf.

So, if I plug in on Saturday, get a full charge by 8PM, then at Midnight (Sat/Sun), the Leaf will charge again, topping off the 100% battery over the next 15 minutes or so. This probably doesn't do any favors the battery, and it costs kWh.

Return to “Blink”