hi all,
this is the maiden post of a flukso newbie, please be kind ;-).
I installed a FLM with 3-phased electricity measurement using 3 current clamps and 2 pulses from EM10 DIN pv electricity counters. However, these last ones don't show up in my dashboard. I connected the + port (42) to the FLM + port respectively.
I'd like to go back to the web interface of the fluksometer to see if there's a log or any more information, but I cannot access it anymore with http://192.168.255.1 I guess this is because I have no ethernet cable between my computer and the FLM since it's installed. Through my router configuration webserver, I can see the IP and mac adress of the FLM, but I don't know if that can be used to access the FLM?
I also observe warnings when I try to see the minute dashboard. I think I get warnings for both elec, pv1 and pv2 but I can only see the 'last' warning I think as it appears above the previous ones. Does the minute dashboard make a direct connection between my computer and the FLM while the other dashboards go over the Flukso server?
Thanks for your help,
Roel
Be aware that you can either access the configuration via wire only or you change the WLAN access behavior following https://www.flukso.net/content/lan-connection-setup-connection-flukso-v2
Use google with site:flukso.net in the beginning of to search field to encounter the forum :-)
I'm assuming you're using the FLM in wifi mode. If so, just hook up your laptop to the FLM's ethernet port. Then try accessing the local web config pages.
Ports 4 and 5 seem to be configured correctly. Double check your wiring for loose connections. Make sure you haven't mixed up the polarity.
Please note that your DIN-rail meters will not be sending pulses any more since we're past sunset. You could just artificially trigger pulses by shorting the + and - pins of each of the pulse ports a couple of times.
The minute dashboard error is due to the absence of readings of your pulse ports. Once you get those up and running, the minute tab should be working fine as well. We'll fix this in a future firmware release.