Gateway device

[tbowmo]

I've started using KiCad for this project.. Still it's far from completed (things are progressing more slowly with this one, than the last, as it's a bit more complex and I don't have that much time at hand now..

Anyway, I have created a github repository of it, if anyone wants to have a look, https://github.com/tbowmo/MySensorGW

Current schematics are here (PDF file)
MySensorsGW-schematic.pdf

It's still a Work In Progress.. A lot of stuff needs to be ironed out..

[Anticimex]

@tbowmo
Looks good. Perhaps add some header to break out a few I/O:s for future feature expansion? Like the SPI bus or i2c for a WiFi module or similar.

[tbowmo]

@Anticimex

There will eventually be footprints on there for wifi / ethernet modules.. And Yes I2C should go to a pinheader. SPI is already at a pinheader (kindof). As it's connected to the ISP header

I'm trying to get a grip on my thoughts, and create some parts for wifi/ethernet modules..

[tbowmo]

So decision time..

For wired ethernet, it seems that we have 2 options:

• w5100
• enc28j60

I haven't got that much experience with theese devices, so which one should we go ahead with?

Wireless, I think that I am settled with esp8266, but if there are anything else out there, that might be better, then please let me know..

At the moment I can't really decide which one is better So need some help from the community.

[Anticimex]

I use the W5100 on my current gateway, and I have not had any significant issues with it (apart from the infamous SPI issue, which is resolved by controlling the SPI_EN signal to the W5100. Apart from that I am happy with it, and it is intelligent enough to allow the necessary software to fit an Arduino Nano. Unfortunately not with DHCP enabled (and signing support enabled). But if the enc28j60 does not require more software, and handles SPI(?) "properly" perhaps it would be the better alternative?

[tbowmo]

Hmm.. seems that W5100 has a complete TCP/IP stack on board, where as the enc82j60 only has MAC hardware, so the tcp/ip stack needs to reside in the host controller.

So W5100 it is..

And ESP8266 for the wifi (so far)

[tbowmo]

been playing around some more with things..

MySensorsGW-schematic.pdf

currently the PCB is 5x5cm.

[axillent]

@tbowmo thank! it is a good job done!
some questions/comments

• w5100 SPI fix is already inside modern arduino ethernet shield http://www.arduino.cc/en/uploads/Main/arduino-ethernet-shield-06-schematic.pdf
  do you think it is needed? what kind of the shield your are looking for?
• why not to put 20MHz crystal to give some more performance to the gateway?
• USB is normally can supply not more than 500mA, are you sure it will be sufficient? DC-jack probably will be also good to have. ESP+wisnet could be hungry for the supply
• why atmega1284? it is not a standard arduino choice but could costs on a level of 1280. atmega128 is the lowest cost 128k AVR. If we are sure 128k will be sufficient in the future I will select atmega128 because of cost or atmega1280 because it is standard for arduino
  And also I will consider atmega2560 to have a maximum possible resources (not only flash but also RAM)

[tbowmo]

@axillent said:

@tbowmo thank! it is a good job done!
some questions/comments

• w5100 SPI fix is already inside modern arduino ethernet shield http://www.arduino.cc/en/uploads/Main/arduino-ethernet-shield-06-schematic.pdf
  do you think it is needed? what kind of the shield your are looking for?

I was looking at the cheap Chinese breakout boards with W5100 chip on, not all of them have the SPI fix onboard, so that's why I implemented it.

• why not to put 20MHz crystal to give some more performance to the gateway?

Hmmm.. think it was a price thing.. 16Mhz was more common than 20Mhz. But can't remember it right now (it's been a couple of weeks since I put in the 16Mhz xtal)

• USB is normally can supply not more than 500mA, are you sure it will be sufficient? DC-jack probably will be also good to have. ESP+wisnet could be hungry for the supply

In my thoughts, it should be either W5100 or ESP8266 mounted, not both at the same time (since both is for "internet" access. Also, most phone chargers are delivering 1A and up. Also, if you connect the thing to a computer via USB, you might not want to use W5100 / ESP8266 to communicate with it, so those power eaters could be left out in that case, leaving only NRF and/or RFM69 as radios.

• why atmega1284? it is not a standard arduino choice but could costs on a level of 1280. atmega128 is the lowest cost 128k AVR. If we are sure 128k will be sufficient in the future I will select atmega128 because of cost or atmega1280 because it is standard for arduino

There are some people that are using atmega1284 with arduino IDE, so it can be used. Solderability is the first reason: atmega1280 is 100pins, while atmega1284 is 44 pins, price: atmega1280 is 15.96$, while atmega1284 is 8-9$. Of course I can see the point in putting in 1280, as it could be swapped for a 2560 if more flash/ram is needed.

And also I will consider atmega2560 to have a maximum possible resources (not only flash but also RAM)

Atmega1280 is pincompatible with atmega2560, so they are interchangeable.

Anyways, this is mainly playing around with KiCAD, and creating something that might be usefull along the road :). Design is not locked yet, so I'll take a couple of iterations on it (just like I did on the sensebender micro, with selecting powersource, and sensor types).

[axillent]

@tbowmo 20mhz should cost very similar to 16mhz, price is not an issue in this choice. Frequency is one of the parameter you will need to put inside boards.txt, it could be no issue to replace 16 by 20

ok I see. if soldering is an issue there is also atmega1281/atmega2561 pin compatible having TQFP64 package while been fully compatible with atmega1280/2560 (they do have single datasheet). Their maximum xtal is 16mhz

[tbowmo]

@axillent

As I said, I can't remember why I decided on the 16MHz crystal... it could have been a decision based on baudrate accuracy. But I'm not sure now.

one thought, is the arduino spi library capable of using the extra spi ports on the atmega1280? (The 4 uarts can be reconfigured as spi ports)

Started debating with myself, the benefits of changing cpu I'll look further at the data sheets.

[axillent]

@tbowmo I'm not sure that arduino SPI library can deal with USART as SPI at all
but it could be no problem to write down a peace of a new code to use USART as SPI

why you need 5 SPI's?)

[tbowmo]

@axillent

why you need 5 SPI's?)

Just a thought on versatility, that's all you could have ethernet hanging on one SPI channel, and NRF / RFM on another, giving higher throughput (Ok, I know that it might not be necessary in this project at the moment..)

Btw. just had a look at the datasheets for atmegas. 1280 / 2560 / 1281/2561 has 8Kb ram, while 1284 has 16Kb. Also operating frequency, 1284 is specified up to 20Mhz, while 1280/2560 etc. is only 16Mhz.

So many parameters to choose from

[axillent]

@tbowmo said:

giving higher throughput

ohh) the logic coming from PC world not working here. regardless how many SPIs you will initiate MCU will handle them in a sequence.
but any way it could be a benefit
for example you can avoid SPI fix if there will be exclusive SPI port used for wiznet

