I have used Tile Builder before on my other C7 and C8
I have a third C8, added Tile Builder, and I can see my new tile when I look at the Tile device, its show my tile I built, it has the devices, data etc, all looks correct.
So I know the device is linked to the storage
I also, added the tile storage builder device in my dashboard app
On my dashboard I can select the Tile device, Attribute, tile1 and save it
When I view the new tile on my dashboard, its blank,
While having a blank tile, after about 15 second, I get this 192.168.40.174 took too long to respond
Is this more a case of understanding how to use Discourse (the system the Community uses)....? Took me a bit to get used to it a few years ago now... You can click the "Reply" button at the botton of the TB topic I linked earlier, much the same as you clicked Reply here on this topic.
As Simon says using the main thread is the best approach to get the developers attention but we will save that for the future.
If a table is over 1,024 bytes it will either go to a file or an Endpoint depending on which module we are talking about and the users choice. In most cases it is a file.
If you go to the storage device and scroll down to the state variables you will find entries that look like this:
Interpreted it means:
192.168.0.200 - The IP address of the hub which runs the following Tile Builder instance.
local - It's on the hub filesystem
TBSD1 - File generated by Tile Builder Instance linked to Storage Device 1.
_Tile_X - where X is the number of the tile.
.html - the file extension.
You should be able to open the file from your browser on the PC. If you can't, go to your Settings\File Manager and verify if it is there. It should be regenerated each time there is a change in content.
Usually it is a pretty error free process. You mentioned 3 hubs and I wonder if you are using these in a mesh. If so, it's possible that the Dashboard on Hub 1 is referencing a device on Hub 2 because you are using a meshed device. I've not tested it using Hub mesh so not sure what to expect.
No judgement, at least from me.... just a convention that I (at least) can understand as a way to keep the comm's with the developer focused in a single topic and easier to follow. The way the tracking works in Discourse makes this the easier option rather than relying on tags, etc. Also easier for users of the driver/app to have a single spot to go for discussion about the thing they are interested in. Just my 2c.... and a convention adopted commonly here and I would suggest on other Discourse forums.
That's not to say there is anything inherently wrong with creating a new topic.... Just more convenient to add to the existing conversation.
In general yes, mainly because it’s usually the simplest way for a developer and/or users of a custom app like this one to see that a user has a question.
But since Gary has replied here, it’s a moot point for now .
Is your PC\Device on this same subnet? Can you open the file in the browser?
The XXX took too long to respond is a rather generic browser response. It could mean the requested resource is unavailable (no route) or slow to respond because of load issues.
Once a tile < 1,024 all the data is stored in the attribute and the dashboard has easy access. That said, above 1,024 it should still work it just has to load the file in an iFrame but of course needs network connectivity for this to happen.
.
