TIPI Usage and Support

[+jedimatt42]

1 hour ago, Vorticon said:

Awesome work Matt! For pcode compatibility, the TIPI should be ar 1000 and the disk controller at 1100, correct?

That is what works for me in MAME. Correct.

[+jedimatt42]

Plato disk extraction needs some attention. I forgot I had to modify xdm99.py from @ralphb to decode strings from the disk as 'latin-1' or it gets UTF-8 errors. 

 

Working on the patch and PR now... xdt99.py also needs a python upgrade on the PI.. so gonna fork xdt99 so I can control the version on TIPIs.

 

Some disks may work as is, but some are known to have issues.

 

Also, Plato disks all have the volume name LESSONDISK, so I will produce an archive of them all extracted in a PLATO/<lesson name disk #>/LESSONDISK hierarchy that can just be unzipped onto the TIPI share. 

[+Vorticon]

One more question: the ROM upgrade is necessary for the pcode functionality, right? 

[+jedimatt42]

25 minutes ago, Vorticon said:

One more question: the ROM upgrade is necessary for the pcode functionality, right? 

 

Yes... no sector routine to call if the ROM isn't updated.

[+jedimatt42]

If people are interested in Plato on TIPI, here is an archive of all the plato disks ( from some other bundle on this forum ) unpacked and renamed from LESSONDISK back to something useful:  https://jedimatt42.com/downloads/plato-tipi-disks.zip

 

unzip into your TIPI file share, and it'll create a 'PLATO' directory, with folder under that for each lessondisk... 

 

...

[+Vorticon]

7 hours ago, jedimatt42 said:

 

Yes... no sector routine to call if the ROM isn't updated.

Yes of course. Sorry old chap, my brain is not what it used to be ?

I'll update the EPROM tonight and give it a whirl. Does copying a physical pcode disk to a TIPI folder work as far as creating a sector image? Also I have 180K pcode disk images which combine the Editor/Filer and the Compiler all on one disk for ease of use as well as a 360k image of a pcode work file. Will these be supported by FC?

[+jedimatt42]

Up to 360k should work.

[+Vorticon]

So I tested booting the Pcode card with the TIPI at 1000, and it works!

However, there are a couple of issues:

• The Editor issues a STACK OVERFLOW*REBOOT message after loading any text file or starting a new file. I tried 2 different disk images with similar results. I cannot replicate this error under Classic99
• Copying the contents of a real pascal disk from a physical drive to a folder on TIPI and pointing a disk drive to that folder does not work as it looks like it's not being recognized by the pcode card.

On the other hand, I am able to run existing programs fine and the Compiler and Filer work as they should.

[+jedimatt42]

3 hours ago, Vorticon said:

So I tested booting the Pcode card with the TIPI at 1000, and it works!

However, there are a couple of issues:

• The Editor issues a STACK OVERFLOW*REBOOT message after loading any text file or starting a new file. I tried 2 different disk images with similar results. I cannot replicate this error under Classic99

 

I was able to reproduce this, but only with the TIPI at >1000... lots of things seem to work, but loading a file into the editor fails. Running a file works. Loading a file does load the contents, but leaves that crashed state. I don't see it making any requests that result in an error.

 

This failure does not occur with TIPI at >1100. ( But then you have to remove your Floppy Controller )  -- I guess the partial working state at >1000 was too good to be true. 

 

Quote

• Copying the contents of a real pascal disk from a physical drive to a folder on TIPI and pointing a disk drive to that folder does not work as it looks like it's not being recognized by the pcode card.

On the other hand, I am able to run existing programs fine and the Compiler and Filer work as they should.

 

