@martinhjelmare I think you might be on to something, as I have noticed that other microcontroller modules point the antenna away from the PCB, where as the Sensebender and RF module are overlapping.
I will investigate by adding jumper wires from the SenseBender and the RF module to add some separation.
Thanks...
@tomkxy No signing on my modules...
Distance from a few feet to 20, 50, 100 ft. All yield the same result.
@mfalkvidd The bypass caps are already installed on the PCB.
The SenseBender Micro runs off 2 AA batteries and there is no extra cap on it (that was the design).
@sundberg84 The Sensebender does not have a capacitor, other than bypass.
Not a range issue either, close or further away does not make a difference.
It's pretty consistent with the st=fail debug output.
@mfalkvidd The gateway works fine as other sensors are being received.
Since I am using battery power on the Sensebender Micro, there is no capacitor as that would drain the battery.
What else could be the issue?
I am trying to troubleshoot the debug output below.
Any suggestions?
Sensebender Micro FW 1.3send: 44-44-0-0 s=255,c=3,t=15,pt=2,l=2,sg=0,st=fail:0
send: 44-44-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,st=fail:1.5.4
send: 44-44-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=fail:0
sensor started, id=44, parent=0, distance=1
So on the bus it is disabled with D8 high?
I need to disable the SPI Flash chip on the Sensebender Micro in order to troubleshoot an issue with the NRF24 module.
Is there a way to disable the flash chip in code to prevent it from communication on the SPI bus?
Thanks,
Tony
@Jokgi Hi Jokgi, do you think you can have a rep from Nordic send out some sample authentic modules to the MySensors community to those that can help solve the deficiency between the fake and authentic modules? I think that might help.
If there are community members that might want to work with the authentic module maybe reply here if interested.
@Jokgi So then why would these companies not use the authentic Nordic chips if there are distributors in China? Seems like a lot of trouble to go and produce fake chips when the real chips are readily available there already?
@alexsh1 I think that the folks that are getting unknown Nordic fakes are actually shortchanging themselves. First there is no way the Chinese can make an exact duplicate of the Nordic chip, all they can do is make a cheap facsimile (which is what they do best anyway). If you're like me an seriously want to utilize the work that the guys did on the SensBender module and get the longest battery life and best RF performance then you'd want to use the genuine Nordic chip.
Second, Nordic does not manufacture those chips in China anyway (according to Nordic). So if a reseller says they get them from a Chinese manufacturer then they are fake, no doubt.
I also received an email from Seeed Studio indicating they get their chips from a Chinese manufacturer...So probably fake as well.
@alexsh1 I believe the sketch works for the Chinese chips, as you say, but not for the genuine Nordic chips.
That said, I contacted ITead yesterday and asked if the Nordic Module they sell uses the genuine Nordic chip or another chip from a 3rd party. The response I got back was that the supplier they get the Nordic chips says they are authentic. Although, they did not indicate which supplier. So I replied back to ask which supplier they use and I am still waiting for a response from ITead on this question.
Let's say that ITead is using an authentic chip. I run the sketch with their module and it works. I replace the module with the Nordic sample I have and the sketch does not work. So now what?
Is ITead actually using the authentic chip or not?
@tbowmo Understand, any suggestions on another person to help. I think that in all honesty we should make this work and resolve the issue.
@tbowmo Hi Thomas, I am still having an issue with the authentic Nordic module and the mysensors software.
I was wondering if you has access to one of these modules and could test the software?
Or, if there is someone else that could help out?
If needed, I could ship a Nordic module out for testing as I have several that I got from a Nordic rep in the U.S.
Thanks,
Tony
I kind of got it working by manipulating the nRF24L01.h file.
By changing these two params:
#define EN_ACK_PAY 1
#define EN_DYN_ACK 0
to:
#define EN_ACK_PAY 0
#define EN_DYN_ACK 1
The Nordic module registered on the gateway and reported battery voltage, but failed on temperature.
Anyway, I am not an expert on this software, so maybe someone might be able to help, especially the folks which wrote it.
Thanks,
Tony
@Yveaux Yeah, no other modules available, except from China.
However, that might change. I think there may be a manufacturer in the U.S. that is going to make official modules at a reasonable price soon and pretty much duplicate the Nordic module.
I think that Nordic may have shot themselves in the foot by not making the module more available and at a much lower price. This opened the door for the fake chip market.
@hek said:
The sketch works. We can rule out that. I suspect the power requirement might differ from the clone. You could play around width extra capacitors on the module.
Well, not sure how you can say the sketch works when I have it here and it does not work with the Nordic module.
Have you tested the SensBender sketch with the genuine Nordic module?
Since these are battery powered adding a capacitor will not make a difference and it will further drain the battery over time.
Again, there is something else going on...
The genuine Nordic chips can be purchased for less than $3 in the U.S.
That is just the chip and not the module.
The actual parts which make up the module cost about $3-4.
If you are concerned about battery operation you'd want the genuine chips as they have a lower sleep current which would extend battery life, which is critical in my application. So cost of batteries is a factor as well.
@Yveaux I'm not a big fan of companies stealing the design of another company which has put time and resources into the development of a chip.
I only want to use genuine Nordic products in my sensor network. That said, I think that some work needs to be done on why the SenseBender appears to have an issue operating with the Nordic module. I hope that the responsible folks will step up and make this work.
Let me know if I can do any other testing as I'd like to get this issue resolved ASAP.
Thanks,
Tony
@hek I did the test here is the result.
While the Nordic radio is connected to the gateway it receives the data from all the Chinese radios, no problem.
When I connect the Nordic module to one of the SenseBender modules I do not receive any data according to the gateway debug whether it has the Nordic or Chinese module.
So it appears that the Nordic and the Chinese can communicate, but the Nordic appears not to work when only connected to the Sensebender module. So I suspect something going on there?
I can try a Nordic Module on my Gateway. But I am actually using one of the high power radios on the gateway, which I may assume it has the Chinese chip instead of the Nordic one.
If it does work, then I will need a high power radio with an authentic Nordic chip, it that is even available. If so let me know..
I will get back with the test shortly...
@Yveaux Are you using the code for the SenseBender Micro?
why is the debug above indicating failure in 5 of the debug outputs for the genuine Nordic modules and no failures for the Chinese modules?
@tbowmo Also, here is some info that I got from Nordic Tech Support
"The re-marked nRF24L01P (+) clones are not 100% register compatible. The issue with the counterfeit devices is that when they enabled “Dynamic Payload Length” (EN_DPL) in the “FEATURE” register, one bit get’s activated in the on-air payload (the NO_ACK bit) This bit should be active high (according to the Nordic datasheet), but it’s actually implemented the other way around. When EN_DPL is activated, the NO_ACK bit get reversed in the real nRF-devices. They did such a good job of cloning they cloned the datasheet error into the device!!!
If someone is using the fake parts on both ends it will work to some degree. In a mixed environment where you may have both real L01P and the fake ones you will have issues. But don’t look to be fully “compatible” with the real nRF24L01P firmware wise. And on a side note, As the nRF24LE1 and nRF24LU1P both use the nRF24L01P radio this makes the counterfeit parts incompatible with those as well.
@tbowmo OK, I got ver 1.5.4 loaded and it's still failing with the authentic Nordic module.
Here is the output from the serial debug.
Sensebender Micro FW 1.3send: 4-4-0-0 s=255,c=3,t=15,pt=2,l=2,sg=0,st=fail:0
send: 4-4-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,st=fail:1.5.4
send: 4-4-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=fail:0
sensor started, id=4, parent=0, distance=1
@tbowmo Where is the link to download the updated sketch??
I will check tomorrow morning. What is the latest version?
And do any of the libraries need updating?
The debug looks normal as far as I can tell.
But appears nothing is getting transmitted??
any suggestions?
-Tony
I can use the Nordic as a Gateway and it works fine with the Chinese that are running the code on the SenseBender module....That's not the issue.
The issue is, in my opinion, that there is a minor bug in the SenseBender code as that is where the Nordic modules are failing. Basically the code works with the Chinese version, but does not with the authentic Nordic.
-Tony
I've been using the nRF24L01+ modules I purchased from China (which are most likely clones) along with the Sense Bender Micro as Temperature Sensor Nodes for a few months and they seem to be working ok.
I recently received some "official samples" of the nRF24L01+ modules directly from a Nordic Rep here in the U.S. When I replace the Chinese modules with the Nordic modules they do not work - No response from the Node while monitoring the gateway. I am running the exact same software for the SenseBender Micro.
I spoke to the Nordic rep and he indicated that there are some subtle differences between the authentic and clone versions and suspects that it is a software issue on the Sensbender PCB.
For testing, I hooked up the Nordic module to my gateway Arduino and it worked fine. So I would assume the same conclusion that there is a bug in the SenseBender code.
Yeah, I dug through the .h files and found the right spellings and got it to finally work...
Thanks...
I tried the short program above, but at compile time It got this error:
'hwReadConfig' was not declared in this scope
Any suggestions?
Is there a way to modify the Node ID once a Node ID has been issues to a sensor node that was originally configured in AUTO Node ID mode?
Thanks,
Tony
So that works setting a new Node ID. However, how can I change the Node ID to another value?
Thanks,
Tony
So if I understand then the response would be 255,255,3,0,4,NODE_ID
Is this correct?
Thanks,
Tony
I am trying to figure out how to assign a Node ID to a new device on my network.
I am using a Sensbender Micro set to AUTO mode for receiving a static Node ID.
When I monitor the serial data from my gateway, it shows the data as 255,255,3,0,3.
What data do I send to the node in order to give it an static node ID from the gateway, or controller. Note I am not using any specific controller, just a simple Node Red application to display the mode data...
Thanks,
Tony
Is there a BOM for the Sensebender micro?
I didn't see one on the github page.
Thanks
What is the current consumption of the Sensebender during sleep and active modes?
Thanks,
Tony
I just received my Sensebender today and I am having an issue getting it work correctly.
When I tie A0 to GND for the self test this is what I get from the Serial Monitor:
Sensebender Micro FW 1.3 - TestMode
Testing peripherals!
-> SI7021 : ok!
-> Flash : failed!
-> SHA204 : Ok (serial : 0123753C526A1A06EE)
Test finished
----> Selftest failed!
Also, in normal mode no data gets transmitted to my Gateway. The only change I made to the sketch was to specify a unique Node ID (4) in this case.
Any suggestions?
Thanks,
Tony
In this case I am not using a Controller, just a Gateway for now. It appears the GW is assigning a Node ID.
If a sensor node is set up to AUTO configure it's Node ID from the Gateway, how can I determine it's Node ID in order to identify it physically?
My scenario is I have 5 rooms each with a Temperature Sensor Node.. I need to know which node is in which room.
Thanks,
Tony
Thanks, I thin that fixed the issue. I set the Repeater node ID to 100. The Arduino sketch has the ID set to AUTO which I think initially set the Repeater Node ID to 255.
Tony
I have two temperature sensors each with a specific node id (1 and 2).
They connect fine to the gateway for testing close by.
I have another node set in repeater mode with the sample arduino code, I'm using the latest 1.5 code base.
I place the repeater node in another location away from the gateway along with both temperature sensor nodes. I can see the repeater in the gateway output, but do not see the temp nodes being sent from the repeater. The repeater id is 255. I was under the impression that the repeater node would automatically send the data from the sensor nodes.
Why is this not working as I though it would????
Thanks, Tony