So many parameters to choose from

on other hand it is good. atmega644/1284 are from later generation having more features. 16k RAM is a very good thing, gateway potentially could be hungry on RAM usage. The disadvantage is missing 256k version

for last resort I will ask @hek to request quotes from partners to understand better the price difference.

[tbowmo]

@axillent said:

@tbowmo said:

giving higher throughput

ohh) the logic coming from PC world not working here. regardless how many SPIs you will initiate MCU will handle them in a sequence.

as they are in HW, they operate independently. So you can have two channels receiving at the same time, and another transmitting. The CPU just needs to put the bytes into the tx buffers, and pick up from the RX buffers.

but any way it could be a benefit
for example you can avoid SPI fix if there will be exclusive SPI port used for wiznet

Yes, when I started looking at the GW, I had in mind using multiple SPI ports just for this. I know that we can use Soft SPI, but i would rather have it as HW implemented as it would offload the MCU for handling the SPI signals.

Anyway, the SPI fix is a single gate that is placed on the board. the cost is at 0.5$ as far as I remember (mouser prices).

So many parameters to choose from

on other hand it is good. atmega644/1284 are from later generation having more features. 16k RAM is a very good thing, gateway potentially could be hungry on RAM usage. The disadvantage is missing 256k version

for last resort I will ask @hek to request quotes from partners to understand better the price difference.

