Hi,
Is the Carloop compatible with the new 3rd generation devices (Boron, Argon, Xenon)?
I will be ordering a few Boron devices and wanted to know if I can plug it into the spot where my electron is now.
Thanks!
Since the new devices are not yet released, there is no way to be absolutely sure.
In terms of hardware interface, we do know there will be differences, since Particle has created an adapter; see this link:
In terms of the system firmware, and support for CAN, we can only assume it will still be supported. However, it is still an assumption for all its worth.
Also, in the particle community, I recall a post where Particle committed to continuing to support the existing hardware, meaning we can expect to still be able to get Photon and Electron devices.
I’ve asked about boron supporting CAN and they say it will not. I believe this is due to main processor change not having CAN. But a daughter board could be made with SPI/I2C controller. This pushes Carloop out of 4G/LTE I believe. Hopefully this isn’t true or someone is creating a carloop with support for this board.
There is really not enough information to be sure of anything at this point. Particle along with the Elites on community.particle.io are not revealing anything substantial.
Since we know the main processor is changing, it is a good bet that the peripherals will also be changing. We can always look into the datasheet for the new main processor to see if CAN is supported or not; even then we would not know if Particle would bring the interface out and make it accessible.
There are always solutions, but not necessarily a solution that fits every use case.
For example, you could have a Carloop attached to a Photon, which then communicates over SPI/I2C/Serial to the Boron.
By the way, depending on your location in the world, 4G/LTE might not be an option anyway.
The Boron works on NB-IoT and Cat-M1, which is not quite the ‘regular’ 4G used by cell phones.
For me in Canada, I have to stick with 3G.
More information here:
I’ve asked particle support and the processor has no CAN support. The cheapest and easiest way to go is with a daughter board with an mpc2515 style chip. If carloop is upgraded this can go on it.
Travis
I also asked to particle support (Ziran Wang from particle support) and confirm that CAN will be supported.
That’s weird because looking at the datasheet there is no CAN. I guess if they are keeping it backwards compatible then maybe they will provide an SPI device. I sure hope so!
The guy I emailed and chatted with was Rick on June 18th.
Maybe there is something special they are doing, like providing an aux CPU or providing a SPI device.
I’ve been using a raspberry pi in my car and would like to switch to something smaller like this. I haven’t used the old boards but I have pre-ordered the boron. Hopefully they either provide can or someone creates a daughter board for it.
I’ve been looking for feather boards with CAN and haven’t found any except the carloop.
Any news if carloop will support these new devices? Ive gotten my order of the new boards and would like to order a carloop if it will work.
Particle has now released some of the datasheets and reference materials for the new devices.
There is now enough information available to start our investigation whether these boards will work with the existing Carloop or not.
In the second generation devices (Photon, Electron, RedbearDuo), the STM32F10… processor supported CANbus as a microprocessor peripheral. Do the new Nordic processors have the same support? This would not be a show-stopper, but lacking support would greatly increase the magnitude of the project.
[Edit: I just did a quick searh]
I found the product specification for the new microprocessors, and I did not find CANbus mentioned anywhere:
Does the new third generation break out that functionality and make it available on the feather pins? If not, then it might mean designing a 3rd party third generation product, much like how the Duo was developed by RedbearLabs. If the hardware is brought out to the correct pins, then the feather adapter would allow that connection. If it is brought out to different pins, it would mean a custom adapter or maybe it would be simpler to design a CarloopMesh version.
There should be enough information available now to at least partially answer these questions.
On the other hand, the new devices are intended to be part of a MeshNetwork with connection to the Particle Cloud. Depending on your application, you might be better off with a second generation device. Can you elaborate on whether you need mesh capability with Carloop?
Congratulations on getting your order. I placed my order late, so I will be at the end of the initial deliveries. I just hope they are delivered before Christmas holidays so I can have a friend hand-deliver across the border during holiday travel.
I don’t really need mesh. I got the LTE boron to play with. I’m hoping to make a car telematics/datalogger/asset tracker. I’ve started this with a raspberry pi 3 but realize it might not be the best. I need a battery to properly shut it down. I’m assuming the nRF52840 doesn’t need to be shutdown properly and power can just be cut like a microcontroller.
On this thread, Rick Kas at Particle confirms that CAN is not directly supported by the Nordic processors in the Mesh products:
For anyone that needs Carloop and ParticleMesh, then you need a new design. How about CarloopMesh for a name?
The hardware would not be too difficult; refactor the board to use the featherwing specification and add a MCP2515 or similar SPI-CAN chip. However, the Carloop library will not work on its own. Most likely, a hardware driver library will need to be created or ported to support the MCP2515 to enable CAN capability.
If you do not need Mesh, then the existing Carloop with a Photon (or RedbearDuo or Electron) would be the easiest way to go. A bit more expensive in hardware than the Mesh option, but much easier for firmware development.