Page 1 of 1

Telelogger

Posted: Sat Nov 24, 2018 4:45 am
by ramsaymike
Trying to get telelogger operating and not really sure how to do it... The server seems to be running on my linux machine but I can' access it. Here is what it says on the terminal:

Freematics Hub Personal Edition (built on Oct 20 2017)
(C)2016-17 Freematics.com / Mediatronic Pty Ltd / Developed by Stanley Huang

Server Host: 127.0.1.1:8080
UDP Port: 8081
Max Channels: 4

Web UI:
http://127.0.1.1:8080

Data Feed Simulator:
http://127.0.1.1:8080/simulator.html

1 channels loaded
Error starting HTTP server on port 8080
Press ENTER to exit

And on the One +:

--- Miniterm on /dev/ttyUSB0 115200,8,N,1 ---
--- Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ESP32 240MHz 4MB Flash
DEVICE ID:ESP32D04006C40A24
Nearby WiFi APs:
1: TP-LINK_27B6 (-81dB)
2: QAHOME-2.4 (-82dB)
3: NETGEAR73 (-90dB)
4: NETGEAR02 (-91dB)
5: Amped_REC33A_2.4 (-93dB)
GPS..
OK
WiFi...OK
IP...192.168.0.193
LOGIN(127.0.1.1:8081)...Server timeout
LOGIN(127.0.1.1:8081)...Server timeout
LOGIN(127.0.1.1:8081)...Server timeout
LOGIN(127.0.1.1:8081)...Server timeout
LOGIN(127.0.1.1:8081)...Server timeout
Logout...
GPS OFF

I have tried the IP of the server machine in place of the 127.. but get the same response. (I do get a response when trying hub.freematics.com)

What am missing? Any help greatly appreciated.

Re: Telelogger

Posted: Sat Nov 24, 2018 6:19 am
by ramsaymike
I missed the :
Error starting HTTP server on port 8080
Press ENTER to exit

It still does not work with no error.

And here is a bit of what I get in terminal:

1 channels loaded
41 bytes from 192.168.0.193 | Invalid VIN
41 bytes from 192.168.0.193 | Invalid VIN
41 bytes from 192.168.0.193 | Channel not found (ID:0)
41 bytes from 192.168.0.193 | Channel not found (ID:0)
41 bytes from 192.168.0.193 | Channel not found (ID:0)

Re: Telelogger

Posted: Fri Jan 04, 2019 12:06 am
by stanley
Source code updated. Multiple bugs fixed. Make sure to use latest revision of telelogger as well.

Re: Telelogger

Posted: Fri Apr 12, 2019 10:03 pm
by mcfrojd
I am running the Teleserver & Telelogger from 2019-04-11
I have the Freematics One+ rev B
Running throu wifi
Running against your hub.freematics.com works fine
My local install of teleserver works fine with SIMULATOR.
But when i try to run the One+ against my own i get this in serial output:

//
REBOOT
WiFi OFF
E (104) spiram: SPI RAM not initialized
E (104) esp_himem: Cannot allocate memory for meta info. Not initializing!
CPU:240MHz Flash:16MB
IRAM:322KB
Firmware: V12
DEVICE ID: A0HLxxxx
GPS...OK
MEMS...OK
ACC BIAS...-0.01/-0.01/-1.03
OBD...NO
SD:7572 MB total, 2 MB used
/DATA/0.CSV
...
File: /DATA/48.CSV
WiFi...OK
IP...192.168.111.215
LOGIN(xxxxxxx.se:8081)...server timeout
//

And the terminal running Teleserver gives me this:

//
37 bytes from 192.168.111.215 | Invalid VIN
103 bytes from 192.168.111.1 | Invalid data received
332 bytes from 192.168.111.215 | Channel not found (ID:4294967295)
//

Is there a way to set a "fake" VIN / ID that the server will accept?

And are the (E 104) messages from serial output someting that needs attentions?

Re: Telelogger

Posted: Wed May 01, 2019 5:43 am
by gab696
Hi,
I encounter the same problems.
I am asked to enter a device ID. but the one displayed on the serial terminal is not valid. I get a message "server under maintenance" (on the webpage)
and connection timout on the server serial monitor.
Did I need to register the ID somewhere in a file under the personal HUB folders ?
I really appreciate any helps. thanks !

Re: Telelogger

Posted: Wed Jun 12, 2019 10:02 pm
by Ketil
I fixed the problem with not being able to login with a valid device (ONE+), and just got the "server under maintenance" message. I changed a line in the file "config.js" under "htdocs" folder;

from: const serverURL = window.require ? "http://localhost:8080/api/" : (window.location.href.indexOf("localhost") > 0 ? "/api/" : "hub/api/");
to: const serverURL = window.require ? "http://localhost:8080/api/" : (window.location.href.indexOf("localhost") > 0 ? "/api/" : "/api/");


This works for me, so i hope this can help others too.