No nodes discovered

[baldvinhansson]

I had your excellent library working just fine a while back. Then, for whatever reason, it stopped working and I'm totally at loss as to what might be my issue. Been googling for days now but unable to get this going.

I've two modules. DigiMesh 9000 PRO firmware. Series 2. Both are API with escapes mode (2). Using XCTU I can discover and send packets back and forth, no problem. But when I connect using .net code and hope for discovery event, nothing happens. And packets broadcast to 0xFFFF 64bit address (the .net code connects to my coordinator) are not received by the end node.

Using nuget packages BinarySerializer 8.1.3 and XBee Core 1.6.3 XBee 5.3.3

I can provide any details needed to assist in getting me back on track. But not sure what's relevant, so I'll wait and see if anybody might be willing to help me out before providing more details.

[jefffhaynes]

Sorry, I’ll take a look as soon as possible

…

________________________________ From: baldvinhansson <[email protected]> Sent: Friday, September 14, 2018 9:03 AM To: jefffhaynes/XBee Cc: Subscribed Subject: [jefffhaynes/XBee] No nodes discovered (#54) I had your excellent library working just fine a while back. Then, for whatever reason, it stopped working and I'm totally at loss as to what might be my issue. Been googling for days now but unable to get this going. I've two modules. DigiMesh 9000 PRO firmware. Series 2. Both are API with escapes mode (2). Using XCTU I can discover and send packets back and forth, no problem. But when I connect using .net code and hope for discovery event, nothing happens. And packets broadcast to 0xFFFF 64bit address (the .net code connects to my coordinator) are not received by the end node. Using nuget packages BinarySerializer 8.1.3 and XBee Core 1.6.3 XBee 5.3.3 I can provide any details needed to assist in getting me back on track. But not sure what's relevant, so I'll wait and see if anybody might be willing to help me out before providing more details. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#54>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AJSKR-w0ry6sxNCf3n1O8DRAyebFdhdiks5ua6kQgaJpZM4WpO6D>.

[baldvinhansson]

Revisiting this issue now and was trying to see if it was just some silly user error that I made. Still stuck and not able to get this to work. Is it possible there's something wrong with the library in its current state? I'd really appreciate if you could see if there's perhaps a trivial issue that could be corrected? Unfortunately I'm not well versed enough to check this effectively my self though I'd love to help in any way I can.