Slashdot Mirror


Kickstarter Bets On 'Wired' Arduino-Compatible IoT Platform

L-One-L-One writes: Most IoT home projects today are based on Wi-Fi, Bluetooth, Zigbee, and friends. But this is not always the ideal solution: you end up swapping batteries frequently, which becomes annoying quite quickly. You also have to deal with signal strength issues and interferences. To address this problem, a new Kickstarter campaign called NoCAN is proposing an Arduino-compatible internet-of-things platform based on wired connections that combine networking and power in one cable. The platform uses a set of cheap Arduino-compatible nodes controlled through a Raspberry Pi. The network uses CAN-bus and offers a publish/subscribe mechanism like MQTT and over-the-network firmware updates. It can also be controlled by a smartphone or tablet. Even with such features, can it succeed in going against the all-wireless trend? We'll know in a few weeks.

16 of 138 comments (clear)

  1. Slashvertisement brought to you by.. by viperidaenz · · Score: 4, Informative

    Some Kickstarter campaign marketing company!

    1. Re: Slashvertisement brought to you by.. by Zero__Kelvin · · Score: 5, Insightful

      This is 100% in the spirit of the original Slashdot I assure you. The fact that you have no interest in such things suggest that you might prefer other news sources.

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  2. CAN-bus is patented by lkcl · · Score: 3, Insightful

    question: why is this company seeking funding based exclusively round a *patented* interface? https://en.wikipedia.org/wiki/...

    1. Re:CAN-bus is patented by religionofpeas · · Score: 2

      Indeed, why not use a simple open protocol on top of a physical RS-485 interface. Cheap and versatile.

    2. Re:CAN-bus is patented by Anonymous Coward · · Score: 2, Informative

      It was developed in the 1980s. The patents have expired (except on the new CAN FD parts of the system).

      Also, you realise that Bosch Automotive is a components supply company? From its inception, CAN was always available under quite reasonable licensing terms, as Bosch had an interest in spreading the technology throughout the automotive world.

    3. Re:CAN-bus is patented by thegarbz · · Score: 2

      because CAN is way more safe

      Shit! We better get right on ripping RS-485 out of oil refineries, chemical plants, and other hazardous industries around the world then!

      Facetousness asside, if we can happily run RS-485 at speed with many multi-drop components along several hundred meters running under HV power lines, I think our Internet of Shit devices will be just fine.

    4. Re:CAN-bus is patented by OzPeter · · Score: 2

      because CAN is way more safe

      Shit! We better get right on ripping RS-485 out of oil refineries, chemical plants, and other hazardous industries around the world then!

      Facetousness asside, if we can happily run RS-485 at speed with many multi-drop components along several hundred meters running under HV power lines, I think our Internet of Shit devices will be just fine.

      While raw RS-485 is fine, many of the container port cranes I am involved in building actually run CANbus for particular I/O runs.

      --
      I am Slashdot. Are you Slashdot as well?
    5. Re:CAN-bus is patented by drinkypoo · · Score: 2

      Serial makes sense because sometimes you don't want a battery nor a mains connection. For sensors and the like, of course. PoE doesn't daisy chain, serial does.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:CAN-bus is patented by thegarbz · · Score: 2

      In this case, engineers are testing and qualifying each device. It's not like an end-user just buys an RS485 device and plugs it into the bus.

      Oh wow, have you got an over-inflated view of engineering at these facilities! No it's quite literally buying off the shelf parts and plugging it into a bus and hoping for the best. There's a special place in hell for those people who leave it up to the commissioning technician to identify a common set of speeds, parities, and other settings that devices support. Bonus points for using something like modbus and from a vendor which used a non-standard way of storing data.

      On a consumer level these devices would suffer a problem of pre-configuration. The USB specification has it's flaws too, such as dragging the entire bus down when low speed devices are connected via a hub, but when the specification is configurable and doesn't auto-negotiate you're going to end up with grief, like we used to in the RS-232 world.

    7. Re:CAN-bus is patented by AHuxley · · Score: 2

      Security as in anything that can be jammed on consumer wifi. So wired is getting interesting again for low cost security products.

      --
      Domestic spying is now "Benign Information Gathering"
  3. Power and open interface its called ethernet by johnjones · · Score: 3, Insightful

    Use ethernet or you could go with a wireless standard like Wi-Fi for high bandwidth or Bluetooth for low power local

    dont give these fools any money...

    1. Re:Power and open interface its called ethernet by maxrate · · Score: 2

      An ethernet network is generally star-topology - everything has to go back to switch or switches. A CAN bus doesn't need all the connections to come back to a central location on an individual/device basis. This saves on having to install 'home run' wiring back to a central point per device (or group of devices). This could save a lot of ethernet ports too - saving space/power in a central location. If someone created a similar looking device with two ethernet ports per device (to support a non star-topology wiring arrangement), I could see a number of issues including power, number of hops, over all unit cost, software (reboot a device and the whole chain drops - or a device goes 'bad' and the whole chain drops out, etc. Really comes down to enthusiasts who are willing to put the effort in to run cable. There are situations where a mix of wireless and wired nodes would be ideal. Personally, I'd be interested in the device they are creating. Most IOT devices require little bandwidth. If a high bandwidth application is needed, ethernet / wifi / bluetooth = yes.

  4. *two* microcontrollers per board?!? by ecloud · · Score: 4, Interesting

    STM32F0 and SAMD21... so it's not cheap and can't be.

    Is the connector standardized for CAN? Otherwise they could have picked one that's easy to install by crimping, like RJ11. We've already been there with the Dallas one-wire networks: either use RJ11 to have power, power ground, signal and signal ground, or RJ45 because those connectors are more readily available and some extra pins are there just in case. Or maybe use an audio connector, for convenience and robustness, although those are more trouble to make up your own cables.

    But there are other standards for a reliable low-speed low-wire-count low-compute-power network. But differential signaling is a must, and higher voltages help to make it more robust too.

    A worthwhile next step would be to get an open core design for one of these incorporated into a next-gen Risc-V based microcontroller. Then all the makers could get behind it, just to support the open-IP ecosystem.

    Remember when RepRaps used RS485 between components? (e.g. https://reprap.org/wiki/Extrud...) And there have been smart stepper motors. I kindof thought that idea was going to take off, early on, but most seem to have decided it's cheaper to centralize the logic and the stepper drivers on one board. But that doesn't scale to larger machines. If CAN has an advantage over RS485 for that, it might make some sense; but I still think one micro ought to be enough to implement it; and if it's not, then CAN is probably the wrong choice.

    Wireless is popular, but every device needs power so nothing can really be disconnected for the long term, unless it runs from solar power. (Batteries either have to be plugged in to recharge, or else they are environmentally unsustainable. Or both.) And there is the ongoing suspicion that RF exposure might cause health problems too. Whenever that risk finally hits the majority's radar, which technology is going to be in position to be the next contender? LiFi could be fairly easy I think.

    I had an idea years ago to incorporate optical fiber into every power cable and every power outlet (simply standardize the position on the plug, relative to the other 3 prongs, assuming a choice of fiber technology such that precise alignment isn't necessary), so that when you plug anything in, you get networking at the same time. But that's a chicken-egg problem.

    Alternatively, find a way to make one of the powerline networking standards cheaper. We can't get away from in-wall wiring to power stuff; so, one way or another, the network and the power wiring ought to be combined, IMO.

  5. Hard wired and behind a firewall is the ONLY way by geekprime · · Score: 3, Insightful

    Hard wired and behind a firewall is the ONLY way to use any device that interfaces to my real life.
    Call me a luddite all you wish, but you can't fuck with my locks, lights, freezer or whatever else I might care to control.

  6. Re:Good idea by Jaime2 · · Score: 3, Informative

    The main advantage of a wired connection is the lack of batteries and a consistent connection. Would you ever consider installing RFID door latches in an office that were dependent on batteries? How about a security camera that could be trivially disabled, from outside camera range, with a $10 signal jammer.

  7. Re:Hobby Project.... by Shirley+Marquez · · Score: 2

    They chose to use the SAMD21 as the main processor for Arduino compatibility - it's the same processor that is used in the Arduino M0. But it doesn't support CAN, so they put in a cheap STM processor to act as a dedicated CAN controller. It's rather like how the Arduino Uno uses a second ATMega chip as a USB controller - because it's cheaper than the FTDI chip that they used in previous Arduino products.