Hello,
my Flukso failed suddenly. First, were delivered to two analog channels any more data. After a reset (> 10 sec) I can no longer connect to the IP address 192.168.255.1. If the Flukso V2 is defective or any other default IP address used for? The Heartbeat LED illuminates continuously.
Regards Heinz
Hello Heinz,
If you have pushed the toggle button for more than 10s, the default network settings should be restored. Have your tried power-cycling the FLM and waited a minute for it to boot before trying to connect to the local web page? When the FLM finishes booting, the heartbeat LED should start to blink.
Cheers,
-Bart.
Hello Bart,
The heartbeat LED remains on after rebooting over and does not begin to flash. I can not even ping the Flukso V2 IP: 192.168.255.1. As the Flukso can reawaken to life? The LAN LED is lit after plugging in the RJ45 connector.
Best Regards Heinz
Hello Heinz,
Could you tell me what state (off | on | blinking) each of the LED's are in after booting? Could it perhaps be this state?
1/ wifi off
2/ eth on
3/ globe on
4/ heartbeat on
5/ power on
Cheers,
Bart.
Hi Bart,
yes, exactly is the status, when I pull the LAN cable goes from the eth-LEG.
With IP-scan the MAC address is displayed on Flukso but no IP address. Is there a different default IP address but the IP 192.168.225.1?
After the Flukso has provided no values, I first pressed the reset button 2-5 sec. When still no connection came, I have the reset button> hit 10 sec.
Is it possible to connect via the serial interface with the Flukso?
best greetings
Heinz
You seem to have a bricked FLM. The only way to fix this is to re-flash the FLM firmware.
A. On a Linux terminal you'll have to run following commands:
goto C;
B. For a Windows machine, use your browser to download:
1/ http://www.winpcap.org/install/bin/WinPcap_4_1_2.exe
2/ http://www.flukso.net/files/flm02/tools/ap51-flash-gui.exe
3/ http://www.flukso.net/files/flm02/bin/FLM02-1-4/openwrt-atheros-root.squ...
4/ http://www.flukso.net/files/flm02/bin/FLM02-1-4/openwrt-atheros-vmlinux....
Install winpcap by running the installer exe in 1/. Then run ap51-flash-gui.exe. Select 3/ as rootfs and 4/ as kernel files.
C. Then, for both the Linux and Windows case:
a/ directly connect the computer to the FLM via ethernet
b/ power up the FLM
c/ verify in the program trace that both rootfs and kernel are written to the FLM's flash
d/ wait until the heartbeat LED starts to blink (this might take a couple of minutes)
D. You should now be able to point your browser to http://192.168.255.1. Please note that you will have to reconfigure your FLM from scratch. Make sure the synchronization to the Flukso server is successful when saving the sensor settings.
Cheers,
-Bart.
hello bart,
Thanks for the detailed instructions. The flash of the FLM firmware worked perfectly.
Now the Flukso works again like new!
I like Flukso!
Many greetings heinz
Hi Heinz,
Good to hear the FLM is up and running again. Did you use a Linux or a Windows machine for flashing?
Cheers,
-Bart.
Hi Bart,
Flash I've done with Windows 7.
Two information should be in Flash description possibly complemented:
1. Host IP address from the computer to flash convert 192.168.255.100
2. Flash software on the host computer to start and then turn on Flukso
Thanks again for your help!
Regards Heinz
Hi Bart,
I seem to have the same problem with my FLM. I recently moved house and ran into this when re-installing it. They only thing I can think that may have triggered it is and interruption during boot up or an interruption during upgrade. I can't connect to the device and have all lights except the WiFi on with no lights blinking.
I've tried running your above procedure through parallels on a Mac running windows XP. Also updated the root and vmlinux links to FLM02-2-3 and downloaded these successfully. Then tried running the software but it doesn't seem to be writing to the FLM. The program trace reads:
No packet
stderr:Non arp received. Make Sure, the device is connected directly!
I once saw it read something like:
Expected... 46... received 60
But apart from that just iterations of the above two lines in random order.
Any ideas would be greatly appreciated.
Hi Bart,
I got it working, had to use a windows machine (was using windows via parallels, I'd say there was a network within network thing going on between the MACOS and Windows XP with the parallels set up). Also had to go into the TCP/IP V4 settings and change my computer's IP address to 192.168.255.100, then once I had the correct network selected in the ap51 program it started sending through the data. The Flukso meter took quite a while to reboot (was worried I was back to square one) but it did eventually and is now connecting with my computer via a ethernet cable. Need to try to reconnect with the internet etc tonight when I get home again.
Cheers,
Richard
Gooday Bart
Ive tried to get mine going again using the above method.
The message I get repeated is
No Packet
No packet
etc
Please advise what to do next?
Currently power and heartbeat (still) and eth when pc plugged in.
Thanks Bazzle
Bart
Ive sent you an email but had no response. :(
If anyone else has any ideas please add.
Thanks Bazzle
Now out of frustration I accidently clicked "remove" and lost my Flukso account.
It would of been nice if it said" are you sure"
Bugger.
Come on Bart please answer here or my email.
I now also need the FLM account restored.
Baz
Just type in the FLM's number printed on the back and it is available again...
Thanks Geb
Any idea how to reboot the flm?
Baz
Log into the FLM via ssh (on a PC use PuTTY) and type command "reboot"... (this is actually the same as power cycling) or what is your question?
as above
FLM has stopped .
Only has power and heartbeat lights after a power outage.
I tried the method from Bart in this post above but only get
No packet
No packet
etc.
When I try to ssh etc into FLM it just times out...
New Here:
https://www.flukso.net/content/no-ip-connect