mgiannikouris / vi-firmware Goto Github PK

On initial testing, the modem was able to connect. However, after a couple minutes it appeared to power cycle. The LED was flashing blue and red and then back to solid green while waiting to go blue for the modem connection. It did this about 5 times on a 40 minute drive. Zac also reported a couple power cycles on his first try. I was not able to capture any logs yet using python though.

When compiling with 'fab c5 emulator build' the resulting c5 devices connects to an iOS device over Bluetooth, but only for a few (<5) seconds. Then it goes away. Has been confirmed on 2 different C5 builds and iOS devices. Seems like emulator isn't keeping the BT alive?

I updated this morning and openxc-message-format is fixed. Out of habit I did a ‘fab reference build’ first. Got the below error:

config.cpp: In function 'openxc::config::Configuration* openxc::config::getConfi
guration()':
config.cpp:115:5: error: C99 designator 'APN' outside aggregate initializer
};
^
config.cpp:115:5: error: C99 designator 'host' outside aggregate initializer
make: *** [build/FORDBOARD/config.o] Error 1
make: *** Waiting for unfinished jobs....

I was able to build for cellc5 successfully though.

There is a bug in the Telit HE910 firmware that reports the GPS speed signal as 1/100 of the actual value. We've known about this for a while so I added a x100 to the signal value before publishing it. Works OK sometimes, but I'm seeing some signal values show up like {"name":"gps_speed","value":10721}. The GPS speed signal values around these instances make me think that these instances are 100x too high.

I'm also noticing that other signals like engine_speed are also wonky at times....so I'm not sure if my x100 correction is sometimes not needed (which would be unfortunate if it's unreliable) or if something more systemic is going on.

Hi @mgiannikouris, I was testing the OBD-II request-based modem this weekend. It looks like the mechanism for going to sleep is not 100% robust. Not sure if this is a modem or vi-firmware issue.

In 2 cases, I saw GPS data pushed to the server after the vehicle was off. In the first case, it looks like the modem didn't go to sleep and GPS data kept being pushed for about 1.5 hours.

In the 2nd case, the modem went to sleep when the vehicle was off, and then woke back up 45 minutes later and started pushing GPS data.

I think that the issue here is calling telit code before we are in run level ALL_IO.