Re: Re: Digi's treatment of Rabbit products
| Newsgroups | gmane.comp.hardware.rabbit-semiconductor |
|---|---|
| Message-ID | <[email protected]> |
Hi Tom, The Github development looks very interesting as I have run into a number of problems with the libraries which I have had to work around/fix. Some of these I've fed back to Digi and they have made it into the libraries and examples (the uCos stack issue and improvements to the FTP client libraries) but others were not due to time constraints. Most of the issues have been found whilst working on my own product development which is a BACnet data logger based on a custom Rabbit 4000 board and Digi tech support, understandably, prefer to see an example of the issue running on one of the standard products so that they can reproduce it. This means I have to take time to put together a sample based on a BL4S100 or other board from my collection when I want to submit a fix or a problem. I'll have a look at the Github files to see what's happening there. Is there scope for feeding fixes/improvements back through Github? I've a problem I'm working on at the moment in relation switching between different networks and DHCP leases which is due to issues in the TCP/IP stack that would definitely be useful when I finish working out what's up. Regards, Peter