You have to copy the DSK sector dump image to the TIPI ( such as with the TIPI web-ui, you cannot just copy the PASCAL file from a PCODE disk into a directory. I don't know if that is what you did, but 'the contents' sounds like just the PASCAL file.  The tooling to take a sector dump from a physical disk is not yet in my toolset... surely something existed in the past?  If there is already a sector dumping tool for the 4A that can write to a DIS/FIX 128 file with open ended file name specification like TIPI.?X.PCODE.WORK/DSK then that would work.  But I have no idea how people started creating sector dump files from original media. Still on my todo list is to write a 4A utility for this. 

 

I'm not going to hold my breath that anything working with sector read write ever had any intention of working with anything other than a single floppy controller at crubase >1100. 

 

 

 

[+Vorticon]

I'm not giving up on this just yet. Since we are able to boot and run programs, perhaps there is a patch that could be written and run after boot to fix the Editor issue.

But first, I need to understand what is causing that error. Anders to the rescue again

[+mizapf]

11 hours ago, jedimatt42 said:

But I have no idea how people started creating sector dump files from original media. Still on my todo list is to write a 4A utility for this. 

In this thread:

 

[+jedimatt42]

My question goes back to the times before 2015?  No more than a few of this community would have used such a tool on Linux to read a real floppy drive..  not everyone had Fred's HDX either, and gotek drives seem too new as well ..  

 

This seems like one of those questions so obvious to anyone that I can't ask it correctly...

 

What did the majority of people use to move disk from a 4A to a PC/internet medium?

[+9640News]

1 hour ago, jedimatt42 said:

My question goes back to the times before 2015?  No more than a few of this community would have used such a tool on Linux to read a real floppy drive..  not everyone had Fred's HDX either, and gotek drives seem too new as well ..  

 

This seems like one of those questions so obvious to anyone that I can't ask it correctly...

 

What did the majority of people use to move disk from a 4A to a PC/internet medium?

TI99_PC

[+Ksarul]

1 hour ago, jedimatt42 said:

What did the majority of people use to move disk from a 4A to a PC/internet medium?

BITD, there was basically one choice: PC Transfer. That would let you move files between TI and PC formatted disks with an appropriate DSDD controller. There was a second option: the TI/IBM Connection cartridge from CorComp, but that only allowed text files. Very few people used the cartridge, as PC Transfer just did a whole lot more.

 

Note that BBS systems were also a hotbed of file movement between the TI and everything else. . .as were online services like Delphi, TexNet, CompuServe, and Prodigy.

[+Vorticon]

1 hour ago, jedimatt42 said:

My question goes back to the times before 2015?  No more than a few of this community would have used such a tool on Linux to read a real floppy drive..  not everyone had Fred's HDX either, and gotek drives seem too new as well ..  

 

This seems like one of those questions so obvious to anyone that I can't ask it correctly...

 

What did the majority of people use to move disk from a 4A to a PC/internet medium?

V9t9 emulator. It allowed for a connection via RS232 to the TI for file transfers. DOS based. Essentially format a blank floppy on the TI and send individual files to it from the PC to created a disk copy. Painful but it worked.

Then came the HDX which was a real life saver, particularly when DSK2PC came out for it as well as full integration with DM2K. But you still needed a wired connection.

Finally the holy grail appeared in the form of the TIPI and allowed us to shed the last of the shackles. Praise Thee

[+jedimatt42]

Oh, I might have used DSK2PC once. But it wrote to HDX directly, on the side, separate from your HDX FIADs. 

 

Ok, I guess I have to write another program

[+mizapf]

16 hours ago, jedimatt42 said:

My question goes back to the times before 2015?  No more than a few of this community would have used such a tool on Linux to read a real floppy drive..

Well, yes, I used that tool around 2008 to create DSK images from all of my floppy disks. This is a valid answer to your question. ?

 

But I know what you mean; this is a well-known challenge for me: to formulate a question so that the students give me the answer that I expect. And I know I must not formulate closed questions like "Can you explain why this XY behaves in this way?" - Answer: "No" (actually correct, he could not explain it)

 

You don't need to understand the following questions and answers in a famous interview in German television with Willy Brandt, chancellor from 1969-1974:

 

 

[+acadiel]

Great job, Matt!  Can't wait to give it a whirl.

 

I honestly need to find space to where I can keep my CC 9900 and my TIPI setups both going.  I'm constantly switching between them!  LOL

 

[+InsaneMultitasker]

I finally got around to installing the JTAG header on my 2nd TIPI card so that I could update its CPLD. 

 

@jedimatt42 when I enter the 'curl' command from the wiki, the response is 'no valid openPGP data found.  (I used my RPI to update the first card's CPLD in 2020, however, I reformatted the SD card back then and didn't reinstall xc3sprog at that time.)  How should I move forward and are there any wiki steps in need of any refreshing?  Thank you for your help.  

 

---

tipi@tipi:~ $ curl https://apt.matrix.one/doc/apt-key.gpg | sudo apt-key add -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
gpg: no valid OpenPGP data found.
tipi@tipi:~ $

---

 

Wiki steps: 

CPLD Programming With PI · jedimatt42/tipi Wiki · GitHub

 

On 4/11/2020 at 6:42 PM, InsaneMultitasker said:

I prepped my TIPI-PEB card and am about ready to update the CPLD.  From your comments it seems that the two items above are the only differences you encountered in the instructions.  One quick question: did you type all of the following in at the console?  It isn't clear to me if this is a "batch" file or meant to be keyed in, one line at a time. 

 

 

 

 

[+jedimatt42]

I've had to update this wiki page in the past already. The off-site references are volatile. Once I figure out what the recommendation will be, I'll have to capture the tooling and get it onto the default SD card images... Save the occasional hassle.  

 

I'll look at the details in the morning.

[+InsaneMultitasker]

1 hour ago, jedimatt42 said:

I've had to update this wiki page in the past already. The offset references are volatile. Once I figure out what the recommendation will be, I'll have to capture the tooling and get it onto the default SD card images... Save the occasional hassle.  

 

I'll look at the details in the morning.

Understood.  I may be fighting some other issue concurrently.  I reinstalled the known, working TIPI card and it now hung/hangs whenever I tried to access files via the Geneve hardware. (Edit)

 

I downloaded the current image from the downloads page (2.37) and used BalenaEtcher to write the image.  The RPI boots and seems ok, but the system hangs at "CALL TIPI".  I tried the troubleshooting steps under the TRIAGE section.  Troubleshooting · jedimatt42/tipi Wiki · GitHub    After fiddling with that a while, I reimaged using an older 2.5 file (this version kills the monitor output near the end of the bootup) for comparison.  The results seem to be the same.  I have this RPI connected via Ethernet so I used PuTTY to log into the TIPI and these are the results.  I assume the services it cannot find are needed?   I am going to call it a day.  Fortunately, I was wise enough to back up my TIPI share, a precaution I don't always remember to execute. 

 

tipi@tipi:~ $ sudo systemctl status tipi*
Unit tipi.config.service could not be found.
Unit tipi_disk.service could not be found.
Unit tipi.uuid.service could not be found.
● tipi.service - TI-99/4A DSR Service
   Loaded: loaded (/lib/systemd/system/tipi.service; enabled; vendor preset: ena
   Active: active (running) since Sat 2022-08-20 21:40:41 PDT; 1min 27s ago
 Main PID: 1738 (tipi.sh)
    Tasks: 2 (limit: 2200)
   Memory: 4.0M
   CGroup: /system.slice/tipi.service
           ├─1738 /bin/bash /home/tipi/tipi/services/tipi.sh
           └─1746 python ./TipiService.py

Aug 20 21:40:41 tipi systemd[1]: Started TI-99/4A DSR Service.
Aug 20 21:40:41 tipi tipi.sh[1738]: checking for operation mode...

tipi@tipi:~ $ tipi@tipi:~ $ sudo tail -f /var/log/tipi/tipi.log

tail: cannot open '/var/log/tipi/tipi.log' for reading: No such file or directory
tail: no files remaining
 

 

TIPI log file not found output from tipi:9900/logs :

Spoiler

 

 

Here is the daemon.log file via the browser for v2.37:

 

 

Spoiler

My TIPI

Files

Tools

/var/log/daemon.log

goto bottom

Aug 20 22:13:36 tipi systemd[1]: logrotate.service: Succeeded.
Aug 20 22:13:36 tipi systemd[1]: Started Rotate log files.
Aug 20 22:13:37 tipi systemd[1]: phpsessionclean.service: Succeeded.
Aug 20 22:13:37 tipi systemd[1]: Started Clean php session files.
Aug 20 22:13:38 tipi systemd[1]: man-db.service: Succeeded.
Aug 20 22:13:38 tipi systemd[1]: Started Daily man-db regeneration.
Aug 20 22:13:39 tipi systemd[1]: apt-daily.service: Succeeded.
Aug 20 22:13:39 tipi systemd[1]: Started Daily apt download activities.
Aug 20 22:13:39 tipi systemd[1]: Starting Daily apt upgrade and clean activities...
Aug 20 22:13:40 tipi systemd[1]: systemd-hostnamed.service: Succeeded.
Aug 20 22:13:41 tipi systemd[1]: apt-daily-upgrade.service: Succeeded.
Aug 20 22:13:41 tipi systemd[1]: Started Daily apt upgrade and clean activities.
Aug 20 22:13:52 tipi systemd[1]: Created slice User Slice of UID 999.
Aug 20 22:13:52 tipi systemd[1]: Starting User Runtime Directory /run/user/999...
Aug 20 22:13:52 tipi systemd[1]: Started User Runtime Directory /run/user/999.
Aug 20 22:13:52 tipi systemd[1]: Starting User Manager for UID 999...
Aug 20 22:13:53 tipi systemd[868]: Listening on GnuPG network certificate management daemon.
Aug 20 22:13:53 tipi systemd[868]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Aug 20 22:13:53 tipi systemd[868]: Reached target Timers.
Aug 20 22:13:53 tipi systemd[868]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Aug 20 22:13:53 tipi systemd[868]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Aug 20 22:13:53 tipi systemd[868]: Reached target Paths.
Aug 20 22:13:53 tipi systemd[868]: Listening on GnuPG cryptographic agent and passphrase cache.
Aug 20 22:13:53 tipi systemd[868]: Reached target Sockets.
Aug 20 22:13:53 tipi systemd[868]: Reached target Basic System.
Aug 20 22:13:53 tipi systemd[868]: Reached target Default.
Aug 20 22:13:53 tipi systemd[1]: Started User Manager for UID 999.
Aug 20 22:13:53 tipi systemd[868]: Startup finished in 244ms.
Aug 20 22:13:53 tipi systemd[1]: Started Session 1 of user tipi.
Aug 20 22:17:58 tipi systemd[1]: Stopping TI-99/4A DSR Service...
Aug 20 22:17:58 tipi systemd[1]: tipi.service: Main process exited, code=killed, status=15/TERM
Aug 20 22:17:58 tipi systemd[1]: tipi.service: Succeeded.
Aug 20 22:17:58 tipi systemd[1]: Stopped TI-99/4A DSR Service.
Aug 20 22:17:58 tipi systemd[1]: Started TI-99/4A DSR Service.
Aug 20 22:17:58 tipi tipi.sh[1575]: checking for operation mode...
Aug 20 22:17:58 tipi tipi.sh[1575]: TIPI_SIG_DELAY=100
Aug 20 22:18:10 tipi app_run.sh[555]: 2022-08-20 22:18:10,270 - werkzeug - INFO - 192.168.0.8 - - [20/Aug/2022 22:18:10] "#033[35m#033[1mGET /logs HTTP/1.1#033[0m" 500 -
Aug 20 22:18:10 tipi app_run.sh[555]: Traceback (most recent call last):
Aug 20 22:18:10 tipi app_run.sh[555]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 2091, in __call__
Aug 20 22:18:10 tipi app_run.sh[555]:     return self.wsgi_app(environ, start_response)
Aug 20 22:18:10 tipi app_run.sh[555]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask_socketio/__init__.py", line 44, in __call__
Aug 20 22:18:10 tipi app_run.sh[555]:     start_response)
Aug 20 22:18:10 tipi app_run.sh[555]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/engineio/middleware.py", line 74, in __call__
Aug 20 22:18:10 tipi app_run.sh[555]:     return self.wsgi_app(environ, start_response)
Aug 20 22:18:10 tipi app_run.sh[555]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 2076, in wsgi_app
Aug 20 22:18:10 tipi app_run.sh[555]:     response = self.handle_exception(e)
Aug 20 22:18:10 tipi app_run.sh[555]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 2073, in wsgi_app
Aug 20 22:18:10 tipi app_run.sh[555]:     response = self.full_dispatch_request()
Aug 20 22:18:10 tipi app_run.sh[555]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 1518, in full_dispatch_request
Aug 20 22:18:10 tipi app_run.sh[555]:     rv = self.handle_user_exception(e)
Aug 20 22:18:10 tipi app_run.sh[555]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 1516, in full_dispatch_request
Aug 20 22:18:10 tipi app_run.sh[555]:     rv = self.dispatch_request()
Aug 20 22:18:10 tipi app_run.sh[555]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 1502, in dispatch_request
Aug 20 22:18:10 tipi app_run.sh[555]:     return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
Aug 20 22:18:10 tipi app_run.sh[555]:   File "/home/tipi/tipi/htdocs/route.py", line 203, in logs
Aug 20 22:18:10 tipi app_run.sh[555]:     logdata = tipi_admin.logdata()
Aug 20 22:18:10 tipi app_run.sh[555]:   File "/home/tipi/tipi/htdocs/tipi_admin.py", line 18, in logdata
Aug 20 22:18:10 tipi app_run.sh[555]:     with io.open("/var/log/tipi/tipi.log", mode="r", encoding="utf-8") as f:
Aug 20 22:18:10 tipi app_run.sh[555]: FileNotFoundError: [Errno 2] No such file or directory: '/var/log/tipi/tipi.log'
Aug 20 22:18:10 tipi app_run.sh[555]: 2022-08-20 22:18:10,326 - werkzeug - INFO - 192.168.0.8 - - [20/Aug/2022 22:18:10] "GET /logs?__debugger__=yes&cmd=resource&f=style.css HTTP/1.1" 200 -
Aug 20 22:18:10 tipi app_run.sh[555]: 2022-08-20 22:18:10,335 - werkzeug - INFO - 192.168.0.8 - - [20/Aug/2022 22:18:10] "GET /logs?__debugger__=yes&cmd=resource&f=debugger.js HTTP/1.1" 200 -
Aug 20 22:18:10 tipi app_run.sh[555]: 2022-08-20 22:18:10,358 - werkzeug - INFO - 192.168.0.8 - - [20/Aug/2022 22:18:10] "GET /logs?__debugger__=yes&cmd=resource&f=ubuntu.ttf HTTP/1.1" 200 -
Aug 20 22:18:10 tipi app_run.sh[555]: 2022-08-20 22:18:10,362 - werkzeug - INFO - 192.168.0.8 - - [20/Aug/2022 22:18:10] "GET /logs?__debugger__=yes&cmd=resource&f=console.png HTTP/1.1" 200 -
Aug 20 22:19:25 tipi systemd[1]: Started Session 4 of user tipi.
Aug 20 22:21:38 tipi app_run.sh[555]: 2022-08-20 22:21:38,822 - werkzeug - INFO - 192.168.0.8 - - [20/Aug/2022 22:21:38] "#033[32mGET / HTTP/1.1#033[0m" 302 -
Aug 20 22:21:38 tipi app_run.sh[555]: 2022-08-20 22:21:38,939 - werkzeug - INFO - 192.168.0.8 - - [20/Aug/2022 22:21:38] "GET /files HTTP/1.1" 200 -

 

Here is the daemon.log file via the browser v2.5 in case it is of any use: 

 

Spoiler

My TIPI

Files

Settings

/var/log/daemon.log

goto bottom

Aug 20 21:35:47 tipi systemd[1]: logrotate.service: Succeeded.
Aug 20 21:35:47 tipi systemd[1]: Started Rotate log files.
Aug 20 21:35:48 tipi systemd[1]: phpsessionclean.service: Succeeded.
Aug 20 21:35:48 tipi systemd[1]: Started Clean php session files.
Aug 20 21:35:49 tipi systemd[1]: man-db.service: Succeeded.
Aug 20 21:35:49 tipi systemd[1]: Started Daily man-db regeneration.
Aug 20 21:35:50 tipi systemd[1]: apt-daily.service: Succeeded.
Aug 20 21:35:50 tipi systemd[1]: Started Daily apt download activities.
Aug 20 21:35:50 tipi systemd[1]: Starting Daily apt upgrade and clean activities...
Aug 20 21:35:52 tipi systemd[1]: apt-daily-upgrade.service: Succeeded.
Aug 20 21:35:52 tipi systemd[1]: Started Daily apt upgrade and clean activities.
Aug 20 21:39:01 tipi systemd[1]: Starting Clean php session files...
Aug 20 21:39:01 tipi systemd[1]: phpsessionclean.service: Succeeded.
Aug 20 21:39:01 tipi systemd[1]: Started Clean php session files.
Aug 20 21:40:40 tipi systemd[1]: Stopping TI-99/4A DSR Service...
Aug 20 21:40:40 tipi systemd[1]: tipi.service: Main process exited, code=killed, status=15/TERM
Aug 20 21:40:40 tipi systemd[1]: tipi.service: Succeeded.
Aug 20 21:40:40 tipi systemd[1]: Stopped TI-99/4A DSR Service.
Aug 20 21:40:40 tipi systemd[1]: Started TI-99/4A DSR Service.
Aug 20 21:40:40 tipi tipi.sh[1720]: checking for operation mode...
Aug 20 21:40:41 tipi systemd[1]: Stopping TI-99/4A DSR Service...
Aug 20 21:40:41 tipi systemd[1]: tipi.service: Main process exited, code=killed, status=15/TERM
Aug 20 21:40:41 tipi systemd[1]: tipi.service: Succeeded.
Aug 20 21:40:41 tipi systemd[1]: Stopped TI-99/4A DSR Service.
Aug 20 21:40:41 tipi systemd[1]: Started TI-99/4A DSR Service.
Aug 20 21:40:41 tipi tipi.sh[1738]: checking for operation mode...
Aug 20 21:42:36 tipi systemd[1]: Starting Cleanup of Temporary Directories...
Aug 20 21:42:36 tipi systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Aug 20 21:42:36 tipi systemd[1]: Started Cleanup of Temporary Directories.
Aug 20 21:57:33 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:33] "#033[32mGET / HTTP/1.1#033[0m" 302 -
Aug 20 21:57:34 tipi tipimon.sh[496]: 2022-08-20 21:57:34,082 - inotify.adapters - DEBUG - Events received from epoll: ['IN_ACCESS']
Aug 20 21:57:34 tipi tipimon.sh[496]: 2022-08-20 21:57:34,083 - inotify.adapters - DEBUG - Events received in stream: ['IN_OPEN', 'IN_ISDIR']
Aug 20 21:57:34 tipi tipimon.sh[496]: 2022-08-20 21:57:34,083 - tipi_monitor - INFO - locking
Aug 20 21:57:34 tipi tipimon.sh[496]: 2022-08-20 21:57:34,084 - tipi_monitor - INFO - released lock
Aug 20 21:57:34 tipi tipimon.sh[496]: 2022-08-20 21:57:34,085 - inotify.adapters - DEBUG - Events received in stream: ['IN_ACCESS', 'IN_ISDIR']
Aug 20 21:57:34 tipi tipimon.sh[496]: 2022-08-20 21:57:34,085 - tipi_monitor - INFO - locking
Aug 20 21:57:34 tipi tipimon.sh[496]: 2022-08-20 21:57:34,085 - tipi_monitor - INFO - released lock
Aug 20 21:57:34 tipi tipimon.sh[496]: 2022-08-20 21:57:34,086 - inotify.adapters - DEBUG - Events received in stream: ['IN_CLOSE_NOWRITE', 'IN_ISDIR']
Aug 20 21:57:34 tipi tipimon.sh[496]: 2022-08-20 21:57:34,086 - tipi_monitor - INFO - locking
Aug 20 21:57:34 tipi tipimon.sh[496]: 2022-08-20 21:57:34,087 - tipi_monitor - INFO - released lock
Aug 20 21:57:34 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:34] "#033[37mGET /files HTTP/1.1#033[0m" 200 -
Aug 20 21:57:34 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:34] "#033[36mGET /css/style.css HTTP/1.1#033[0m" 304 -
Aug 20 21:57:34 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:34] "#033[36mGET /images/new_file_icon.png HTTP/1.1#033[0m" 304 -
Aug 20 21:57:34 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:34] "#033[36mGET /images/new_folder_icon.png HTTP/1.1#033[0m" 304 -
Aug 20 21:57:34 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:34] "#033[36mGET /images/upload_icon.png HTTP/1.1#033[0m" 304 -
Aug 20 21:57:34 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:34] "#033[36mGET /images/refresh_icon.png HTTP/1.1#033[0m" 304 -
Aug 20 21:57:34 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:34] "#033[36mGET /images/folder_icon.png HTTP/1.1#033[0m" 304 -
Aug 20 21:57:34 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:34] "#033[36mGET /images/download_icon.png HTTP/1.1#033[0m" 304 -
Aug 20 21:57:34 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:34] "#033[36mGET /images/ti_logo_icon.jpg HTTP/1.1#033[0m" 304 -
Aug 20 21:57:37 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:37] "#033[35m#033[1mGET /logs HTTP/1.1#033[0m" 500 -
Aug 20 21:57:37 tipi app_run.sh[506]: Traceback (most recent call last):
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 2464, in __call__
Aug 20 21:57:37 tipi app_run.sh[506]:     return self.wsgi_app(environ, start_response)
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask_socketio/__init__.py", line 46, in __call__
Aug 20 21:57:37 tipi app_run.sh[506]:     start_response)
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/engineio/middleware.py", line 74, in __call__
Aug 20 21:57:37 tipi app_run.sh[506]:     return self.wsgi_app(environ, start_response)
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 2450, in wsgi_app
Aug 20 21:57:37 tipi app_run.sh[506]:     response = self.handle_exception(e)
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 1867, in handle_exception
Aug 20 21:57:37 tipi app_run.sh[506]:     reraise(exc_type, exc_value, tb)
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/_compat.py", line 39, in reraise
Aug 20 21:57:37 tipi app_run.sh[506]:     raise value
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 2447, in wsgi_app
Aug 20 21:57:37 tipi app_run.sh[506]:     response = self.full_dispatch_request()
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 1952, in full_dispatch_request
Aug 20 21:57:37 tipi app_run.sh[506]:     rv = self.handle_user_exception(e)
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 1821, in handle_user_exception
Aug 20 21:57:37 tipi app_run.sh[506]:     reraise(exc_type, exc_value, tb)
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/_compat.py", line 39, in reraise
Aug 20 21:57:37 tipi app_run.sh[506]:     raise value
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 1950, in full_dispatch_request
Aug 20 21:57:37 tipi app_run.sh[506]:     rv = self.dispatch_request()
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/ENV/lib/python3.7/site-packages/flask/app.py", line 1936, in dispatch_request
Aug 20 21:57:37 tipi app_run.sh[506]:     return self.view_functions[rule.endpoint](**req.view_args)
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/route.py", line 160, in logs
Aug 20 21:57:37 tipi app_run.sh[506]:     logdata = tipi_admin.logdata()
Aug 20 21:57:37 tipi app_run.sh[506]:   File "/home/tipi/tipi/htdocs/tipi_admin.py", line 18, in logdata
Aug 20 21:57:37 tipi app_run.sh[506]:     with io.open("/var/log/tipi/tipi.log", mode="r", encoding="utf-8") as f:
Aug 20 21:57:37 tipi app_run.sh[506]: FileNotFoundError: [Errno 2] No such file or directory: '/var/log/tipi/tipi.log'
Aug 20 21:57:37 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:37] "#033[37mGET /logs?__debugger__=yes&cmd=resource&f=style.css HTTP/1.1#033[0m" 200 -
Aug 20 21:57:37 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:37] "#033[37mGET /logs?__debugger__=yes&cmd=resource&f=jquery.js HTTP/1.1#033[0m" 200 -
Aug 20 21:57:37 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:37] "#033[37mGET /logs?__debugger__=yes&cmd=resource&f=debugger.js HTTP/1.1#033[0m" 200 -
Aug 20 21:57:37 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:37] "#033[37mGET /logs?__debugger__=yes&cmd=resource&f=ubuntu.ttf HTTP/1.1#033[0m" 200 -
Aug 20 21:57:37 tipi app_run.sh[506]: 192.168.0.8 - - [20/Aug/2022 21:57:37] "#033[37mGET /logs?__debugger__=yes&cmd=resource&f=console.png HTTP/1.1#033[0m" 200 -

 

