Hi, There was an issue with max string length for the uart being limited to 256, I am wondering if the circular buffer has the same limitation as I am getting the string as expected now but the code still does not work. Before I carry on trying to find out where the issue is I would like to know if ...

Hi Steve,
It did say it needed a reboot to complete but this one took two. Fine now.

Bob

Hi Ben,
That works now and I get the string I was expecting, the code is still not finding the string I am searching for (which I can see in the Rx_String) so I am wondering if the 8 bit circular buffer has a 256 byte limit as well?

Bob

I am not sure this is normal but I had a bit of a panic when I updated to the latest install. I downloaded and as mentioned it took a long time but there is a kettle for such situations. It said I had to close down FC as it was stopping the install and I clicked yes even though I thought it was not ...

Thanks for confirming I was not going mad.
Is that something us mere mortals can see or do you need a professional licence to see it.

Bob

Is the length a byte? This would limit it to 0..255.

Hi,
FC allows me to create a string with a length of 350, the program shows the captured length of the incoming string is 333 so it seems that there is an issue with SendString with strings longer than 255 which is out of my control.

Bob

Hi, I hope this is a simple one as an example might be difficult to provide, I have attached the FC file but it would also require the DB and a couple of PHP files to actually work. I have been testing the example with Chipfryer for retrieving values from a DB, it does not work for me and in the pro...

So following on from Chipfryers excellent example I needed to get the information out of the DB and onto a web page. I know it is not directly related to FC but I think it is relevant and hopefully it will save people hours and hours of trawling through books and the internet for what always seemed ...

Just for completeness I have recreated an issue where wireshark showed the packet showing the string which was as sent but the database did not update at all. Here is the wireshark image showing the sent string. wireshark error.jpg If you look after the packet you will notice (I did not originally) ...

If it does not work straight away (which is why I thought of doing this update) I found Wireshark a good tool. There is a whole load of data flying around your network so I set up a filter for just what I needed. I was also only sending every minute so without it I was inundated with irrelevant stuf...