I had thought about the same, asking our HW partners in china for the price differences.

[RJ_Make]

Looking Good!

[marcusvdt]

Can't say much other, than I'm excited to see where this is going... The only thing that I would like to vote for, is that you keep the atsha chip on board (not optional).

Thanks for your hard work!

[tbowmo]

I just ordered both ESP8266-01, and a W5100 breakout board, of the types that I think would be usable in this design (Both of them are available from iTeadstudio btw). Just to have some mechanical samples that I can measure dimensions, and connector placements.

So will wait for them to arrive from China.. I will also try to fit everything on one side of the PCB, right now I have an FTDI chip, and a capacitor on the backside (besides a footprint for the RFM69 pcb, which is up to the end user to mount).

ATSHA204 will be a mandatory part of the design anyways. We can just as well put in some security measures in our designs.

[tbowmo]

@axillent

Just tried to create a new stanza in the boards.txt file, defining a board with an atmega1284p MCU. Seems like arduino accepts it, as I am able to use Serial1.begin(); in my code. If I switch back to compile it for a standard atmega328p target, it fails on Serial1.begin(). Also Serial2.begin() fails on atemega1284p target, so this indicates to me that it knows about this CPU from the beginning.

So from an arduino point of view, there is no problem in using atmega1284(p) as target device. (I haven't got one on hand, so can't do any specific testing besides trying to compile things).

[axillent]

@tbowmo sure
in general arduino can handle any AVR8 from atmel
my comment was about "not a standard arduino MCU" means it is not described inside official board.txt

if i'm not mistaken atmega644 (same family as atmega1284) is used in reprap and it is arduino too

[plinioseniore]

Hi,

this is my first post and I've pointed here by @hek while discussing of MySensor and Souliss (that is a project similar and different at same time from MySensor).

Just yesterday we got Souliss running on ESP8266 thanks to the porting of the Arduino cores on that MCU, this is an option that in my opinion you should take in account. The use of ESP8266 (and generally of all other) as WiFi to USART isn't impressive, I've never been in love with AT commands and I prefer binary communication compared to ASCII, but generally your AVR USART became your bottleneck.

Compared to SPI, USART isn't a master/slave protocol and the communication is driven by the transceiver, this is a really mess. When you use SPI, your low-RAM AVR decide when read data and this allow you to use the RAM of the transceiver as an external buffer, the tranceiver has mostly more RAM than the AVR.
While running over USART, the transceiver send data when want, so you should care on the AVR of buffering and process the frame only once is complete.

More, the ESP8266 has multiple firmware release that doesn't provide a consistent behavior, so you end-up with a your own firmware to bridge data to USART. But once you need to program the ESP8266, you are just a step away to load on it the whole code.

Hope that this can help.

Regards,
Dario.

[tbowmo]

@plinioseniore

You got a couple of good points there.. So your advice is to find a SPI device for WiFi instead of the ESP8266 module?

Been looking for it, and only found CC3000 module, which (if I remember right) have problems with stability. Is there anything else out there that is affordable for WiFi connection, and usable from Arduino?

What I want in this device, is to have multiple connection methods, that is you can have nrf24l01+ for 2g4 sensor networks, rfm69 for sub 1Ghz sensor networks, and then choose between wired or wireless LAN connectivity to your controller (or serial, if that is wanted).

At the same time, we need to have security in mind, and support the standard authentication methods that is available for mysensors by now (using ATSHA204 chips).

I haven't looked that much at the ESP8266 as a platform thing, but it might be limited as a target platform, if we want to have all the different technologies connected.

[plinioseniore]

@tbowmo

Actually there is really no reason to still use AVR, while there are good reason to use Arduino. I mean, ESP8266 is a SoC that contains both MCU and WiFi radio, you can program the MCU directly and run on it what you need.

