What a great way to start a day - a new IoTT video! The YellowHat is certainly developing into a very interesting module. You have included some remarkable capability in it which make the possibilities almost limitless. Looking forward to when they are available and I can get one to try out.
I've purchased all of Hans items so far .. have yet to use them...unboxed everything and all items are there....will be ordering future items when available..so far things look good Hans!
Hans - I have been testing my Yellow Hats - just tried to write a new LED config to the IoTT Stick in the Yellow Hat - the LED screen now doesn't have the colours or LED table contents just the headers. No real data lost but is this something that can be recovered.
This looks like something went wrong when doing a Save and Restart and the datafile is corrupted. The only way to fix it is loading a backup, in case you saved your settings to a computer, which is a good idea to do. I saw this error in earlier versions of the Stick software in cases of a weak Wifi connection. However, with versions later then about 1.5.4 that should be fixed. Are you connecting the Stick over a Wifi AP or are you using the built-in AP? And what browser are you using? The most stable setup is the Stick connected to your Wifi, not too far away from the AP, and a chromium based browser (Google Chrome or Microsoft Edge). Furthermore it is a good idea to save the Stick to a local file. You can save to individual files from each configuration page, or save the entire Stick configuration when you do a Save To File from the node configuration page. Some example backup files that might get you restarted can be found here for download: github.com/tanner87661/IoTTStick/tree/master/ConfigData/YellowHat%20CTC%20panel
Largely yes, but there is more and some got renamed. Loconet is now Loconet Interface, but what you want to use is the Wifi connection, so you select Loconet lbServer Client. The Button handler is now two different tools. The first is the Hardware Button Setup tab, which lets you specify what type of message you are sending. Select e.g. Detector for sending block detector messages. Then there is now the Event Handler, which can be activated in the Node Configuration. It is a very flexible tool to react on input messages and then trigger action. Watch the videos in the YellowHat playlist to see how to use the event handler to create a signaling system.
Yes. Just set the IP address and port number in the client setup to the one of the server. And for an example how to integrate with EX-RAIL, watch videos #118 and #119
@@IoTT How do I get back to the initial wifi setup? You said give it a IP address so I selected Static Ip using the given settings. Now I cannot access the browser software. Thanks
You can build your own. Watch Video #50. That's sort of the kit version, but as always with kits, requires some building skills and debugging capabilities.
What a great way to start a day - a new IoTT video! The YellowHat is certainly developing into a very interesting module. You have included some remarkable capability in it which make the possibilities almost limitless. Looking forward to when they are available and I can get one to try out.
I've purchased all of Hans items so far .. have yet to use them...unboxed everything and all items are there....will be ordering future items when available..so far things look good Hans!
Hans - I have been testing my Yellow Hats - just tried to write a new LED config to the IoTT Stick in the Yellow Hat - the LED screen now doesn't have the colours or LED table contents just the headers. No real data lost but is this something that can be recovered.
This looks like something went wrong when doing a Save and Restart and the datafile is corrupted. The only way to fix it is loading a backup, in case you saved your settings to a computer, which is a good idea to do.
I saw this error in earlier versions of the Stick software in cases of a weak Wifi connection. However, with versions later then about 1.5.4 that should be fixed. Are you connecting the Stick over a Wifi AP or are you using the built-in AP? And what browser are you using? The most stable setup is the Stick connected to your Wifi, not too far away from the AP, and a chromium based browser (Google Chrome or Microsoft Edge).
Furthermore it is a good idea to save the Stick to a local file. You can save to individual files from each configuration page, or save the entire Stick configuration when you do a Save To File from the node configuration page.
Some example backup files that might get you restarted can be found here for download: github.com/tanner87661/IoTTStick/tree/master/ConfigData/YellowHat%20CTC%20panel
Hello, Do these setting still apply? I do not have a Loconet option for command source. I also can't find the button handler tab. Thanks
Largely yes, but there is more and some got renamed. Loconet is now Loconet Interface, but what you want to use is the Wifi connection, so you select Loconet lbServer Client. The Button handler is now two different tools. The first is the Hardware Button Setup tab, which lets you specify what type of message you are sending. Select e.g. Detector for sending block detector messages. Then there is now the Event Handler, which can be activated in the Node Configuration. It is a very flexible tool to react on input messages and then trigger action. Watch the videos in the YellowHat playlist to see how to use the event handler to create a signaling system.
@@IoTT And this will work with my other stick which is on the CS using the Aux shield, it's still setup for Loopback, Red hat and IB Server? Thanks 👍🏼
Yes. Just set the IP address and port number in the client setup to the one of the server.
And for an example how to integrate with EX-RAIL, watch videos #118 and #119
@@IoTT I'm going to watch the videos for Ex-Rail first. Thanks 👍🏼
@@IoTT How do I get back to the initial wifi setup? You said give it a IP address so I selected Static Ip using the given settings. Now I cannot access the browser software. Thanks
could you make as kit form
You can build your own. Watch Video #50. That's sort of the kit version, but as always with kits, requires some building skills and debugging capabilities.