[+jedimatt42]

Except for there being no tipi.log, the rest of that looks as expected. Most of the noise is the web ui complaining that there is no tipi.log.

 

The missing service noise is misleading. 

 

I need to update my docs on using systemctl status... When sitting in /home/TIPI, the shell replaced tipi* with the list of files and dirs that matched the wildcard expression instead of matching the services starting with tipi. It should have been :

 

sudo systemctl status 'tipi*'

 

so the expression can be handled by systemctl instead of the shell. But it lucked into the main TIPI service cause the shell expression evaluation matched the tipi directory...

[+InsaneMultitasker]

thank you.  I have a spare RPI that I'll pop the 2.37 imaged SD into. If the logs seem ok to you and the spare RPI doesn't bring things back to working order, then I'm guessing both of my TIPI cards are 'dead'.

[+jedimatt42]

For programming the CPLD from the PI, I've compiled and zipped up the xc3sprog binary and put download instructions in place of the package install instructions on my wiki page. The xc3sprog program depends on wiringPi, and there are issues in that community, so it is no longer in distribution... I suspect that motivated the author to stop updating their binary distribution mechanism. 

 

I've added a little more to the troubleshooting wiki page as well.   You can basically go into /home/tipi/tipi/services, and then sudo systemctl stop tipi.service, and then run ./tipi.sh to see if it is blowing up with more data before it gets to creating it's logging infrastructure.

[+jedimatt42]

There is also this page, referenced near the bottom of the Troubleshooting page, that describes working with EasyBug to verify byte level communication between the PI and the 4A.