I experienced some problems whith the Distance US3 Module;
I’m using a Spider mainboard, with Distance module connected on Socket 11 (through an Extender)
and a second one connected on socket 14.
No one is working…
It takes nearly 30 sec to get a measure through the “GetDistanceInCentimeters()” method, and I always get 7 as return value, and the SENSOR_ERROR property is -1.
Same result on both sensors.
Is there a driver problem, or something I miss to make it working ?
Then, add devices individually and see what one introduces the issue. You should then remove the ones you add and just add that last device to see if it’s the combination of devices or really just that last one…
My question is not really on the current module, the fact is that I asking myself if this problem could affect the Distance US3 process since they seems to be in conflict
If you think it’s blocking, then it would block anything on that thread, not directly related to the US3. Since you feel that this could be blocking your US3, then that tells me they are on the same thread.
Can you put the Read_DC_Current into its own thread?
Any feedback would be welcome… I’m starting to be troubled of having no response, not even an update status…
I believe in this technology, but I was hoping more support in case of bugs (which seems to be the case here), especially for giving us trust in building .NET Gadgeteer projects.
I’m actually building a really nice project which is actually blocked because of the component. I spent lots of money to buy your components, and I already cancelled a commercial project because of lack of support, which make me loose money.
I hope I won’t have to cancel this one too, because it would clearly take me off .NET gadgeteer.
It is on the list to look into but there are other higher priority items to look into.
By the way, the distance module driver is open source if you wanted to dig into it.
I am afraid that due to the real time requirements of the distance measurements and NETMF being not real time, the drivers will not properly if the system is busy, like when you have multiple modules. But we will have to confirm this.
Gadgeteer has much to offer, so I hope this small obstacle will not cover the great advantages found in gadgeteer.