6 posts / 0 new
Last post
stoatwblr
auxbatmon oddities

Anyone know what this indicates? 

 

2023-01-21 15:29:41.686 GMT E (5222566) ovms-duktape: [lib/auxbatmon/auxbatmon.js:55] Error: alloc failed|    at [anon] (duk_hobject_props.c:1063) internal|    at push () native strict preventsyield|    at [anon] (lib/auxbatmon/auxbatmon.js:55) preventsyield|    at forEach () native strict preventsyield|    at ticker (lib/auxbatmon/auxbatmon.js:58)|    at callSubscriberWithImmediateExceptions (int/PubSub.js:1) strict|    at deliverMessage (int/PubSub.js:1) strict|    at c (int/PubSub.js:1) strict|    at publish (int/PubSub.js:1) strict|    at [anon] (int/PubSub.js:1) strict preventsyield


2023-01-21 15:30:41.686 GMT E (5282566) ovms-duktape: [lib/auxbatmon/auxbatmon.js:55] Error: alloc failed|    at [anon] (duk_hobject_props.c:1063) internal|    at push () native strict preventsyield|    at [anon] (lib/auxbatmon/auxbatmon.js:55) preventsyield|    at forEach () native strict preventsyield|    at ticker (lib/auxbatmon/auxbatmon.js:58)|    at callSubscriberWithImmediateExceptions (int/PubSub.js:1) strict|    at deliverMessage (int/PubSub.js:1) strict|    at c (int/PubSub.js:1) strict|    at publish (int/PubSub.js:1) strict|    at [anon] (int/PubSub.js:1) strict preventsyield

dexter
dexter's picture
auxbatmon oddities

"alloc failed" normally means the scripting framework ran out of memory.

If you configured a lower heap size as described here https://docs.openvehicles.com/en/latest/userguide/scripting.html#heap-memory you could try raising that. Use command "script meminfo" to see if that's the issue.

 

stoatwblr
I had a suspicion that might

I had a suspicion that might be the case. History was bumped to 168 hours (1 week) but heap wasn't touched (this was in order to better see discharge profiles)

 

 

stoatwblr
This is just after reboot and

This is just after reboot and attempting to load the 12V history web page (which failed)

 

OVMS# script meminfo
{
  "totalBytes": 524224,
  "usedBytes": 343520,
  "freeBytes": 180704,
  "largestFreeBytes": 99232,
  "memlib": "umm",
  "ummTotalEntries": 2232,
  "ummUsedEntries": 2191,
  "ummFreeEntries": 41,
  "ummTotalBlocks": 16382,
  "ummUsedBlocks": 10735,
  "ummFreeBlocks": 5647,
  "ummMaxFreeContiguousBlocks": 3101,
  "ummUsageMetric": 190,
  "ummFragmentationMetric": 42
}

 

interestingly the history page loaded a few minutes later, so the memory must be pretty close to the ragged edge of oblivion

here's what it's like with the 12V history page displaying

OVMS# script meminfo
{
  "totalBytes": 524224,
  "usedBytes": 353536,
  "freeBytes": 170688,
  "largestFreeBytes": 94272,
  "memlib": "umm",
  "ummTotalEntries": 2562,
  "ummUsedEntries": 2553,
  "ummFreeEntries": 9,
  "ummTotalBlocks": 16382,
  "ummUsedBlocks": 11048,
  "ummFreeBlocks": 5334,
  "ummMaxFreeContiguousBlocks": 2946,
  "ummUsageMetric": 207,
  "ummFragmentationMetric": 34
}

 

stoatwblr
hmmm. After bumping to 768kB

hmmm. After bumping to 768kB and issuing a reload, I see this:

 

OVMS# script meminfo
{
  "totalBytes": 786368,
  "usedBytes": 180256,
  "freeBytes": 606112,
  "largestFreeBytes": 593344,
  "memlib": "umm",
  "ummTotalEntries": 2325,
  "ummUsedEntries": 2266,
  "ummFreeEntries": 59,
  "ummTotalBlocks": 24574,
  "ummUsedBlocks": 5633,
  "ummFreeBlocks": 18941,
  "ummMaxFreeContiguousBlocks": 18542,
  "ummUsageMetric": 29,
  "ummFragmentationMetric": 3
}
W (568595) websocket: WebSocketHandler[0x3f8bcc6c]: job queue overflow detected
W (568605) websocket: WebSocketHandler[0x3f8bcc6c]: job queue overflow detected
W (568615) websocket: WebSocketHandler[0x3f8bcc6c]: job queue overflow detected
W (568635) websocket: WebSocketHandler[0x3f8bcc6c]: job queue overflow detected
W (568655) websocket: WebSocketHandler[0x3f8bcc6c]: job queue overflow detected
W (568695) websocket: WebSocketHandler[0x3f8bcc6c]: job queue overflow detected
W (568705) websocket: WebSocketHandler[0x3f8bcc6c]: job queue overflow detected
W (568705) websocket: WebSocketHandler[0x3f8bcc6c]: job queue overflow detected

The job queue messages are utterly spamming everything else

The module rebooted itself about 2 minutes after this reload

stoatwblr
All seems stable after the

All seems stable after the reload, but the history file has been erased (no big deal, the voltage traces showed it was clearly in error and only being recorded intermittently )

For some reason the Trio configuration is not picking up or recording DCDC 12V charger current (which will make checking things more difficult when I refit to the car) and there's no direct measurement of actual 12V battery net input/output available without fitting more instrumentation to the car (a 12V CAN-conneccted coulombometer would be ideal, of course, but these run to about €300 apiece and wouldn't work when keyed-off unless there's some way of storing/flushing data when power returns)

 

 

Log in or register to post comments