Actually there is a porting of Arduino (as core of libraries and methods) to the ESP8266 that is very stable and let you run your own code on the module itself, without have an AVR in between. The ESP8266 has also SPI hardware support, that can give you the way to interact to common radio like nRF24 or RFM69, even if some porting will be required to get the goal. Actually we have just ported Souliss and running over ESP8266 and is really working smoothly.

In terms of hardware there is no one good answer, mostly depends on your (and MySensor) architecture. The Souliss architecture support multiple bridge and routers, with RF and RS485 communication, so it makes sense for us to have nodes based on microcontrollers, this keep power usage and complexity low.
But if you have a start architecture (and probably MySensor has, correct me if I'm wrong) it may also make sense to move to OS based devices with an RF radio to join small and cheap microcontroller nodes.

I know that design need a full stop, otherwise ideas storm far away from the goal. I'm just here to say that use a WiFi to USART device as transceiver for a 2Kbyte or 8 Kbyte RAM microcontroller is a bad design, and in my opinion non-WiFi RF may have short life in smarthome solutions.

What I saw in the three years running Souliss, is that further you try to automate, more likely you end up into a central point of decision, that is an OS based device. So you likely will be into a native WiFi or Ethernet device and this lead to use those technology widely, this is likely if you cannot run new cables. If you can run cables, RS485 looks still a good solution.

Regards,
Dario.

[hek]

Thanks for the feedback @plinioseniore .

Yes, but still, isn't power consumption a bit too high on these puppies to use them for battery operated devices?
Last time I checked they were like 10x NRF. And I imagine powerup/reconnect time to a wifi network is much longer than the parts of a second we see for NRF24L01.

Still it it would be very interesting to get the MySensors library up and running in an ESP! The more options the better. There isn't really any platform quirks or libraries used in the development branch.

For a ESP <-> NRF/RF69 gateway device, power consumption is not an issue. And I agree that it is bad that the USART communication is slow (and non consistent between versions) but it should still be able to shuffle around 70 (MySensors) messages per second at a moderate 19200 bps.

[plinioseniore]

@hek

It mostly depends on what you need, as pointed before, my problem wasn't the USART speed it self.
But that I was no longer able to use the transceiver as a buffer, because is the transceiver to decide when send data over the USART, rather SPI as master allow the MCU to decide when get data.

This is a problem with ATmega328 that has much less RAM that the transceiver that is attached to, but of course depends also on the average lenght of the frames that you over the air.

Dario.

[tbowmo]

Ok guys, I need some feedback before I start routing PCB again (for the 10th time :))

Could some of you please look at the schematics, and see if I have missed something? Also, I have made some design decisions lately, where I removed LEDs / buttons, and placed a pinheader for MMI. I have also added an extra pinheader for the unused GPIOs

MySensorsGW-schematic.pdf

Also, for refference, here are a 3d drawing of the current component layout.

It's designed so that antennas for NRF module / ESP8266 is hanging over the edge on the board (in the bottom of the picture), and W5100 board is having the ethernet connector besides the micro usb connector (which is top right of the picture). ISP programming header is located on the bottom side of the PCB, as it's only needed for initial development.

This is still a conceptual thing though..

So any comments, please?

[Anticimex]

KiCad FTW!

Looks good to me. I have been able to run the ATSHA SDA pin without a pull without problems but I do know Atmel recommends it so I guess it might be good to have. It should not need to be of any high precision so it ought to be cheap.

[tbowmo]

@Anticimex

It doesn't cost anything to add footprints for extra pullup resistors, or decoupling caps. (Other than some time placing them). So I am throwing it in wherever I can..

I have sticked with 0603 components btw. So it should be easier to hand solder the first prototypes

The board is still 5x5 cm, probably being 4 layer so I can get room for all the wiring.

[Anticimex]

@tbowmo
Ah, did not see a no-mount indicator for it so I assumed it would be mounted by default. I agree on keeping all options open if space allows for it.
Yes, you probably have to go 4-layer on that. I had some trouble fitting the routs on my sensorboard in that space. And it has less components.

[tbowmo]

@Anticimex

Havent set any components as NM yet just throwing components iñ at the moment

[RJ_Make]

I'm sure I missed it but..... as it stands this can be used as a serial gateway correct?

[phil pritchard]

@tbowmo

re: PoE supply
http://www.freetronics.com.au/products/power-over-ethernet-regulator-8023af#.VWCsPLmqqko
is cheap and easy you may be able to piggy back it on the board.
hope it helps
phil

[tbowmo]

@ServiceXp

It could be used as serial gateway, there's a ftdi chip onboard. But also place for Ethernet and WiFi connections, together with both nrf24 module and a rfm69 module.

Made to be as versatile as possible.

@phil-pritchard

Ethernet is an add-on module, so a bit hard to implement Poe circuitry on this board. If we could find w5100 module with Poe, it might work.

[tbowmo]

Btw. Would it be an idea to include a sensor onboard? (Si7021)

[Anticimex]

I see no reason not to (depending on available space) add footprints for various "standard" sensors in addition to a IO header on the board. I have no idea on what impact it has on the sw to have a gateway report sensor values to "itself" but I see no reason for why that could not be supported (if it isn't already).

End of double-negations

[tbowmo]

@Anticimex

What do you define as "standard" sensors?

[Anticimex]

@tbowmo
Perhaps an unfortunate label. I guess standard footprints would be a better word. I mean footprints for the most commonly used sensor cases. TO-92, DFN and etc. connected such as the typical sensors (1-wire temps and Si7021 like) will "fit".

[tbowmo]

@Anticimex

Problem is that each sensor has its own pinout, so you can't make generic footprints.

There already is a GPIO header, with 8 pins (4 analog and 4 digital) plus power. So people can make their own daughterboards with sensors. Might convert 2 of them to i2c bus with pull up, and then have si7021 onboard.

[plinioseniore]

Have you considered Grove plugs for sensors? This can give flexibility and a large enough number of sensors at a reasonable price.

[tbowmo]

@plinioseniore

Problem is space on the pcb as I see it Grove connectors are big and bulky. I have placed a couple of pinheaders (one 8 pin, and one 12 pins) for external devices right now..

[Anticimex]

I think a header for daughterboards will go far in terms of flexibility.

[tbowmo]

updated the first post in the thread, with links to github project, and pdf of schematics (on github). So it will always point at the latest available one, so I don't have to remember that there is a forum thread to keep updated

[Anticimex]

Nice nice. I am very interested in this as I have more or less decided to swap to RF69 from RF24. Both for range and because I like the concept of having the radio handle the encryption on my signed packets (yep, I am paranoid as hell). Unfortunately, it means my current gateway has to go but I have made a "sensor evaluation board" (got the PCBs, still waiting for components). Once I get the components and can verify all the features I put on it I will publish it in this forum for those interested. It will still rely on Arduino modules and such so it is not the hard-core approach like the Sensebender Micro though.

[Anticimex]

@tbowmo
I believe you previously had the interrupt for RF69 connected. But it does not seem to be anymore. Any particular reason for skipping that?

[tbowmo]

@Anticimex

I'm still rearranging things in the schematics, in order to get the best board layout :).

Could we go with one combined irq for both radio modules? (rfm69/Nrf24)?

/ Thomas

[Anticimex]

I see no reason why that would not work. I sure hope so as I did that on my board
Both radios will never be connected (or at least in use) simultaneously so it should be ok.

[tbowmo]

@Anticimex

could be someone got brainfreeze and decided to go with both radios at once in one setup.. On the other hand, we're not using IRQ for the nrf24 at the moment..

[Anticimex]

@tbowmo
Even so, the electrical properties of the interrupt outputs on the module should ensure no meltdown occurs. And I think the user would get bigger problems than just having to figure out the origin of the interrupt

[Anticimex]

On the other hand, is there a usecase to provide HW interrupt functionality for a dagughterboard on the gateway? Since it will "by definition" have a solid power supply, any sensors using interrupts should be fine with the soft-interrupt options (have not looked into those myself though) or simply use polling. Power saving makes little sense in this case. The radios are probably better off with "real" interrupts (if we ever use them).

[tbowmo]

been fiddling with layout, and schematics changes..

Added a couple of MAX3002E for level conversion between 5V and 3V3 domains on the board. (Links to the schematic are in the first post of this thread)

Waiting for samples of the ESP8266, and W5100 modules, so I can make some last measurements before ordering boards.

[plinioseniore]

Hi,

just want to share with you some of our progress in a board similar to the one that you are designing.

This is based on Atmega32U4 and has socket for nRF24L01 and ESP8266 and is designed to be battery operated and support Grove connector. The board has mosfet to switch off the sensor while sleeping and keep low the consumption, this should stand a year on battery.

We just received the PCB, picture at the link below,
http://www.souliss.net/2015/06/sensor-battery-board-pcb-arrived.html

The schematic and layout are open-source and hope that this board may fit some needs also in the MySensor community
https://github.com/souliss/boards/tree/master/Battery_Operated_Board/Ver1

Regards,
Dario.

[tbowmo]

@plinioseniore

Looks like a nice board you have created... Only problem is, that we run out of memory on atmega328, if we want to run with signing and have MQTT client on board.

So that is why we have bumped the processor to a atmega1284 instead, having 4 times the memory, than atmega328. Also, with this board, we have the posibility to use both RFM69 and NRF24L01 on the sensor network..

[tbowmo]

Tried to make a concept drawing, of NRF module placement

the esp8266 is placed in a similar way, on the right edge of the board, also hanging over the edge with the antenna part.

the W5100 board (which is similar to this one from itead studio) is turned 180 degrees, which makes the ethernet jack placement above the large "empty" space on the board (there is a 2x3 pinheader in the concept drawing)

The micro usb connector will be just beside the ethernet jack. between the ether jack, and the single pinheader pin (this is the antenna connection point for the rfm69 you can put on the bottom of the board)

Things are still a bit conceptual, trying to visualize it for my self

[rickmontana83]

I'll second (third? fourth? whatever...) the suggestion to design this to fit a cheap and readily available enclosure. Something like:

http://www.aliexpress.com/item/Free-Shipping-Plastic-Waterproof-Clear-Cover-Electronic-Project-Box-Enclosure-Case-85-58-33MM/2025247551.html

(Not saying that's ideal; just an example.)

[tbowmo]

@rickmontana83

the board is 50x50 mm, and with the radio / wifi protruding over the edge, this box should fit nicely.

The reason why I chose 50x50mm for the board size, is that it's either 50x50mm, or 100x100mm board when we order prototypes, which is more expensive. (And I like to make things small :))

[rickmontana83]

Agree about smaller. Everything looks classier with less wasted space.

Probably too late now, but if the board had mounting holes that lined up with the enclosure that would be sweet. I'm always at a loss for how to keep my boards stable inside their plastic homes. Would love to hear peoples' solutions for mounting when the holes don't line up.

[tbowmo]

@rickmontana83

nothing's too late (yet). I haven't even ordered the first prototype batch yet. Still ironing out some details, and routing the PCB (I have only scratched the routing for the 10th time or so :s ). Actually I had thought about adding a couple of mounting holes in the board..

I'll see if the boxes that I have, resembles the one that I just linked to.. (I've talked with @hek about finding some enclosures a couple of days ago, when we suddenly found a seller on ali express, that only had enclosures of various kinds).

[plinioseniore]

@tbowmo

Yes the Atmega32U4 and Atmega328 has in the RAM their main problem, in our case we run smoothly in the 2KBytes available because we don't use ASCII in the protocol, but binary only.

Then the board is for as a remote sensor node, running on battery, not a main gateway board.

In any case, the board that you are designing will work nicely also with Souliss.

[RJ_Make]

@tbowmo Mounting holes would be very good.

[tbowmo]

ok now with mounting holes. Or sort of.. the holes are 4.8cm apart, center to center, and the pcb is 5cm wide. I have used this case as a template.

[tbowmo]

and now with a w5100 module attached

[scalz]

very nice board, bravo !
thank you for sharing your work and knowledge.

[blacey]

Sweet!!!

Sign me up for 5!

[Francois]

You put a work into this board and it looks great. Cannot wait for it to come available.

[5546dug]

@tbowmo My hat is off to you, for the major effort put forth along with @blacey ,@Anticimex , @axillent and @hek to name but a few.

While following this thread at times lost (mostly?) with explanations and concepts I have been learning which is half the battle.

It seems it never too late for a old dog to learn a little.

However it seems there is a need for a better gw from some of the threads I have read.
I for one will purchase a unit in what ever form it morphs into.

Great work with all these boards.

[tbowmo]

I'm still routing the board, it's more complicated than my previous boards, so will be a bit longer process to get all in place.

[tbowmo]

A small update here, on an even larger update on the gateway device.

After some considerations, I have decided to switch the MCU for the GW to an atmel SAM D21G, instead of atmega1284. While doing this I have reduced the BOM for the GW, and cut about 1/3 of the BOM price.

The D21G is the same chip that's on the new arduino zero, and also on a kickstarter project called neutrino. @blacey is the one who pointed me in that direction

While being a more powerful chip (256kb flash, 32kb ram, 48 MHz, loads of extra peripherals) it is actually cheaper than the atmega1284, and it has build in USB controler, so the ftdi chip could be removed, a couple of other glue components is also gone now.

It will mean that we have to work a bit harder at getting mysensors running, but since the MCU is supported by arduino, we should be able to manage.

[scalz]

very interesting! I didn't know neutrino, pretty nice board. Seems there will be some work on software part but it is doable like you said. And you will have more power, which is nice for the GW I think, and I like when chip is usb compatible (like pic18f4550 ...). Maybe one day, it will become HID, lol!

[tbowmo]

@scalz

I didn't know of the neutrino (or arduino zero) before @blacey mentioned it to me, and he finally got me convinced that I should swap the atmega1284. (I know that @axillent tried to convince me to use another chip, than the atmega, before.. But when you find this, and it can reduce board complexity..)

[scalz]

@tbowmo: it is likely same things for me. lots of 8/16bits chip collection (microchip). but never moved to 32bit even if i have a 32bit usb bit wacker (not time to test it). I was thinking that you can do lot of things with 8bit chips. So yesterday, I have read a little the datasheet atsamd21. Wow, 1077 pages! But there is lots lots of features! I think I will try to order one sample for my collection! Plus, these chips seems to be not expensive but there is some learning curve on it. I think Microchip have missed a big move with arduino platform!

[tbowmo]

A couple of late night shots, of the progress..

Getting ready for the first prototype spin of the board

[RJ_Make]

That right there is a work of art!

[NeverDie]

You may be interested in this Arduino shield:

http://www.ebay.com/itm/WireLess-Gate-Shield-DIY-Maker-Seeed-BOOOLE-/171713943896?hash=item27faf2d958

It has both NRF24L01+ and RFM69HW radios.

[5546dug]

@tbowmo this gw is looking good, hope the prototypes get to you soon!

[tbowmo]

The first pcb's have arrived today.

They came a bit faster from dirtypcbs.com, than I had expected. So haven't even sourced the components yet.

So need to look into that the next couple of days.

with W5100 / NRF module "mounted" :

[RJ_Make]

@tbowmo No mounting holes?

[tbowmo]

@ServiceXp

As we need to bring things to life on a new MCU core (Cortex M0), I decided to just make a "simple" dev board, without holes. They will probably be added on the next iteration of the board. (Besides that, 3 of the corners are a bit crammed with components, so no place for the holes anyway.)

[scalz]

@tbowmo: very beautiful board. I can't wait to see how it will work. And your feedback about dirtypcb. I often use seeed for their price. But dirty seems good too regarding their shipping rates. I like osh sometimes for their beautiful boards.

[tbowmo]

@scalz

Haven't tried any of the other "cheap" board houses. But I'm glad for the quality that dirtypcbs are delivering, and the price can't be argued about..

[scalz]

thx good to know.

[tbowmo]

things are beginning to take form..

First arduino sketch are running on the GW

Proof is here

[scalz]

great

[tbowmo]

Just learned a lesson the hard way, the last couple of days.. Discovered that I hadn't read the datasheet for the atsamd21 good enough, so I had connected all the PINS for the SPI / UARTs completely wrong. Which means 10-12 connections that was wrong (the board uses 3 SPI ports and 2 UARTs, one SPI doubles as UART, depending on the network interface connected)

So new boards are in the pipeline from dirtypcbs.com

This is btw improved on a couple of other points, compared to the previous board. Biggest is, that it now has 4 x 3mm mounting holes, (happy now @ServiceXp ? :)). It also got a couple of extra solder jumpers on the backside, that could be used for software configurations, or test points.

[scalz]

@tbowmo: what a bad luck! but it is so easy to miss something when you look at the datasheet size
I hope you will get it working like you want, I am sure
I like your enlarged pads for 0402. Is it easier to solder like this? Do you handsolder it? Do you think using 0603/0805 with no enlarged pads would take same place???I am asking this for my future designs, in case. But 0402 is so small...

[tbowmo]

@scalz

I'm using 0603 components this time, as I'm not under that big a space constraint, as on the sensebender micro.

The biggest issue is the finepitched SAMD21, have to be extra careful not to make solder bridges between the pins..

[scalz]

@tbowmo: 0603, cool. I have some samd21 sample but have not tried to solder them. it looks tiny but I think I will be able but not without some
thank you for your precision

[tbowmo]

@scalz

atsamd21 comes in 3 variants, with 32, 48 og 64 pins (If I remember right). I'm using the 64 pin variant

If things go well with this one, then I might make a sensebender micro 2, with an 32 pin atsamd20 (almost the same as d21, but without USB host/slave capabilities)

[scalz]

@tbowmo: oh, i have the 48p variant. so I will try to use it in another project in the future. and will order other sample.
sensebender micro2 atsam, wow, crazy thing! could be fun to see this

[RJ_Make]

@tbowmo Now that's what I'm talking about.. Those holes look so sexy.... wait, that doesn't sound right.... :bowtie:

[RJ_Make]

@tbowmo How is the testing going?

[tbowmo]

@ServiceXp

I just received the PCBs for the second prototype spin yesterday, the first spin had too many errors in the routing around SPI / UARTS so I decided to ditch it, and do a second spin. Dirtypcbs got some hickups processing my gerbers but finaly made the boards.

I hope that I can get around to assemble one this weekend, but I can't promise anything, as I have been loaded more than 150% with work (both from my employer, and from the wife).

[RJ_Make]

@tbowmo Sounds Good, Thanks for the update.

[tbowmo]

Images of the latest pcb's (Before SMD assembly)

Unfortunately I "injured" my back today (aah, maybe not injured, but feels like it :() so I'm on strong medics to keep the pain away. That means that didn't get around to do the SMD assembly today as I planned, as I can't sit at the desk for a longer time.. hope that it gets better during the weekend.

[RJ_Make]

@tbowmo Oh now that is sexy.. From someone with back problems, you take it easy for the next 3 days Sir!!

[tbowmo]

Aahh.. I'm back in the man-cave. Been too long since I had a chance to power up the soldering irons..

Anyways, I've mounted the first of the second prototype spin, so next up is getting firmware written, and tested..

[scalz]

@tbowmo: it looks very nice. I like the way you place components. I think I need to look more at your design and learn
With a firmware, it looks promising

[tbowmo]

@scalz

Thanks I hope that I at least can get some LED's flashing tonight :). And then perhaps the bootloader programmed.

/ Thomas

[tbowmo]

And we have lights..

MySensors GW 0.7 bring up – 00:04
— Thomas Bowman Mørch

[scalz]

yeah

[tbowmo]

A small update before I hit the bed tonight..

I've got radio up and running on the SAMD, and got the first message from one of my sensebender micros through to my pc.

It's still in debug mode, using a serial port on the samd as output (And my logic analyzer to decode the serial stream). So no ethernet / wifi or the like up yet.

The next step will be to have it use USB instead of the serial port..