If you search my other posts, you'll see I have a camper van with a 1120 amp hour lipo4 battery system that is managed by the Rec BMS and charged via a 280x Nations alternator or Multiplus ii 3000w 120x2 inverter. I've had this setup for a few years now and one was one of the first to purchase Wakespeed's van harnesses. At that time, there wasn't a Wakespeed app and programming it was solely from dip switches or using a PC. The Wakespeed and the Rec have never worked well together when the battery is almost full, usually resulting in a contactor disconnect due to overvoltage. The Rec did enable the Wakespeed to charge the system though and I never delved into it too much as I would usually disable alternator charging when the battery was near capacity.
However, after recently burning out my alternator, which could've been for multiple reasons, I reinstalled a new one from Nations and also updated the firmware on the Rec 2.9.4, Wakespeed 2.5.3, and Cerbo 3.5~20(new beta victron ui is awesome by the way). Configured the Wakespeed via the app, which was new to me, and used the Rec BMS profile. Since then, I haven't been able to get the Rec to call for alternator charging consistently. I've only been testing it at various level of charge from 13.2-13.3X though. 
Could someone clarify three points?
1. Connections - rec bms to cerbo ve can port and wakespeed to cerbo ve can port, all configured to 250k with terminal end connector on the wakespeed to ensure no open connections on the can system. (Tine said many people connect the rec directly to the wakespeed, but when I tried this, the wakespeed didn't pass the can data through to the cerbo when the wakespeed was off (brown wire on WS not receiving power as ignition is off)
2. Wakespeed settings via app: I've tried the rec bms setting that defaults to "get home" alternator settings in case of bms failure with a float of 13.2, which may be contributory to the issues I am having, but this is what the app directs you to do when the WS is set to be slave to the bms. I'll have to drain down the battery a bit more and test today if the issue is the WS resorting to the "get home" protocol. Is anyone using the Wakespeed app to configure. I did have to disable the dvcc parameter as it doesn't allow you to use it if you don't have another shunt at the alternator vs mine at the battery. There was no way to enable dvcc without that. Does the alternator and bms still interact via the nmea2000 can system? Is a lack of dvcc the issue. If so, how is everyone getting around the shunt at the alternator issue vs the battery?
3. The new Rec BMS firmware readme.txt states, "A separate BIN file for dual bus systems is no longer required, parameter MODE 1 is UV and OV, While MODE 2 is only UV controlled by the MAIN relay. So the CHARGE relay should be configured using TASKS in the WiFi." So, how do you enable parameter 1 in the wifi interface?
