-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilation errors TrainAccess.ino #1
Comments
I have 2 repositories related to this TrainsAccess and TrainsWeatherAccess. The latter is a superset of the first and allows access to weather info as well. The TrainsWeatherAccess is the one I have continued to maintain and it does compile OK under 2.0 which is what I use. The older TrainsAccess does show the compilation errors under 2.0 which I have just replicated. I had not previously compiled this one under 2.0. I will look further into this, but in the meantime you can use the TrainsWeatherAccess even if you don't want the weather functionality. |
A quick look also shows that TrainsWeatherAccess was updated to use my BaseSupport library which includes a common core of support functionality which makes it much easier to maintain. The older TrainsAccess did not use that library which meant it had all the core functionality explicitly included. Rather than try to fix that I may just add a compile option in TrainsWeatherAccess to exclude weather functionality. If so I'll remove the TrainsAccess altogether. I'll update when I have progressed either way. |
I have allowed trainsWeatherAccess to be trains only or weather only if required. The trainAccess repository code is removed and the readme references the trainsWeatherAccess repository instead |
Thankyou for this information. I will have a go at making this work.
There are a couple of things in the README that I am uncertain about.
• Ipload the files in data folder using http:ip/upload
• Further file access can use http:ip/edit
• For software updating export a binary and then access http:/ip/firmware
Thankyou
Mike Parr
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
From: ***@***.***>
Sent: 14 January 2023 12:08
To: ***@***.***>
Cc: ***@***.***>; ***@***.***>
Subject: Re: [roberttidey/trainAccess] Compilation errors TrainAccess.ino (Issue #1)
I have allowed trainsWeatherAccess to be trains only or weather only if required.
The trainAccess repository code is removed and the readme references the trainsWeatherAccess repository instead
—
Reply to this email directly, view it on GitHub<#1 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZE2AIL4ZWZJBT4OCIUEOZTWSKJMDANCNFSM6AAAAAATY7UC2I>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Ipload was a typo; I have corrected this to upload. The basic software has a simple file upload mechanism accessed by browsing to http:ip/upload where ip is the IP address of the device. This allows you to choose a browse to a single file and then upload it. This is used to upload some files in the data folder to allow a more sophisticated file browser / uploader. The basic files needed are edit. htm.gz, graphs.js.gz, and favico.ico. The http:ip/firmware mechanism provides a way to change the firmware code on the device without needing a physical connection. If you have compiled a new version of the code in Arduino then you can choose in the Arduino IDE to export a compiled version of the firmware in a bin file. Accessing http:ip/firmware allows you to select this new bin file. It can then be uploaded and flashed to replace the current firmware. At the end of this it will reboot and run the new firmware. |
Thank you for taking the time to explain this to me.
I am looking forward to implementing this project.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
From: ***@***.***>
Sent: 20 January 2023 11:00
To: ***@***.***>
Cc: ***@***.***>; ***@***.***>
Subject: Re: [roberttidey/trainAccess] Compilation errors TrainAccess.ino (Issue #1)
Ipload was a typo; I have corrected this to upload.
The basic software has a simple file upload mechanism accessed by browsing to http:ip/upload where ip is the IP address of the device. This allows you to choose a browse to a single file and then upload it. This is used to upload some files in the data folder to allow a more sophisticated file browser / uploader. The basic files needed are edit. htm.gz, graphs.js.gz, and favico.ico.
Once these are uploaded you can browse to http:ip/edit which gives you access to a better file upload mechanism which can be used to upload the remaining files in the data folder. It can also be used to do simple text edits on files and to download them as well.
The http:ip/firmware mechanism provides a way to change the firmware code on the device without needing a physical connection. If you have compiled a new version of the code in Arduino then you can choose in the Arduino IDE to export a compiled version of the firmware in a bin file. Accessing http:ip/firmware allows you to select this new bin file. It can then be uploaded and flashed to replace the current firmware. At the end of this it will reboot and run the new firmware.
—
Reply to this email directly, view it on GitHub<#1 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZE2AIMNXC7RNLMSFCH6LFTWTJV4XANCNFSM6AAAAAATY7UC2I>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I am getting compilation errors. which I have attached. I am compiling using Arduino IDE v2.0. and esp8266\3.1.0. The board is Node MCU V1.0 ESP 12E module.
TrainAccess Compilation errors.txt
The text was updated successfully, but these errors were encountered: