ATtiny supported?
-
I doubt it but this might help: :)
http://hackaday.com/2014/02/16/nrf24l01-using-3-attiny85-pins/ -
I actually saw some Arduino projects on ATtiny, however I didn't thought of the IO problem.
Guess I will have to kill that idea.Thanks both of you for the fast response :)
-
I would like to use small 8pin AVRs for nodes with only one sensor (like temp).
Is ATtinys supported?I'm sorry if this is a dumb question, I'm new to the Arduino and AVR world.
You can find a lot of guides on the web about using the Arduino environment for the ATTiny series.
The TMRH2o nRF library is supposed to support ATTiny, but may not have been tested.
You already know that pins are going to be very tight, but if you have a one-pin sensor which doesn't need much code...
It might be possible to fit the sensor code (for some sensors) and the MySensors libraries, but if so it would be tight.
One tip: avoid any floating point code (some node sketches use it and some do not).
I'd actually love to see somebody make a MySensors node on an ATTiny.
-
You can find a lot of guides on the web about using the Arduino environment for the ATTiny series.
The TMRH2o nRF library is supposed to support ATTiny, but may not have been tested.
You already know that pins are going to be very tight, but if you have a one-pin sensor which doesn't need much code...
It might be possible to fit the sensor code (for some sensors) and the MySensors libraries, but if so it would be tight.
One tip: avoid any floating point code (some node sketches use it and some do not).
I'd actually love to see somebody make a MySensors node on an ATTiny.
I have looked into this too but decided against it.
Mainly for 2 reasons:- A board stacked onto your own pcb would make that you can keep the width and length of your pcb small. Imho adding your own microcontroller etc. to your own pcb would make it larger. Unless I am mistaken.
- When going that route why not use the ATmega328? Price can't be the reason not to use it or is it?
-
I found such board with ATtiny84 and NRF24L01.
http://nettigo.pl/products/bezprzewodowy-sensor-tinybrd
I am trying to find out from the producers if mysensors library will also work on it.
What do you think? Hardware site is already done. Will it be possible to run sketches with mysensors on it?
Regards -
I am still interested in the answer to the question 'why would you want to use an ATtiny?'....
Fulltime Servoy Developer
Parttime Moderator MySensors boardI use Domoticz as controller for Z-Wave and MySensors (previously Indigo and OpenHAB).
I have a FABtotum to print cases. -
I am still interested in the answer to the question 'why would you want to use an ATtiny?'....
-
I am still interested in the answer to the question 'why would you want to use an ATtiny?'....
@marceltrapman
Because in case of door/window sensor it is better looking, when you have sth small sticked to the frame :) -
Actually i tried to port the mysensors lib to the attiny, a few months ago..
https://github.com/Oitzu/Arduino
I had to remove much of the auto-id, repeater and gw stuff to fit it into the memory of the attiny.
But it the end it didn't run stable enough. This can maybe be fixed but i didn't investigated further. -
I am still interested in the answer to the question 'why would you want to use an ATtiny?'....
@marceltrapman said:
I am still interested in the answer to the question 'why would you want to use an ATtiny?'....
For example, an ATTiny85 is
- cheaper (just $1),
- it's smaller,
- it uses less power (about 1/4 as much),
- it's programmable using the arduino IDE,
- it also sports a differential ADC (for higher accuracy) that the atmeg328p simply doesn't have,
- doesn't require external support components
- wouldn't require a breakout board
For the last point, consider this type of possibility:
http://jeelabs.org/book/1501a/Is that enough of an answer? If necessary software can be crammed in there, it's a clear win.
Some of the attiny's support SPI natively. For those that don't (such as the ATTiny85), I've read there's a softSPI library for it
-
@marceltrapman said:
I am still interested in the answer to the question 'why would you want to use an ATtiny?'....
For example, an ATTiny85 is
- cheaper (just $1),
- it's smaller,
- it uses less power (about 1/4 as much),
- it's programmable using the arduino IDE,
- it also sports a differential ADC (for higher accuracy) that the atmeg328p simply doesn't have,
- doesn't require external support components
- wouldn't require a breakout board
For the last point, consider this type of possibility:
http://jeelabs.org/book/1501a/Is that enough of an answer? If necessary software can be crammed in there, it's a clear win.
Some of the attiny's support SPI natively. For those that don't (such as the ATTiny85), I've read there's a softSPI library for it
@NeverDie I would like to add my support for your worthy quest. Some time ago I was looking for a way to make MySensors RFID like tags for presence detection but the result was just too big as well as too energy consuming.
-
@NeverDie @Moshe-Livne the underlying rf24 library supports the use of the attiny85.
As mentioned above, the modified (shrinked) mysensors library runs on the attiny85 but is a little bit unstable.
There could be multiple reasons for this... i stopped the development of the attiny85 port because of low interest and time for other projects.@Sweebee : Do you still have the sketches and layouts for the attiny85 mysensors node?
-
@NeverDie @Moshe-Livne the underlying rf24 library supports the use of the attiny85.
As mentioned above, the modified (shrinked) mysensors library runs on the attiny85 but is a little bit unstable.
There could be multiple reasons for this... i stopped the development of the attiny85 port because of low interest and time for other projects.@Sweebee : Do you still have the sketches and layouts for the attiny85 mysensors node?
@Oitzu said:
@NeverDie @Moshe-Livne the underlying rf24 library supports the use of the attiny85.
As mentioned above, the modified (shrinked) mysensors library runs on the attiny85 but is a little bit unstable.
There could be multiple reasons for this... i stopped the development of the attiny85 port because of low interest and time for other projects.Which fork or version of RF24 did you try? Perhaps we can pick up where you left off.. I've read that TMRh2O is both supported and has fixes to bugs in prior versions. Is there presently anything better? However, if it turns out that's unstable too, then maybe just poking registers on the NRF24L01+ is enough for something barebones but stable. Anybody know? A softSPI library would still be needed though. Any suggestions on which of those would be a good choice for the Attiny85?
I recently received a tiny AVR programmer:
http://sfe.io/p11801
purely for convenience, but I haven't tried it out yet. There's also a youtube video (https://www.youtube.com/watch?v=30rPt802n1k) which shows another way how to do it using a spare arduino as the programmer. -
@NeverDie @Moshe-Livne the underlying rf24 library supports the use of the attiny85.
As mentioned above, the modified (shrinked) mysensors library runs on the attiny85 but is a little bit unstable.
There could be multiple reasons for this... i stopped the development of the attiny85 port because of low interest and time for other projects.@Sweebee : Do you still have the sketches and layouts for the attiny85 mysensors node?
-
@Sweebee said:
@Oitzu https://github.com/sweebee/Arduino-home-automation/tree/master/2.4Ghz (MySensors)/Attiny/button-switch
I gave it a quick read, and noticed that it appears to be using maniacbug's RF24 library. Six months ago Maniacbug posted the following here:
My fork has been abandoned.TMRH20 now has the premier fork - by far. You'll find considerably improved reliability and performance over both my fork and the original code base. Plus he has made an effort to keep RF24Network working well. Don't walk, but run from the orginal code base and immediately starting using TMR's fork.
Unfortunately, he posted this seemingly vital news in a comment buried way down the page instead of at the top, which is where it belongs. I wouldn't be surprised if most people are unaware of it.
Would it be much effort to migrate to the new library? It sounds like that alone might solve the stability problem.
-
@NeverDie i used a spare arduino nano as programmer for the attiny85. This works great.
As you maybe have seen i'm using a fork of the mysensors library of the end of may 2015.
I don't really can identify, at this moment, with which version of rf24 the mysensors library comes by...
but because the last update of this lib seems to be 9 months ago i should give it a try to update it.My suggested way to go would be: To merge the changes in the mysensors library from may 2015 to now into the fork (to be up-to-date with mysensors again) and then try to replace the rf24 library with a newer version.
Did we have anyone here able to test the libs? At the moment i have no spare attiny & nrf laying arround, i'm waiting for a new delivery.
About SPI: The rf24 lib includes a softSPI lib for communication.The lib even supports different ways to connect the nrf24 with the attiny.
See: http://tmrh20.github.io/RF24/rf24ping85_8ino-example.htmlI never tried the 3 connect. I simply connected CE with VCC to get one pin for testing free.
-
@NeverDie i used a spare arduino nano as programmer for the attiny85. This works great.
As you maybe have seen i'm using a fork of the mysensors library of the end of may 2015.
I don't really can identify, at this moment, with which version of rf24 the mysensors library comes by...
but because the last update of this lib seems to be 9 months ago i should give it a try to update it.My suggested way to go would be: To merge the changes in the mysensors library from may 2015 to now into the fork (to be up-to-date with mysensors again) and then try to replace the rf24 library with a newer version.
Did we have anyone here able to test the libs? At the moment i have no spare attiny & nrf laying arround, i'm waiting for a new delivery.
About SPI: The rf24 lib includes a softSPI lib for communication.The lib even supports different ways to connect the nrf24 with the attiny.
See: http://tmrh20.github.io/RF24/rf24ping85_8ino-example.htmlI never tried the 3 connect. I simply connected CE with VCC to get one pin for testing free.
@Oitzu said:
About SPI: The rf24 lib includes a softSPI lib for communication.The lib even supports different ways to connect the nrf24 with the attiny.
See: http://tmrh20.github.io/RF24/rf24ping85_8ino-example.htmlThis is good news. It means the radio portion can be tested independently of the mysensors portion. If it turns out the radio portion tests out fine running standalone, then that would be good to know, as it might help isolate the source of instability to somewhere in the mysensors code. Or, visa versa.
Using genuine Nordic Semiconductor parts for at least the initial radio testing would be ideal. I'm suggesting that so as to rule out possible clone-related problems. In about a week I should to receive a couple allegedly genuine Nordic Semiconductor NRF24L01+'s from an Itead distributor. Once I receive them, I can try running some standalone ATTiny85 wireless tests, starting with running the example code you referenced above from the TMRh2O library.
As I'm a brand new arrival, I don't yet know anything about the mysensors code, and I have no experience by which to judge what's normal or atypical mysensors program behavior. So, in the near-term, I expect others would be in a better position to help with that part of the coding/testing/debugging/troubleshooting..
-
@NeverDie i used a spare arduino nano as programmer for the attiny85. This works great.
As you maybe have seen i'm using a fork of the mysensors library of the end of may 2015.
I don't really can identify, at this moment, with which version of rf24 the mysensors library comes by...
but because the last update of this lib seems to be 9 months ago i should give it a try to update it.My suggested way to go would be: To merge the changes in the mysensors library from may 2015 to now into the fork (to be up-to-date with mysensors again) and then try to replace the rf24 library with a newer version.
Did we have anyone here able to test the libs? At the moment i have no spare attiny & nrf laying arround, i'm waiting for a new delivery.
About SPI: The rf24 lib includes a softSPI lib for communication.The lib even supports different ways to connect the nrf24 with the attiny.
See: http://tmrh20.github.io/RF24/rf24ping85_8ino-example.htmlI never tried the 3 connect. I simply connected CE with VCC to get one pin for testing free.
I'm getting a little confused. Not enough sleep I guess. :sleepy: Given what hek stated this morning in this link here, does that mean the current version of mysensors already supports the attiny85? Or does it need to be slimmed down to fit, which is what I gather (perhaps incorrectly) Oitzu and others were/are planning to do? Or is the required work something else entirely? If the TMRh20 library is already integrated, as hek stated in that link, and it contains the SoftSPI needed for the attiny85 to interface with an NRF24L01+, what other work, if any, remains to be done? Again, sorry for the Noob question.
By the way,I made a typo in some of my posts. It should be TMRh20 (twenty), not TMRh2O (water). That's why my search of the forum hadn't turned up any reference to it, which is why I thought it might be new news rather than old news, as it apparently is. Sorry for that.
-
@NeverDie to clear things up to you: Yes the underlying rf24 is fully compatible with the attiny85.
The full-blown mySensors library is to big to fit on the attiny and has some compatibly issues.
In April 2015 i forked the mysensors library and cut it down to fit on the attiny.
It worked, but not reliable. The reason why it didn't worked correctly is at this moment not known, and i didn't investigated further.What need to be done: We need to merge the current mysensors library into the attiny fork, then we should merge the current rf24 lib into the attiny fork, after that... testing.
