-
Notifications
You must be signed in to change notification settings - Fork 13
PI.HTTP
Matthew Splett edited this page Mar 17, 2019
·
2 revisions
TIPI supports accessing files by URL for read.
Files are specified with the prefix "PI.HTTP" or "PI.http", "PI.HTTPS" or "PI.https"
For example:
PI.http://www.cwfk.net/4afiles/AMBULANCE
Loading program image files is only supported if the hosted file is a TIFILES format FIAD file.
Other types of files may be loaded and TIPI will treat them as raw binary files, breaking the data up into records matching the open-mode record length.
"URI1.", "URI2.", and "URI3." aliases can be mapped as shortcuts to long URLs making this more compatible with legacy software written for a 32 column screen.
If you have "URI3." mapped as such:
URI3=http://www.cwfk.net/4afiles
Then you can load AMBULANCE in EA5 by entering:
URI3.AMBULANCE
Usage:
- Why-TIPI
- tipi-installation
- tipipeb-installation
- safe-shutdown
- TIPI-to-PI-Wiring
- Which-PI
- Disk-Images
- TIFILES
- Raspberry-PI-configuration
- Backup-Restore
- FAQ
- TIPICFG
- BASIC-CALLs
- Auto-mapping
- File-name-rules
- Downloads
- emulation-installation
- Cloud Storage
- TIPI Sharing
- Updates
- Windows 11
Details:
- Devices
- Level2-IO
- Native-Files
- PI.CLOCK
- PI.CONFIG
- PI.HTTP
- PI.PIO
- PI.REBOOT
- PI.SHUTDOWN
- PI.STATUS
- PI.TCP
- PI.UDP
- PI.UPGRADE
- PI.VARS
- PI.LOG
- RawExtensions
- Extension-Mouse
- Extension-NetVar
- Extension-TCP
- Extension-UDP
- Extension-TLS
- Extension-LOG
- PABMessaging
- Known-incompatible-software
- crubase
- Design
- Services
- TIPI-Protocol
- Troubleshooting
- Sideport-BOM
- TipiPEB-BOM
- CPLD-Programming-With-PI