Omega-TI Posted December 28, 2013 Share Posted December 28, 2013 (edited) I was thinking and pondering the technical aspects and possibility of using the HDX modification and the HDX program itself, if it were updated, on constantly reading the PC's clock every second and sending that data to the TI. This would be a 100% software solution to obtaining a RTC, by emulating one. It seems to me that the difficult part would be doing something with the actual data, because on the TI's side the data would have to be read and possibly translated into a format that is usable by existing programs, say the CorComp or MBP formats. Is this even remotely possible? Edited December 28, 2013 by Kevan Quote Link to comment Share on other sites More sharing options...
+arcadeshopper Posted December 28, 2013 Share Posted December 28, 2013 so basically now it has a hdx.clock device you can read the clock with.. your desire is to change that to allow a corcomp clock compatible interface? this would really only require the dsr to include the clock device to allow the same access as a corcomp clock, not sending the time all the time.. you request it the same way as you would with a corcomp clock card, by opening a file to the device CLOCK Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted December 28, 2013 Author Share Posted December 28, 2013 so basically now it has a hdx.clock device you can read the clock with.. your desire is to change that to allow a corcomp clock compatible interface? this would really only require the dsr to include the clock device to allow the same access as a corcomp clock, not sending the time all the time.. you request it the same way as you would with a corcomp clock card, by opening a file to the device CLOCK NO, I would LIKE it to have an HDX.CLOCK device. I think that would be an easy upgrade for a guy like Fred. All it would need to do is read the time, and send the ASCII text to the TI. Of course the modification would be worthless without the ability to use it on the TI's side. There are multiple programs on the TI that can already use a RTC, Remind and BOOT are just two that come to mind. Just something to think about. Quote Link to comment Share on other sites More sharing options...
+arcadeshopper Posted December 28, 2013 Share Posted December 28, 2013 NO, I would LIKE it to have an HDX.CLOCK device. I think that would be an easy upgrade for a guy like Fred. All it would need to do is read the time, and send the ASCII text to the TI. Of course the modification would be worthless without the ability to use it on the TI's side. There are multiple programs on the TI that can already use a RTC, Remind and BOOT are just two that come to mind. Just something to think about. So easy its already there... latest version has it Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted December 28, 2013 Author Share Posted December 28, 2013 (edited) So easy its already there... latest version has it Well I'll be damned! It is! Now I guess we just need the DSR for the TI side to get it to work with programs like BOOT and Remind-Me!. I tried "OPEN#1:"HDX1.CLOCK" in XB and it worked, so later I'll figure out how to import the data in XB. I'm assuming it'll be just like you said, the same method as CorComp used and that Classic99 also employs in Extended BASIC. Edited December 28, 2013 by Kevan Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted December 28, 2013 Author Share Posted December 28, 2013 Apparently I cannot access the HDX clock with the same method in Extended BASIC as I could with my old Triple Tech Card or the same way Tursi has implemented it in Classic99. In Classic99, this short program works... The very same program with the HDX1.CLOCK call gives the following result... According to the display on the HDX.... Is there another method that I do not know about? Or am I overlooking something really simple? Quote Link to comment Share on other sites More sharing options...
jens-eike Posted December 28, 2013 Share Posted December 28, 2013 On Fred's webpage, the function is documented as "TIME": (Why don't you get an error for opening "CLOCK"?) HDX1.TIME If a data file HDX1.TIME is opened in INPUT, OUTPUT, APPEND or UPDATE mode then it is possible to read the PC's time. The file characteristics for the HDX1.TIME file is INTERNAL, FIXED 32. Data written to the HDX1.TIME file is ignored (for now). Read example: 100 OPEN #1:"HDX1.TIME",INTERNAL,FIXED 110 INPUT #1:SEC$,MIN$,HOUR$,DAY$,MONTH$,YEAR$,DAYOFWEEK$ 120 CLOSE #1 Write example: 100 OPEN #1:"IDE.TIME",INTERNAL,FIXED 110 PRINT #1:SEC$,MIN$,HOUR$,DAY$,MONTH$,YEAR$ 120 CLOSE #1 Hours from 00 through 23, minutes and seconds from 00 through 59. The day of the week from 01 to 07 (01=Sunday). The month 01 through 12, day of the month 01 through 31 and the year 2000 through doomsday (which apparently is around the year 9999!) 1 Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted December 28, 2013 Author Share Posted December 28, 2013 On Fred's webpage, the function is documented as "TIME": (Why don't you get an error for opening "CLOCK"?) Success! Thank you for the the help and information! I dunno why I didn't get an error on CLOCK, but after it accepted it, I just ASSUMED it was the correct statement and could not figure out why it was not working! 10 CALL CLEAR :: CALL SCREEN(5) :: FOR CL=1 TO 13 :: CALL COLOR(CL,15,5) :: NEXT CL 20 OPEN #1:"HDX1.TIME",INTERNAL,FIXED 32 30 INPUT #1:SEC$,MIN$,HOURS$,DAY$,MONTH$,YEAR$,DAYOFWEEK$ 40 DISPLAY AT(2,2):"Time > ";HOURS$;":";MIN$;".";SEC$ 50 DISPLAY AT(3,2):"Date > ";MONTH$;"/";DAY$;"/";YEAR$ 60 CLOSE #1 :: GOTO 30 Errors corrected per Gazoo's suggestion. Quote Link to comment Share on other sites More sharing options...
Gazoo Posted December 29, 2013 Share Posted December 29, 2013 Success! Thank you for the the help and information! I dunno why I didn't get an error on CLOCK, but after it accepted it, I just ASSUMED it was the correct statement and could not figure out why it was not working! 10 CALL CLEAR :: CALL SCREEN(5) :: FOR CL=1 TO 13 :: CALL COLOR(CL,15,5) :: NEXT CL 20 OPEN #1:"HDX1.TIME",INTERNAL,FIXED 32 30 INPUT #1:SEC$,MIN$,HOURS$,DAY$,MONTH$,YEAR$ 40 DISPLAY AT(2,2):"Time > ";HOURS$;":";MIN$;".";SEC$ 50 DISPLAY AT(3,2):"Date > ";MONTH$;"/";DAY$;"/";YEAR$ 60 CLOSE #1 :: GOTO 20 Do you need to close and then reopen the file? Can you just put a GOTO 30 at the end of line 50? Gazoo 1 Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted December 29, 2013 Author Share Posted December 29, 2013 (edited) Do you need to close and then reopen the file? Can you just put a GOTO 30 at the end of line 50? Gazoo Actually yes, the file needs to be closed, if I tried that it would take the data in an endless stream of records, getting the appropriate data out of sequence and then displaying the information in the wrong fields. The result is an unusable, unreadable mess. ** EDIT ** I found out why! I forgot to input day of the week string, after I fixed the bug, your suggestion worked. Thanks Gazoo! Edited December 29, 2013 by Kevan Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.