I can confidently say this will not be an issue in Truckler - the continuation of ETCARS - more stable, more robust and better reporting. https://trucklerprocessor.jammerxd.dev
Hi Titanic4,
I considered the update rate speed as well. The trouble is the size of the data being fed. Many clients need to be able to transfer and receive that amount of data very quickly and lowering the time between broadcasts can create overruns with how fast a client can process a message.
Right now the JSON data is updated once per second. In certain cases the user may want to increase the update rate in order to allow the data to be updated in real time when used in virtual dashboard overlays, where such slow update rate won't look good. Is it possible to implement the option to change the update rate?
ETCARS was an online solution as well at one point where the configuration was done online.
Ah, it's unfortunate to hear that it's an online API compared to an offline solution. Still, I'll check it out :)
Sure. There is a little information on https://truckler.jammerxd.dev. Most of the information is contained in the Discord channel for what needs to happen. The latest releases are sent here: https://gitlab.com/jammerxd/truckler-client-releases. A sample snippet for receiving the delivery info is here: https://gitlab.com/jammerxd/truckler-client-releases/-/snippets/2013717. If you need additional help, use the forums at https://forums.menzelstudios.com(I managed to switch to a new provider that seems to be doing a lot better)
I am also interested in this new project. If possible I'd like to get setup for the alpha as well. :)
That's unfortunate to hear. I am interested in this new project, is there a link where I can see more information on it?
Just as an update for you I'm not going to be maintaining ETCARS. I have a new plugin for delivery reporting called Truckler that does all the delivery reporting really well. If you'd like to try that out, please let me know so I can get you setup for the alpha.
I've been using this as a temporary solution, however I cannot compile my program since I'm actually using a Node.js module to provide an API for ETCars. I'm not entirely sure the owner of that node module would want to put in the temporary solution...
You can filter out the -nan using a replace in the string before parsing it. An unusual step and a step that shouldn't be required, I know. But for now, please try that.
Possibly some JSON validation could fix this, I'm not sure. Using the latest ETCars version and the latest ATS version w/ ALL currently available states as DLC.
etcars-node-client reports the following:
Unexpected token n in JSON at position 1118
Unexpected token n in JSON at position 1118
Unexpected token n in JSON at position 1118
Unexpected token n in JSON at position 1118
Unexpected token n in JSON at position 1118
Attempting to parse the JSON and finding said position using this website resulted in me finding that the following value returns like this:
"brakeTemperature":0,
"fuelRange":0,
"oilPressure":-nan,
"oilTemperature":0,
"waterTemperature":0,
"batteryVoltage":0,
As you can see, "oilPressure" is returning dash-nan, which is an invalid JSON value.
I had a lot of problems with parsing the received JSON .... so i logged some exceptions [BTW, i use C#]
Near the bottom of the string there was a weird ,A ?? 6
value
Here is a bit larger code snippet :
"realTimeStarted": 1546 ,A ?? 6,"realTimeEnded": 0,"realTimeTaken": 102046}}}
I'm closing this issue for now. If this issue returns, please open a new ticket or open a topic on the forums.