RE: CANopen and Lithium Iron Magnesium Phosphate batteries
"Al Thomason" <[email protected]> Sun, 8 Sep 2019 06:39:41 -0700
| Newsgroups | gmane.comp.hardware.bus.can |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. ------=_NextPart_000_008E_01D56610.33418720 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Take a look at Orion and Orion Jr. Their CAN subsystem is fully = configurable and you should be able to stuff in the CANopen messages you = need (if they are not already there, the util has a few pre-configed = chargers supported, one of which might be what you are looking for). =20 =20 I will take a peek at openCAN and its BMS spec, it might be a couple = other BMSs we are poking at are indeed aligned with the spec and I do = not know it. If I find any will put up a message here. =20 Best of luck! -al- =20 From: [email protected] = [mailto:[email protected]] On Behalf Of John Dammeyer Sent: Saturday, September 7, 2019 3:08 PM To: [email protected] Subject: RE: [CANLIST] CANopen and Lithium Iron Magnesium Phosphate = batteries =20 Thanks Al,=20 Yes it must be CANopen. The BMS interface thread is currently supported = on one of the 5 CAN channels. It's been moved to an external module = that does other battery centric things along with fortunatetely having = two CAN channels. It's better suited for the high message rate = transmitted by the BMS. I'll convert the BMS information now part of = the Object Dictionary of this Battery Interface Module (BIM) into = CANopen PDOs which can then join the rest of the messaging. =20 =20 If I do have to interface to other 'brands' of BMS/Battery sets then in = the long run it will be easier to modify the BIM firmware than to modify = the main controller. =20 =20 I was hoping there was an established CANopen BMS model to follow. =20 John =20 From: [email protected] = [mailto:[email protected]] On Behalf Of Al Thomason Sent: September-07-19 2:40 PM To: [email protected] Subject: RE: [CANLIST] CANopen and Lithium Iron Magnesium Phosphate = batteries =20 Must it be CANopen? =20 We have worked with Lithionics which is based on J1939/RV-C. Am working = with MG Energy and their STD addressing (11-bit) SMA protocol. We have = also done an Orion JR integration, their CAN subsystem is fully = configurable =E2=80=93 should not be an issue to configure for CANopen = if needed. (Plus they seem very EV centered) A few others in the = queue, does seem most folks have their own approach to things. We kind = of gave up with one approach and now host (5x at last count) different = CAN protocol linkages to BMS devices. =20 -al- =20 ------=_NextPart_000_008E_01D56610.33418720 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta = http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta = name=3DGenerator content=3D"Microsoft Word 12 (filtered = medium)"><style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} p.Code, li.Code, div.Code {mso-style-name:Code; margin:0in; margin-bottom:.0001pt; font-size:8.0pt; font-family:"Courier New";} span.EmailStyle18 {mso-style-type:personal; font-family:"Times New Roman","serif"; color:windowtext;} span.EmailStyle19 {mso-style-type:personal; font-family:"Calibri","sans-serif"; color:#1F497D;} span.EmailStyle20 {mso-style-type:personal; font-family:"Times New Roman","serif"; color:#993366;} span.EmailStyle21 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue = vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>Take a look at Orion and Orion Jr.=C2=A0=C2=A0 Their CAN subsystem is = fully configurable and you should be able to stuff in the CANopen = messages you need (if they are not already there, the util has a few = pre-configed chargers supported, one of which might be what you are = looking for).=C2=A0 =C2=A0<o:p></o:p></span></p><p = class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>I will take a peek at openCAN and its BMS spec, it might be a couple = other BMSs we are poking at are indeed aligned with the spec and I do = not know it.=C2=A0=C2=A0 If I find any will put up a message = here.<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>Best of luck!<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>-al-<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'> <o:p></o:p></span></p><p class=3DMsoNormal><a = name=3D"_MailEndCompose"><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></a></p><div><div = style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = 0in 0in'><p class=3DMsoNormal><b><span = style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>= </b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> = [email protected] = [mailto:[email protected]] <b>On Behalf Of </b>John = Dammeyer<br><b>Sent:</b> Saturday, September 7, 2019 3:08 = PM<br><b>To:</b> [email protected]<br><b>Subject:</b> RE: = [CANLIST] CANopen and Lithium Iron Magnesium Phosphate = batteries<o:p></o:p></span></p></div></div><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal><span = lang=3DEN-CA style=3D'font-size:11.0pt;color:#993366'>Thanks Al, = <o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-CA = style=3D'font-size:11.0pt;color:#993366'>Yes it must be CANopen.=C2=A0 = The BMS interface thread is currently supported on one of the 5 CAN = channels.=C2=A0 It's been moved to an external module that does other = battery centric things along with fortunatetely having two CAN = channels.=C2=A0 It's better suited for the high message rate transmitted = by the BMS.=C2=A0 I'll convert the BMS information now part of the = Object Dictionary of this Battery Interface Module (BIM)=C2=A0 into = CANopen PDOs which can then join the rest of the messaging.=C2=A0 = <o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-CA = style=3D'font-size:11.0pt;color:#993366'><o:p> </o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-CA = style=3D'font-size:11.0pt;color:#993366'>If I do have to interface to = other 'brands' of BMS/Battery sets then in the long run it will be = easier to modify the BIM firmware than to modify the main = controller.=C2=A0 <o:p></o:p></span></p><p class=3DMsoNormal><span = lang=3DEN-CA = style=3D'font-size:11.0pt;color:#993366'><o:p> </o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-CA = style=3D'font-size:11.0pt;color:#993366'>I was hoping there was an = established CANopen BMS model to follow.<o:p></o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-CA = style=3D'font-size:11.0pt;color:#993366'><o:p> </o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-CA = style=3D'font-size:11.0pt;color:#993366'>John<o:p></o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-CA = style=3D'font-size:11.0pt;color:#993366'><o:p> </o:p></span></p><div= style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in = 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF = 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span = style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>= </b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> = [email protected] = [mailto:[email protected]] <b>On Behalf Of </b>Al = Thomason<br><b>Sent:</b> September-07-19 2:40 PM<br><b>To:</b> = [email protected]<br><b>Subject:</b> RE: [CANLIST] CANopen = and Lithium Iron Magnesium Phosphate = batteries<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span = lang=3DEN-CA><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>Must it be CANopen?<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>We have worked with Lithionics which is based on J1939/RV-C. Am = working with MG Energy and their STD addressing (11-bit) SMA = protocol. We have also done an Orion JR integration, their CAN = subsystem is fully configurable =E2=80=93 should not be an issue to = configure for CANopen if needed. (Plus they seem very EV centered) = A few others in the queue, does seem most folks have their = own approach to things. We kind of gave up with one approach and = now host (5x at last count) different CAN protocol linkages to BMS = devices.<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>-al-<o:p></o:p></span></p><p class=3DMsoNormal><span = lang=3DEN-CA><o:p> </o:p></span></p></div></div></body></html> ------=_NextPart_000_008E_01D56610.33418720-- -- Archives and useful links: http://groups.yahoo.com/group/CANbus Subscribe and unsubscribe at www.vector.com/canlist/ Report any problems to <[email protected]>