Recent Posts

Pages: [1] 2 3 ... 10
1
Raspberry PI / Re: ngrok for LocalStatusPanel on Remote Computer
« Last post by mcsarge on November 20, 2019, 04:51:33 PM »
All,

I did not mention it, but this tool is used heavily for getting a web server out form behind a firewall - this would be great if one of the guys creating the Raspberry Pi based monitoring system wanted to see the UI from the internet. Also, you it gives a lot of very good information about the tunnel, you can even look at the tunnel info using a browser - just open a page on http://localhost:4040 and you see some cool stuff about the connection.

Matt
2
Raspberry PI / Re: ngrok for LocalStatusPanel on Remote Computer
« Last post by boB on November 20, 2019, 04:16:29 PM »

This looks really CooL Matt  !!
3
Raspberry PI / ngrok for LocalStatusPanel on Remote Computer
« Last post by mcsarge on November 20, 2019, 03:36:43 PM »
Hello All,

I have been using an awesome little tool called ngrok (https://ngrok.com/)  to connect to port 502 on the Classic on my remote network. I need to use this tool since I am running my remote network on a cellular connection; I can't just forward a port from the cell router to the Classic, the cell company blocks all incoming ports. I have a Rasperry Pi running at the remote site and I connect to it by VNC. I installed ngrok on it, and I use it to create a tunnel to the Classic.

Essentially, the ngrok tool allows you to create a tunnel from behind your firewall/router to a server on the internet, you then connect to that server to communicate with your Classic. After installing, use this command to start up the tunnel:

Code: [Select]
./ngrok tcp 192.168.0.225:502

Which instructs ngrok to forward tcp port 502 from IP address 192.168.0.225. In my system, the Classic is on IP 192.168.0.225, while my Raspberry Pi is on another IP address on the same network.

And the tool then shows this:

Code: [Select]
ngrok by @inconshreveable                                       (Ctrl+C to quit)
                                                                               
Session Status                online                                           
Account                       Matt Sargent (Plan: Free)                         
Version                       2.3.35                                           
Region                        United States (us)                               
Web Interface                 http://127.0.0.1:4040                             
Forwarding                    tcp://0.tcp.ngrok.io:19146 -> 192.168.0.225:502   
                                                                               
Connections                   ttl     opn     rt1     rt5     p50     p90       
                              0       0       0.00    0.00    0.00    0.00     
                                                                             

All I have to do now is connect the LocalStatusPanel to 0.tcp.ngrok.io and use port 19146 instead of 502.

Once you are done, hit Cntrl-C and the tunnel is taken down. On the free version you get a new server and port every time, if you pay, you can setup one that does not change. But to be honest, it is a security risk so use at your own risk. I setup the tunnel, do what I need to and then take it down, but it works great!

Matt
4
Fair enough boB...but what about Net WbJr. Ah? As I tried in my last post to make the case, this alone would go a huge way toward enabling LiFePO4 owners to charge and discharge their battery banks in a way that protects them very effectively.
Can we hope for a firmware change that would let us toggle Aux outputs based on + and - Net Ah set points???
5
Lithium / Re: Bought new LifePO4, 24V/400AH with internal BMS
« Last post by Steve_S on November 19, 2019, 12:26:56 PM »
Just a quick addition,  The pack Arrived November 19th, all 71Kg / 156lbs of it.  See the link above for the ongoing thread on this pack.
6
Thank you boB.
If the people you chat with need to chat with someone who can make a compelling, air-tight, overwhelming, stupendous, powerful, stunning, powerful case for these two enhancements, send 'em over to me and I'll work my persuasive magic.  Oh, and did I mention that with these two enhancements sales of Classics will spike by at least 20%?  Yup...
--Paul, aka Openplanet
7

Yeah, you won't be seeing battery voltage sense on a Classic but the new stuff has it.

I would have liked to add V sense to the WB Jr. cuz it could have used the same communications wire method.

I don't think that there is actually any jitter in the WB Jr. values themselves.  Just jitter in the Classic's charging during absorb at high input voltages.

Don't know if I remember hearing about SOC rate of change ?  Sounds like an interesting idea though.


8
Have been wanting the Classic to have a Rate Of Change of WB current as an additional means of ending Absorb,  in addition to  the present EA function.

Also,   if the Jitter of the WB current could be reduced (further),   this would be a large help for anything that uses WB currents.

boB,  you are speaking of FirmWare enhancements,   BUT,   if we could ever see battery voltage Sense terminals on a Classic,   that would be SO useful.   Know that the new covey of MN CCs all seem to have this function,   and adding hardware functions are probably not in the cards  for Classics  ...

If the rate-of-change in measured battery charge current function could be included in the FirmWare for the new CCs this would be a large plus,   here.

FWIW,   THANKS   for asking,   Vic
9
Really glad you're listening boB!
  A year's supply of blinker fluid and muffler bearing grease for your ride?

Thoughts?  Thanks!

Well, I don't drink (anymore) but maybe some blinker fluid might make me feel good.

Will chat with others about this but cannot guarantee any immediate action.

 Over and out   :)
10
Really glad you're listening boB!

So...Hear Ye!  Hear Ye!

When I had FLA I didn't pay much attention to WB Jr. net Ah, since voltage and SG together give a good read on SOC.

Now that I have LiFePO4, I'm convinced that TWO SIMPLE ENHANCEMENTS could HUGELY increase a Classic's functionality with these batteries. The most important rule LiFePO4 owners should adhere to (aside from temp constraints) is to keep depth of discharge between 20% and 80%.  The super flat discharge curve makes voltage essentially useless for this purpose, at least on a daily basis.  What voltage changes there are, are in the 10s of mV range.  While the Classic can't see those differences, your BMS can.  What to do?  Simple: (1) calculate 60% of the bank's total Ah capacity; (2) carefully study the (resting!) voltage, as reported by your BMS, as you charge and discharge, so that you can (3) establish an accurate 20% or 80% SOC point, then (4) track net Ah.

HERE'S THE KEY: If you can configure the Classic to STOP CHARGING when net Ah reaches a specified positive value, you're preventing the bank from being over charged.  If you can configure the Classic to TOGGLE AN AUX LOGIC LEVEL when net Ah reaches a specified negative value, you have a way to throw a contactor and disconnect some or all loads (but NOT the Classic!)

I know everyone at Midnite is maxed out.  So many initiatives, so little time...  But truly, these two changes in the software would go SO FAR toward accommodating the most critical needs of LiFePO4 owners.  What can we do to entice you.  Beer?  A Home Depot gift certificate?  Weekend for two at the world-famous Motel 6 in Peoria?  A year's supply of blinker fluid and muffler bearing grease for your ride?

Thoughts?  Thanks!
Pages: [1] 2 3 ... 10