-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
TeslaMS tools for telemetry data visualization
- Thread starter dirkhh
- Start date
-
- Tags
- Model S User Interface
hans
P631
I see, I misunderstood where the software runs. If you collect the data yourself then just store it in a file or mongodb and have the script periodically check the latest position data to trigger the required actions.
Yeah, because of the nature of some of these events, would prefer not to have the added delay in location gathering so we are looking to store the data in an aspx page and then go from there. Each time a new row of data comes in a new aspx page is made and then deleted. Btw, how often is streaming.js polling tesla, every 30s or more often?
When the car is active/in-motion. When parked/idle, the rate will slow down. Just FYI.
Yes, of course. I also observe occasional outages while driving where I don't get streaming data even while driving in the city
hans
P631
When the car is idle it will update once every 2 minutes. As said before, 4 updates per second while driving.
Yah, that about matches a random sample from my latest log. It seems to sway between 120 seconds and 124 seconds.
They have blocked people who make too many REST calls. But not (AFAIK) people just listening to the streaming API. It's the streaming API that gives you days with up to 250msec resolution. Not the REST API.
Has anyone been able to get visualize.js to run on a Windows 2008 server?
I had everything working with the Node/Mongodb/Streaming/Visualize combo on a Windows 8 machine and wanted to replicate it to an "always on" Windows 2008 server for data collection/distribution.
Everything is working except for getting the visualize server to fire up. When I enter the node visualize --db tesla location from a > prompt it just returns ... and a web page request times out.
I had everything working with the Node/Mongodb/Streaming/Visualize combo on a Windows 8 machine and wanted to replicate it to an "always on" Windows 2008 server for data collection/distribution.
Everything is working except for getting the visualize server to fire up. When I enter the node visualize --db tesla location from a > prompt it just returns ... and a web page request times out.
What do you mean it returns ... - do you mean literally 3 dots?
What port are you running on? It looks like there is a bug in visualize.js where the -p argument is ignored and it actually *always* runs on port 8766 no matter what you put in there.
- - - Updated - - -
I submitted a patch request to fix the -p bug...
What port are you running on? It looks like there is a bug in visualize.js where the -p argument is ignored and it actually *always* runs on port 8766 no matter what you put in there.
- - - Updated - - -
I submitted a patch request to fix the -p bug...
chargebar, climatemon, streaming, telsacmd, teslamap, all work.
Everything else with a .js extension returns an error similar to:
The term 'visualize' is not recognized as the name of a cmdlet, function, scrip
t file, or operable program. Check the spelling of the name, or if a path was i
ncluded, verify that the path is correct and try again.
At line:1 char:10
+ visualize <<<< --db tesla
+ CategoryInfo : ObjectNotFound: (visualize:String) [], CommandNo
tFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command visualize was not found, but does exist in t
he current location. Windows PowerShell doesn't load commands from the current l
ocation by default. If you trust this command, instead type ".\visualize". See "
get-help about_Command_Precedence" for more details.
Everything else with a .js extension returns an error similar to:
The term 'visualize' is not recognized as the name of a cmdlet, function, scrip
t file, or operable program. Check the spelling of the name, or if a path was i
ncluded, verify that the path is correct and try again.
At line:1 char:10
+ visualize <<<< --db tesla
+ CategoryInfo : ObjectNotFound: (visualize:String) [], CommandNo
tFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command visualize was not found, but does exist in t
he current location. Windows PowerShell doesn't load commands from the current l
ocation by default. If you trust this command, instead type ".\visualize". See "
get-help about_Command_Precedence" for more details.
hans
P631
The commands listed install as global commands when installed using "npm install -g". That means you can run them from anywhere like built in OS commands since they are added to your path.
I used to include visualize.js in the list of global commands installed but this caused other problems because it needs to be run from the from the teslams\examples\visualize directory.
I can put it back the way it was before, but in the meantime you will need to specify the full path name to visualize.js and you will have to include the .js extension or put "node" in front.
Similar threads
