shaman
1 kW
@marcos good to see this released! One question though. Why use a digital isolator + non-isolated CAN transceiver instead of an isolated CAN transceiver like the ISO1042?
Main reason is sourceability, if that is a word. I prefer to avoid part obsolescence and keep supply chain flexible. ISO1050 and ISO1042 come in rather specific packages that you can't easily replace, and they don't make the area much smaller. Its not the main concern, but using a discrete isolator and CAN phy is also cheaper.shaman said:@marcos good to see this released! One question though. Why use a digital isolator + non-isolated CAN transceiver instead of an isolated CAN transceiver like the ISO1042?
shaggythegangsta said:Hello MArcos, could you please provide some updates on what is going on with Axiom? any updates on ACIM support?
No updates in that regard. I have the kicad files ready to upload, they didn't change since we defined the general layout and pinout. I just never made the time to create a github repository to make them online, I just emailed the files to the guys that wanted them.shaggythegangsta said:would like to ask also any update on the pcb that would let us adapt let say already built powerstage from some inverter to the axiom logic board?
hockinsk said:I watched one of Arlin's videos on the Axiom he's using in his Honda and he suggests there might be Torque Vectoring possible/coming? I assume Traction Control is already possible through VESC software anyway, but are there plans for Torque Vectoring to be available or is Arlin developing this just for the Honda himself? Thanks,
hockinsk said:I watched one of Arlin's videos on the Axiom he's using in his Honda and he suggests there might be Torque Vectoring possible/coming? I assume Traction Control is already possible through VESC software anyway, but are there plans for Torque Vectoring to be available or is Arlin developing this just for the Honda himself? Thanks,
atarijedi said:Does this controller have the ability to daisy chain, so if you had 4 motors, and 4 controllers, you could connect the throttle to one acting as the master controller, which would send data to the other 3?
atarijedi said:Does this controller have the ability to daisy chain, so if you had 4 motors, and 4 controllers, you could connect the throttle to one acting as the master controller, which would send data to the other 3?
marcos said:If you want a smarter approach, the code allows to connect 1 torque input to the controller A, and over CANbus it will send torque commands to the controller B, but they will take into consideration the speed difference and reduce the torque if there is a loss of traction. Currently this only works for 2 motors. For 4 motors some firmware changes would be needed.
Its not a daisy chain, it would be a bus.
hockinsk said:I thought VESC already supports multiple VESC with multiple motors over CAN? Is that not what Vedder describes as Arrays of VESCs or are we limited to an array of two VESCs only in Version 6? How do they implement e.g. 4wd skateboard with 4 VESC & 4 Motors? Are they simply running 4 motors off two VESC in parallel over CAN link between the two VESC?