Search results

I should perhaps reiterate that earlier failures to connect made me uninstall/reinstall the sw and drivers a number of times, with system reboot between driver changes. I note that uninstall did not remove any non-default folders used. At present the executable resides in C:\Program Files...

In another link: a correspondent suggests that tx and rx are reversed in the ZKEtech-supplied (prolific) harness. Opening the clam shell shows white/TX , green/RX. Swapping these over made no difference here - ie green/TX, white/RX in the clamshell still loads as com port 10, without...

Hardwiring the CH341 adapter into the EBC-A20 allowed the software to detect a com port, but still no device is detected. tried swapping the com lines with no difference - port detected but no device id'd.

I'm looking at posts which concentrate on possibly-defective serial-usb hardware: https://diysolarforum.com/threads/zketech-ebc-a20-software-frozen.33475/ The replacement option shows 4 wires on the serial (EBC-A20) end. Serial com (RS-232, RS-422, RS485 etc) normally uses only 3 wires ( TX, RX...

Dusting off a never-used EBC-A20, V3.0.3, I find it will not identify itself to the PC software. The serial usb adapter invokes a PL2303 driver for connection on com port 10 - which is within the recommended port range, but differs from other website references to a CH341 usb-serial driver...

Using v1.2.8 of the monitoring software introduced no improvement in long-term stability in communications by UART/USB. In fact, it seemed that this rev could be counted on to reliably crash the portable PC after about 2hrs of monitoring - leaving a log file that never exceeded 255KB in...

The use of the switch failed to restore more frequent comms in a slow-running PC program instance, in succeeding trials. It WAS needed and proved capable of starting a logging session on a newly connected BMS in all instances. More accurate use of this feature would require knowledge of the...

When the BMS was first hooked up to the PC, without a charger or load, using v1.2.5 of the monitoring SW, it was not recognized as a port, until the thermistor was removed and reinserted. Although the port was then visible to the program, no comms were yet possible. The actual BMS power switch...

The physical transfer of the system had some glitches. (Be advised that a monitoring harness, meticulously and perfectly installed backwards, will kill a Daly BMS, even if each wire is individually fused. Actual connection and wake-up issues with both the BMS (low-z switch) and comm lines are...

The comms responsibility was shifted to a W7 portable machine, using a later rev of both the BMSMonitor (v1.2.5) and the driver installer, to see if the stink followed the monitoring system, for this specific BMS. The installation parked itself on Port7, the only USB port offered by the...

I'm reporting comm trials with a Daly 4S BMS on another thread, that may be of interest. https://diysolarforum.com/threads/daly-bms-pc-software-connection-issue.21126/ These show that comm integrity may be software-related, with behavioral characteristics similar to those reported...

After a number of trials at quiescent ( 0 and 2A charging), charging (80-90A) and discharging (100-120A) states, a pattern of Daly BMS to PC comms begins to form. These are illustrated in the two attached charts. Both show the time-stamped 'BMS Life' reporting intervals reported in the logs of...

After the BMS stopped reporting, managed to get datalogger and BMS back up and running. Put the BMS UART/USB interface into an 'enhanced' USB port this time. The timestamps on the log and the corresponding 'BMS Life' ticks showed that, at the time of lost comm on this last run, the comm was...

The BMS monitor PC comm function is not as secure on this 32bit WXP lab PC as you might like. Its relevance to users of more current hardware may be doubtful, though the SW was first developed to include the older environments. The period of time that the BMS will continue to communicate with...

I had trouble establishing com to Daly 4S BMS using PCMaster from DalyBMSMonitorV1.1.6. The CH340 driver insisted on installing as a port (COM12) that the PCMaster would not recognize. (it wanted COM7 - already in use). When the CH340 port was altered to suit the PCMaster, it was displayed in...

What do you mean by reboot? Is this an operator intervention?

Sounds like you're BMS is passing slowly through the zero current condition and is getting confused. It doesn't sound like it's a nonrecoverable condition, requiring manual interference, from what you've related. I have no 8S experience, but the 4S types seem pretty confused around there.