Kickstarter Bets On 'Wired' Arduino-Compatible IoT Platform 138
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.
Slashvertisement brought to you by.. (Score:5, Informative)
Some Kickstarter campaign marketing company!
Re: (Score:1)
Who gives a shit. All I wanna know is...Will it Blend?
Re: Slashvertisement brought to you by.. (Score:5, Insightful)
Re: (Score:2)
What makes it worse is the title implies that Kickstarter is backing this thing, not a Kickstarter campaign.
Campaigns don't bet on anything. To bet on something you need to use your own money. The point of a crowd funding campaign is to convince others to bet on your idea.
SPI or 1-wire bus? (Score:2)
Doesn't the 1-wire bus or the SPI bus already do all this already? Arduino and Raspi have these libraries. So is this just adding a convenient molex connector?
Re: (Score:1)
Not exactly; this is also using CAN instead of naked SPI which shifts the basic signalling from raw high/low to a mixture of 0V, 2.5V, and 5V (DC offset differential signalling) so it's a lot more resilient against signal loss issues.
The separate networking chip they're using keeps the individual CAN nodes easy to re-flash without fishing them out of wherever they're installed as well, so you can literally develop something in place like a backyard lighting system instead of having to build it on a workbenc
Re: (Score:2)
thanks. though I don't understand what's no robust about 1 wire line levels. I agree that having having a separate network address has potential resiliency advantages. but 1-wire chips already have that too.
Re: (Score:2)
differential signalling is much more robust in terms of interference suppression.
1 wire combats this by using slow speeds.
Re: (Score:2)
Sounds great from a security point of view.
All you need to do to gain access to a network is tap in to a couple of wires anywhere on a property and reflash one of the devices.
Re: (Score:2)
CAN is a lot more robust and tolerant of noise. It also allows longer cable runs. IIRC SPI is meant for short distance only.
Re: (Score:2)
SPI, no, 1 wire, yes.
1-wire can go up to 500m, depending on how many devices are on the wire. It doesn't provide much power though and it's extremely slow. You're lucky if you get ~10kbits shared between all slave nodes.
Hobby Project.... (Score:2)
CAN is just horrible. It was designed for high noise environments, but get it slightly wrong and it is a real pain to diagnose. Interoperability can be touchy.
They include *2* 32bit arm cores on the end nodes why? I am guessing they are using some off the shelf code on one of them for the networking, but come on, no real device would function this way.
Their prices are rather high for the level of functionality.
And they are asking for a very small amount of money in total - looks much more like someones pers
Re: (Score:3)
Re: (Score:1)
Ethernet requires more wires, and more expensive hardware than simpler busses, such as CAN.
IoT devices need to be cheap and low-power. Ethernet won't always be good enough.
Re: (Score:2)
Re: (Score:1)
They're thicker and less flexible than CAN cables though.
I'm curious what IoT type stuff is full wireless though. Most of what I see already has a power source (Doorbells, Lights, Smoke Alarms, Fans, AC, Washers, Thermostats).
Other things are useless with a wire (locks, can't really think what else).
Sure, this solves the janky security issue to an extent, but I'm unconvinced this actually solves the power issue.
Re: (Score:2)
Two easy ways to power a lock:
1. With a wire from the hinge side of the door.
2. Inductive coupling like the charger for your electric toothbrush.
There are a frustrating number of thermostats which must be wired in to the furnace and have wifi but don't have ethernet. Why? Why would you make the product that way?
Re: (Score:1)
It seems to me that for a home thermostat, wireless only is good enough if it's a retrofit. To add Ethernet you're going to need to run another wire through the wall, why not just use wifi and the supplied power that already exists (a reason big enough that it's worth designing around the space used and the extra however much a piece to have a niche item on every thermostat). Essentially every house already has a thermostat wire in the correct place for a thermostat.
As for the door, sure, it's easy if you h
Re: (Score:2)
worst case, I have to spin the knob
Worst case someone hacks your wifi from the street and cranks your thermostat to 90. IoT security is not great.
Re: (Score:2)
What do you mean by serious IoT stuff vs the Toys we have now?
The key reason of the popularity of wireless internet is due to the difficulty of upgrading buildings to current networking demands.
20 years ago it would be common to see Network with BNC cables. Category 5 was just started to take over. In terms to cable I think we are at Cat 7. When we hit limits on our speed we need to upgrade the building infrastructure. It is often cheaper and easier to go with wireless even if it is 5 years slower.
Re: (Score:2)
Why kind of IoT device would benefit from a wired data connection over, say, Wifi or low power long range radio?
The main advantage of a wired connection is data rate. What kind of IoT device needs more than WiFi can supply?
Re:Good idea (Score:4, Informative)
Re: (Score:2)
RFID door latches with solar power are not a bad idea. Have a key as a backup but most people can just use a card/phone for entry.
Wireless security cameras are very popular thanks to ease of installation. They usually have an SD card slot that stores the video, the wireless just being for viewing or downloading video.
Re: (Score:2)
RFID door latches with solar power are not a bad idea. Have a key as a backup but most people can just use a card/phone for entry.
We would never issue keys because the use of a key leaves a hole in our audit trail. If employees are only issued RFID tags, the log is complete unless there were "system issues", which should be limited in duration and documented. If we issued keys, even if they were only issued for the purposed of backup, we would always have to second guess the entry logs.
I'm not saying everyone needs this. But, a lot do. The unreliability of batteries and WiFi are the reason these products are consumer/hobbiest only pro
Re: (Score:2)
Re: (Score:2)
Wired cameras can have the wires cut. Hard line installation is no good if bad people with wire cutters can disable the cameras.
Back in the real word the average burglar doesn't carry a wifi jammer, most firmware isn't so flakey that loss of wifi signal results in the SD card recording failing, and these cameras are a big improvement over the alternative - which is nothing.
Re: (Score:2)
Thats what everyone thought who put in consumer wifi security...
Re: (Score:2)
But in any case, what would be the point of a wifi jammer? The burglar would still be recorded on the SD card.
I guess some cameras have an alert feature that wouldn't operate while the jammer was active, but if you rely on that for security...
Re: (Score:2)
The area is left without 360 deg cameras and no easy way to use a cell phone.
Wired camera networks start to become another investment to consider beyond just consumer wifi cameras that can be jammed.
Fall back to a SD card on a consumer wifi camera is not going to really be much use at that time in real time.
Criminal groups in different nations can import a lot of low cost once mil grad
Re: (Score:2)
What's to stop the burglar from stealing the cameras too?
Not only would they be taking the only copy of their footage, they'll also have resale value.
Re: (Score:2)
These are consumer grade IoT devices. You seem to be talking about professional, manned devices.
Re: (Score:2)
So are low cost wifi security camera networks used around the world.
Thats one part of the IoT that could "benefit from a wired data connection"
Re: (Score:2)
You'd be surprised about firmware stability.
I wouldn't be surprised if they rebooted when the wifi connection failed.
Cutting the power cord on a wifi camera also disables it too, btw.
Dome cameras don't have exposed wires either. you'd need to smash the dome first.
Re: (Score:2)
If that were my only layer of security, I'd be worried. It's not, and worst case (aside from confronting me, Smith and Wesson), would be paying the deductible on my insurance. But there are several layers between those.
Re: (Score:2)
Re: (Score:2)
Any device that needs a power connection would benefit.
If you already have to run a power cable, why not run data over it too?
You can get 100mbit full duplex along with 12+ watts of power over 4 conductors. You don't need 4 pair cat5, you could use any 2 pair 100ohm utp cable. You don't need802.3af compliant PoE, you can use cheap passive PoE.
The security camera screwed to the side of my steel garage doesn't have signal issues and only needs a single cable to provide power and data, with enough power to als
CAN-bus is patented (Score:4, Insightful)
question: why is this company seeking funding based exclusively round a *patented* interface? https://en.wikipedia.org/wiki/... [wikipedia.org]
Re: (Score:3)
Indeed, why not use a simple open protocol on top of a physical RS-485 interface. Cheap and versatile.
Re: (Score:1)
because CAN is way more safe , the collision avoidance is built into the controller and is less noise sensitive.
Re: (Score:2)
because CAN is way more safe , the collision avoidance is built into the controller and is less noise sensitive
Just because the collision avoidance is done in the controller doesn't make it more safe. It only makes it better suited for hard real time applications, because the highest priority devices have guaranteed access to the bus. The price you pay is annoyingly short packets. If your software is good, RS-485 is just as safe, a bit less real-time, but more flexible.
The high impedance during the recessive bit makes CAN more noise sensitive.
Re: (Score:3)
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.
Re: (Score:3)
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.
Re: (Score:2)
And if Siemens is used, they'll use Profibus, which is RS-485 based or Profinet, which is ethernet based.
I'm using GE, so it's
EGD
Modbus/TCP
Modbus/RTU
Vendor specific RS-485
Profinet
OPC-UA
STRP
SSI
And probably a few more that I have missed. And I have used Profibus in the past.
Re: (Score:2)
Shit! We better get right on ripping RS-485 out of oil refineries, chemical plants, and other hazardous industries around the world then!
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. Although CAN suffers from the same problem. Compare them to USB, where everything is sufficiently robust and standardized that you can buy an off-the-shelf USB device and connect it. Although USB doesn't support the cable length we would need for home wiring.
Re: (Score:3)
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 wou
Re: (Score:2)
What kind of IoT device would benefit from RS-485 over, say, WiFi or low power long range radio link?
I'm struggling to see any good applications.
Re: (Score:3)
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.
Re: (Score:3)
Re: (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.
CAN Patents are expired (Score:1)
From the link you gave, the patents are expired.
I don't know about CAN-FD, but this project does not use CAN-FD.
Or your meant trademarked? You can call it ISO 11898 instead of CAN...
Re: (Score:1)
I never owned a car. I ride a US bus (in San Jose), not a CAN one.
It gives me an opportunity to pick up second hand lottery tickets at the bus stop and consolidate my long term revenue streams.
Re: CAN bus (Score:1)
Power and open interface its called ethernet (Score:4, 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...
Re: (Score:2)
Re: (Score:2)
It's usually also easier to find an outlet for a wall-wart than installing network sockets everywhere.
Re: (Score:2)
I've been in several new houses that were not wired for anything more complicated than cable/sat tv.
I think "housing shortage" is a common issue these days and that means margins are high enough and labor in demand enough that builders aren't tacking on $10k options like structured data wiring for most new houses. Most consumers will just use a shitty AP plugged into the cable modem because that's good enough for them.
My boss bought a "custom" house in a development. He ended up having a bunch of ethernet
Re: (Score:2)
Yup. We built our home in 2001, and had it partially pre-wired, including a large open conduit from the basement to the attic (3 stories above). But, in the long run, it was mostly a waste since I'm running mostly everything over wireless.
I don't see the average consumer wanting to deal with cabling all over their home. Especially, when wireless is likely to be a much less expensive and messy option.
Re: (Score:2)
Wireless is so much easier but I find it sucks for high bandwidth. 802.11ac can't really deliver without near line of sight and 5 ghz 802.11g isn't much better.
You can play games with bandwidth steering by running multiple APs with unique SSIDs, but that's a pain, too, and its just simpler from a family tech support perspective to run a single SSID and let the fucking radios sort it out.
And of course in 2001 I lacked the foresight to consider running dedicated drops for a smarter/better access point layout
Re: (Score:2)
It's easier to just plan to use a switch for the outlying locations that need more connections. Switches are cheap and readily available. And unless your foresight is perfect and you know exactly WHERE in the room you're going to put that entertainment center, you'll end up using a switch anyway. (Do you really want a bunch of whips going to those jacks that are ten feet away? You get a much neater installation by running one whip to a switch and using short cables within the gear rack.)
If you're retrofitti
Re: (Score:2)
I agree on the switches for the most part, the problem I have is that switches require power and if you want to do any segmentation or VLANs, you have to buy more expensive switches to get that functionality. Switches are also kind of obtrusive if the use case doesn't allow them to be hidden or mounted out of the way.
There's also the nuisance factor in troubleshooting when you wind up with daisy chains. A bad cable, power or switch issue can lead to annoying failure modes that are difficult to track down.
Re: (Score:2)
The usb port embedded into a socket is useless for anytthing other than USB charging. It's just a cheap converter to give DC out of AC. As such the suitability for carrying a signal is lower than sending over the AC lines through the socket. Doesn't require new construction, just replace an outlet, it's not like those USB ports are wired beyond the socket itself.
When I had a house built 14 years ago, I had to go out of my way to have ethernet connectivity in most rooms. This was a time when tech was pr
Re: (Score:3)
Re: (Score:1)
The problem with ethernet is it's WAY too high speed for most uses, and more expensive than CAN or similar low-speed bus interfaces. This avoids the complexities of rolling your own network for transmitting between half a dozen or more items, and is meant for things like roll-your-own lighting control systems around your house or other larger-scale projects where permanently installing cabling (to specifically get away from the interference issues of wifi/bluetooth) for them makes more sense.
Also it's WAY e
Re: (Score:2)
Most of the stuff in my house communicates by Z-Wave, and reliability, range or interference never have been issues. Battery life on these dev
Re: (Score:2)
Just because Ethernet can do 10Gbps over Cat6a does not mean you have to. If you want to run it at 10Mbps that is just fine and there are plenty of switches available that still support it.
You could also use 802.3bw if you wanted, with the advantage of it actually being still ethernet but only needing a single pair.
Re: (Score:2)
Re: (Score:1)
Which requires additional equipment, and instead of running things in a chain you have to run them to the router. This is better in that say you have 2-3 nodes in a room, you run 1 wire from the master Pi to the room, then run wire between the 2-3 devices. With PoE you're running 2-3 times as much wire.
Re: (Score:1)
You can totally hook multiple ethernet devices on the same cable, or did you forget about how splitters and hubs worked?
Re: (Score:2)
"splitters and hubs" extra equipment. as I STATED, or did you NOT READ? Just what I want hubs all over the house...
Re: (Score:1)
You know what splitters and hubs are physically? Hooking some wires together... So it takes the same amount of effort to daisy chained ethernet as for the bus you propose, with ethernet wiring and connectors being a lot cheaper. Please, learn about the physical implementation of these technologies first.
Re: (Score:2)
Does CANbus have an infrastructure cabling standard? I've got Cat5 pulled to RJ45s all over my house. Am I going to have to crawl around in the attic and pull more wire?
Ethernet works. I just plug stuff in and my router provisions it with an address. It would be great if CANbus used the same cabling. And someone were to develop a smart hub that would sense the type of connected device and switch it to the appropriate bus. Although I suspect that CANbus might not work on a star topology with long runs.
ADVERTISEMENT WARNING (Score:1)
C'mon Slashdot! You can do better than this!
*two* microcontrollers per board?!? (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... [reprap.org]) 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.
Use the wall power cable for data (Score:2)
Anything else, like adding wires in the walls is nonsense.
Hard wired and behind a firewall is the ONLY way (Score:4, 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.
Re: Hard wired and behind a firewall is the ONLY w (Score:1)
Re: (Score:2)
Hardwired does provide improved security, but if done correctly wireless can be almost as secure.
That depends on how you define secure. With one powerful transmitter you can execute DOS attack on a wireless network fairly easily.
Re: (Score:2)
Not if the bad people jam all consumer wifi. That is very bad for security that will use wifi.
Re: (Score:2)
All about trade offs, and I don't think most IoT is worth the trade off. Someone is almost always home at my house. I can get up and switch on/off lights and other stuff in my house rather than doing it from my couch with my smartphone. I'm willing to pay people to come into my house to do things, except for the rare more expensive item like a replacement AC, so a physical key is all I've ever needed to get in and out of my house. I also pretty much never forget to turn off the lights or similar things
Re: (Score:2)
That would be my interest as well— wireless is just subject to too many unknowns even with a fairly robust design. I also cringe when people talk about powerline— I expect 24VDC to start taking over in the next 10 years for both commercial and residential power, with a power supply on a room-level basis. Power consumption per device simply no longer warrants 120VAC (much less 220VAC). The lower energy consumption, ability to provide backup power, and lower installation cost/ease of modificatio
Re: (Score:2)
why again? (Score:2)
300m - interesting (Score:2)
Re: (Score:2)
Good old RS485, two wires offering mutliple drops, can do way more than 300m. When pulling wires anyway it's trivial to add power wires, so no problem there.
The main problem of bringing power that far is the low voltage so relatively high currents and with it high cable losses.
CAN-bus can go away, please (Score:2)
CANbus was developed for the automotive environment and it has some worthwhile features there, but for a flexible network where you want some amount of bandwidth? No way.
In the automation world we went through a decade or more of using DeviceNET, which is just a proprietary version of CANbus. Yes it's nice that power goes through the same cable, but you have to set your throughput at 125, 250, or 500 kbit/sec based on cable length and you have to add terminating resistors at both ends. There's only one m
ESP32 are very capable ... (Score:1)
Over the past year, I started a few projects and tested several microcontrollers.
There are already several alternatives that are very capable. There is no point in using Arduino anymore with these options available.
First, you have the STM32 Blue Pill [slashdot.org] and its cousin, the Black Pill. Each sells for less than $3 on eBay. They are 72MHz ARM Cortex M3, with 20KB of RAM, and 128KB of Flash storage. I am using it to make a Goto telescope controller with USB and WiFi based on OnStep, and ported it to the STM32 plat
It's about time!!!!!!! (Score:1)