Jump to content
Have You Played Atari Today?
2600|5200|7800|Lynx|Jaguar|Forums|Store
IGNORED

#FujiNet - a WIP SIO Network Adapter for the Atari 8-bit

tschak909

By tschak909
in #FujiNet SIO Network Adapter

 Share

Recommended Posts

Mr Robot River Patroller

Mr Robot

Posted
Posted
1 hour ago, Atari_bbs_fan said:

Will it be possible to rework older Fujinet boards to be compatible with v1.3 boards or is it a whole new design?

Anything is possible, but it wouldn't be easy. The connection between the Atari and the ESP32 is now buffered so all of that would need to be reworked and the power goes through a couple of new mosfets so all that needs to be redone too. The ESP to USB/SD/LED's/Switches is all mostly the same.

Link to comment
Share on other sites
tschak909 Quadrunner

tschak909

Posted
  • Author
Posted (edited)

It must be understood that what culminated in the 1.3 boards was really unexpected, it was a case of people testing with many different configurations, and we found very specific problems, (1) that the fuji's power switch being off was causing the ESP32 to be slightly back-bias powered (WHOOPS), (2) People with external peripherals other than fujinet were seeing bus signals get seriously degraded coming out of the fujinet pass-through due to a lack of buffering. This worked okay at normal speeds, but high speed transfers were seriously affected.

 

It's a 1.3 revision because it took three board spins to get it right.

 

-Thom

Edited by tschak909
Link to comment
Share on other sites
Mr Robot River Patroller

Mr Robot

Posted
Posted

Also a few incremental improvements: the reset button is now a safe reset, not hard reset as before, the resistor that fixes cassette loading now has a home rather than between two sio pins, the on/off switch has a little hat to make it more robust, the USB UART is now a smaller part (all the hand solderers say "Thanks Mozz!" :D ) because the original part is out of stock everywhere.

 

 

  • Like 1
Link to comment
Share on other sites
FifthPlayer Dragonstomper

FifthPlayer

Posted
Posted (edited)

I finally set up my Atari with Fujinet today.

 

I set up a local TNFS server on a Raspberry Pi that works great - I can browse, mount disks, and boot.  But remote Internet hosts such as fujinet.online behave very unreliably (actually all that come pre-loaded into the Fujinet firmware).  Sometimes I can browse remote TNFS directories, but sometimes it times out after a long delay.  Sometimes I can boot off remote disk images, sometimes it hangs in the middle of boot.

 

I'm using an unmodified 130XE with Fujinet as the only peripheral on the device (and a joystick, FWIW).  The Fujinet is running the 2020-12-14 firmware.

 

Has anyone had this problem? 

 

Update: log of a failed attempt to browse fujinet.online - also attached a photo of the config app after the failed read.

 

[17:36:32]
[17:36:32]CF: 70 f9 01 00 6b
[17:36:32]sioFuji::sio_process() called
[17:36:32]ACK!
[17:36:32]Fuji cmd: MOUNT HOST
[17:36:32]::mount {1} "FujiNet.online"
[17:36:32]::mount_local Attempting mount of "FujiNet.online"
[17:36:32]::mount_tnfs {1:0} "FujiNet.online"
[17:36:32]Calling TNFS::begin
[17:36:32]Resolving hostname "FujiNet.online"
[17:36:32]Resoled to address 157.245.127.133
[17:36:32]TNFS mount FujiNet.online[157.245.127.133]:16384
[17:36:32]TNFS mount successful. session: 0xf813, version: 0x0102, min_retry: 1000ms
[17:36:32]vfs_tnfs_register "/tnfs0x3fff4be4" @ 0x3fff4be4 = 0 "ESP_OK"
[17:36:32]COMPLETE!
[17:36:32]
[17:36:32]CF: 70 f7 01 00 69
[17:36:32]sioFuji::sio_process() called
[17:36:32]ACK!
[17:36:32]Fuji cmd: OPEN DIRECTORY
[17:36:32]<-SIO read 256 bytes
[17:36:32]ACK!
[17:36:32]Opening directory: "/", pattern: ""
[17:36:32]::dir_open {1:2} "/", pattern ""
[17:36:32]::dir_open actual path = "/"
[17:36:32]TNFS open directory: sortopts=0x00 diropts=0x00 maxresults=0x0000 pattern="" path="/"
[17:36:32]Directory opened, handle ID: 0, entries: 11
[17:36:32]COMPLETE!
[17:36:32]
[17:36:32]CF: 70 e4 00 00 55
[17:36:32]sioFuji::sio_process() called
[17:36:32]ACK!
[17:36:32]Fuji cmd: SET DIRECTORY POSITION
[17:36:32]::dir_seek {1:2} 0
[17:36:33]COMPLETE!
[17:36:33]
[17:36:33]CF: 70 f6 24 00 8b
[17:36:33]sioFuji::sio_process() called
[17:36:33]ACK!
[17:36:33]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[17:36:33]::dir_nextfile {1:2}
[17:36:35]Timeout after 2000 milliseconds. Retrying
[17:36:36]Reached end of of directory
[17:36:36]->SIO write 36 bytes
[17:36:36]COMPLETE!
[17:36:36]
[17:36:36]CF: 70 f5 01 00 67
[17:36:36]sioFuji::sio_process() called
[17:36:36]ACK!
[17:36:36]Fuji cmd: CLOSE DIRECTORY
[17:36:36]COMPLETE!

 

PXL_20201221_013853762.jpg

Edited by FifthPlayer
added log
Link to comment
Share on other sites
FifthPlayer Dragonstomper

FifthPlayer

Posted
Posted (edited)
5 minutes ago, tschak909 said:

The quality of your WiFi connection is important. and yes, please output debugging information.

-Thom

Updated with debug output.  The Fujinet is not more than 10 feet away from the wifi router, so signal strength is likely not an issue.  But I will look into the signal quality and possible interference.

Edited by FifthPlayer
Link to comment
Share on other sites
tschak909 Quadrunner

tschak909

Posted
  • Author
Posted
Just now, FifthPlayer said:

Updated with debug output.  The Fujinet is not more than 10 feet away from the wifi router, so signal strength is likely not an issue.

Ok, I don't see anything unusual from your directory output. can you try atari-apps.irata.online ?

 

also perhaps attach a traceroute to both atari-apps.irata.online and fujinet.online?

 

-Thom

 

Link to comment
Share on other sites
mozzwald Stargunner

mozzwald

Posted
Posted
29 minutes ago, FifthPlayer said:

Update: log of a failed attempt to browse fujinet.online - also attached a photo of the config app after the failed read.

 

14 minutes ago, tschak909 said:

and yes, please output debugging information.

 

If it helps, here's debug from the tnfs server:

Spoiler

111.222.333.444 s=f813 c=00 q=00 | Mounted / OK, SID=f813
111.222.333.444 s=f813 c=17 q=01 | REQUEST cmd=0x17 TNFS_OPENDIRX
111.222.333.444 s=f813 c=17 q=01 | opendirx: diropt=0x00, sortopt=0x00, max=0x0000, pat="", path="/"
111.222.333.444 s=f813 c=17 q=01 | opendirx response: handle=0, count=11
111.222.333.444 s=f813 c=16 q=02 | REQUEST cmd=0x16 TNFS_SEEKDIR
tnfs_seekdir to pos 0
111.222.333.444 s=f813 c=18 q=03 | REQUEST cmd=0x18 TNFS_READDIRX
111.222.333.444 s=f813 c=18 q=03 | readdirx request for 32 entries
111.222.333.444 s=f813 c=18 q=03 | readdirx responding with 11 entries, status_flags=0x1
111.222.333.444 s=f813 c=18 q=04 | REQUEST cmd=0x18 TNFS_READDIRX
111.222.333.444 s=f813 c=18 q=04 | readdirx no more entries - returning EOF
111.222.333.444 s=f813 c=18 q=04 | readdirx request for 32 entries
111.222.333.444 s=f813 c=18 q=04 | readdirx responding with 0 entries, status_flags=0x1
111.222.333.444 s=f813 c=12 q=05 | REQUEST cmd=0x12 TNFS_CLOSEDIR


 

Link to comment
Share on other sites
FifthPlayer Dragonstomper

FifthPlayer

Posted
Posted (edited)
29 minutes ago, tschak909 said:

Ok, I don't see anything unusual from your directory output. can you try atari-apps.irata.online ?

also perhaps attach a traceroute to both atari-apps.irata.online and fujinet.online?

 

[17:50:12]
[17:50:12]CF: 70 f4 00 00 65
[17:50:12]sioFuji::sio_process() called
[17:50:12]ACK!
[17:50:12]Fuji cmd: READ HOST SLOTS
[17:50:12]->SIO write 256 bytes
[17:50:12]COMPLETE!
[17:50:12]
[17:50:12]CF: 70 f2 00 00 63
[17:50:12]sioFuji::sio_process() called
[17:50:12]ACK!
[17:50:12]Fuji cmd: READ DEVICE SLOTS
[17:50:12]->SIO write 304 bytes
[17:50:12]COMPLETE!
[17:50:15]
[17:50:15]CF: 70 f9 02 00 6c
[17:50:15]sioFuji::sio_process() called
[17:50:15]ACK!
[17:50:15]Fuji cmd: MOUNT HOST
[17:50:15]::mount {2} "atari-apps.irata.online"
[17:50:15]::mount_local Attempting mount of "atari-apps.irata.online"
[17:50:15]::mount_tnfs {2:2} "atari-apps.irata.online"
[17:50:15]::mount_tnfs Currently connected to host "atari-apps.irata.online"
[17:50:15]COMPLETE!
[17:50:15]
[17:50:15]CF: 70 f7 02 00 6a
[17:50:15]sioFuji::sio_process() called
[17:50:15]ACK!
[17:50:15]Fuji cmd: OPEN DIRECTORY
[17:50:15]<-SIO read 256 bytes
[17:50:15]ACK!
[17:50:15]Opening directory: "/", pattern: ""
[17:50:15]::dir_open {2:2} "/", pattern ""
[17:50:15]::dir_open actual path = "/"
[17:50:15]TNFS open directory: sortopts=0x00 diropts=0x00 maxresults=0x0000 pattern="" path="/"
[17:50:16]Directory opened, handle ID: 0, entries: 18
[17:50:16]COMPLETE!
[17:50:16]
[17:50:16]CF: 70 e4 00 00 55
[17:50:16]sioFuji::sio_process() called
[17:50:16]ACK!
[17:50:16]Fuji cmd: SET DIRECTORY POSITION
[17:50:16]::dir_seek {2:2} 0
[17:50:16]COMPLETE!
[17:50:16]
[17:50:16]CF: 70 f6 24 00 8b
[17:50:16]sioFuji::sio_process() called
[17:50:16]ACK!
[17:50:16]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[17:50:16]::dir_nextfile {2:2}
[17:50:18]Timeout after 2000 milliseconds. Retrying
[17:50:19]Reached end of of directory
[17:50:19]->SIO write 36 bytes
[17:50:19]COMPLETE!
[17:50:19]
[17:50:19]CF: 70 f5 02 00 68
[17:50:19]sioFuji::sio_process() called
[17:50:19]ACK!
[17:50:19]Fuji cmd: CLOSE DIRECTORY
[17:50:20]COMPLETE!

  

pi@jotabout:~ $ traceroute fujinet.online
traceroute to fujinet.online (157.245.127.133), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  2.063 ms  1.720 ms  1.552 ms
 2  gw-v200b.static.monkeybrains.net (199.241.203.129)  78.942 ms  82.973 ms  82.727 ms
 3  172.17.22.208 (172.17.22.208)  82.681 ms  82.456 ms  82.471 ms
 4  172.17.18.138 (172.17.18.138)  111.460 ms  111.174 ms  111.144 ms
 5  172.17.21.194 (172.17.21.194)  85.164 ms  83.821 ms  85.922 ms
 6  172.17.22.206 (172.17.22.206)  109.127 ms  104.807 ms  105.729 ms
 7  172.17.21.218 (172.17.21.218)  105.720 ms  70.233 ms  48.385 ms
 8  172.17.20.59 (172.17.20.59)  41.117 ms  40.762 ms  40.678 ms
 9  172.17.16.242 (172.17.16.242)  46.378 ms  46.116 ms  49.313 ms
10  10ge16-19.core1.sfo1.he.net (216.218.244.49)  48.991 ms  36.432 ms  36.290 ms
11  100ge3-1.core4.fmt2.he.net (72.52.92.25)  42.461 ms 10ge5-6.core1.sjc2.he.net (184.105.213.161)  67.898 ms  67.752 ms
12  100ge10-2.core1.nyc4.he.net (184.105.81.217)  109.124 ms 10ge7-5.core1.sjc2.he.net (72.52.92.70)  43.932 ms 100ge14-1.core1.sjc2.he.net (184.105.213.157)  83.766 ms
13  * 100ge10-2.core1.nyc4.he.net (184.105.81.217)  148.483 ms  140.602 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

pi@jotabout:~ $ traceroute atari-apps.irata.online
traceroute to atari-apps.irata.online (35.184.35.130), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 3.324 ms 3.194 ms 3.105 ms
2 gw-v200b.static.monkeybrains.net (199.241.203.129) 19.721 ms 19.491 ms 19.362 ms
3 172.17.22.208 (172.17.22.208) 22.925 ms 22.691 ms 22.580 ms
4 172.17.18.138 (172.17.18.138) 17.231 ms 18.304 ms 15.762 ms
5 172.17.21.194 (172.17.21.194) 19.172 ms 19.029 ms 21.514 ms
6 172.17.22.206 (172.17.22.206) 21.336 ms 24.901 ms 29.012 ms
7 172.17.21.218 (172.17.21.218) 37.613 ms 19.467 ms 19.241 ms
8 172.17.20.59 (172.17.20.59) 16.879 ms 16.789 ms 16.550 ms
9 172.17.16.242 (172.17.16.242) 25.262 ms 25.209 ms 25.094 ms
10 208.52.0.73 (208.52.0.73) 25.066 ms 24.964 ms 24.747 ms
11 192.175.30.252 (192.175.30.252) 31.421 ms 31.193 ms 18.703 ms
12 192.175.29.226 (192.175.29.226) 22.733 ms 23.648 ms 34.473 ms
13 * * *
14 * be1.cr3-55smarket.bb.as11404.net (192.175.30.71) 41.486 ms *
15 be10.cr4-11greatoaks.bb.as11404.net (192.175.30.33) 53.163 ms 53.032 ms be12.cr4-11greatoaks.bb.as11404.net (192.1
75.30.222) 58.264 ms
16 209.85.168.110 (209.85.168.110) 63.560 ms 65.563 ms 75.345 ms
17 108.170.243.1 (108.170.243.1) 50.761 ms 209.85.142.239 (209.85.142.239) 44.341 ms 49.893 ms
18 108.170.242.237 (108.170.242.237) 48.857 ms 48.729 ms 108.170.242.254 (108.170.242.254) 48.565 ms
19 74.125.253.151 (74.125.253.151) 48.439 ms 74.125.253.149 (74.125.253.149) 48.146 ms 142.250.234.139 (142.250.234.1
39) 47.777 ms
20 142.250.237.174 (142.250.237.174) 54.128 ms 142.250.233.118 (142.250.233.118) 56.247 ms 142.250.237.176 (142.250.2
37.176) 56.025 ms
21 142.250.235.182 (142.250.235.182) 97.561 ms * 100.516 ms
22 * 209.85.245.86 (209.85.245.86) 95.398 ms 142.250.231.46 (142.250.231.46) 95.159 ms
23 142.250.232.104 (142.250.232.104) 95.141 ms 142.250.231.124 (142.250.231.124) 83.720 ms 142.250.232.22 (142.250.23
2.22) 83.259 ms
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
 

 

 

Edited by FifthPlayer
fix cut/paste job on fujinet.online
Link to comment
Share on other sites
tschak909 Quadrunner

tschak909

Posted
  • Author
Posted

The fact that it's not returning ANY directory entries at the server side is .... interesting, to say the least.

 

for contrast, here's my output:

  

19:58:41.833 > CF: 70 f9 02 00 6c
19:58:41.833 > sioFuji::sio_process() called
19:58:41.833 > ACK!
19:58:41.833 > Fuji cmd: MOUNT HOST
19:58:41.833 > ::mount {2} "fujinet.online"
19:58:41.833 > ::mount_local Attempting mount of "fujinet.online"       
19:58:41.834 > ::mount_tnfs {2:2} "fujinet.online"
19:58:41.835 > ::mount_tnfs Currently connected to host "fujinet.online"
19:58:41.835 > COMPLETE!
19:58:41.931 > 
19:58:41.932 > CF: 70 f7 02 00 6a
19:58:41.932 > sioFuji::sio_process() called
19:58:41.932 > ACK!
19:58:41.932 > Fuji cmd: OPEN DIRECTORY     
19:58:41.933 > <-SIO read 256 bytes
19:58:41.955 > ACK!
19:58:41.955 > Opening directory: "/", pattern: ""
19:58:41.955 > ::dir_open {2:2} "/", pattern ""
19:58:41.955 > ::dir_open actual path = "/"
19:58:41.955 > TNFS open directory: sortopts=0x00 diropts=0x00 maxresults=0x0000 pattern="" path="/"
19:58:42.040 > Directory opened, handle ID: 0, entries: 11
19:58:42.040 > COMPLETE!
19:58:42.044 >
19:58:42.044 > CF: 70 e4 00 00 55
19:58:42.044 > sioFuji::sio_process() called
19:58:42.044 > ACK!
19:58:42.044 > Fuji cmd: SET DIRECTORY POSITION
19:58:42.046 > ::dir_seek {2:2} 0
19:58:42.107 > COMPLETE!
19:58:42.112 >
19:58:42.113 > CF: 70 f6 24 00 8b
19:58:42.113 > sioFuji::sio_process() called
19:58:42.113 > ACK!
19:58:42.113 > Fuji cmd: READ DIRECTORY ENTRY (max=36)
19:58:42.114 > ::dir_nextfile {2:2}
19:58:42.217 > tnfs_readdirx resp_count=11, dirpos=0, status=1
19:58:42.218 > tnfs_readdirx cached 11 entries
19:58:42.218 >  _readdirx_fill_response: dir: Yes, size: 4096, mtime: 2020-07-28 19:29:48, ctime: 2020-12-08 15:58:31 "DOS"
19:58:42.219 > ::read_direntry "DOS"
19:58:42.221 > ->SIO write 36 bytes
19:58:42.221 > COMPLETE!
19:58:42.232 >
19:58:42.233 > CF: 70 f6 24 00 8b
19:58:42.233 > sioFuji::sio_process() called
19:58:42.233 > ACK!
19:58:42.233 > Fuji cmd: READ DIRECTORY ENTRY (max=36)
19:58:42.233 > ::dir_nextfile {2:2}
19:58:42.233 > tnfs_readdirx responding from cached entry
19:58:42.233 >  _readdirx_fill_response: dir: Yes, size: 4096, mtime: 2020-11-19 19:42:41, ctime: 2020-12-08 15:58:31 "games"
19:58:42.234 > ::read_direntry "games"
19:58:42.234 > ->SIO write 36 bytes
19:58:42.234 > COMPLETE!
19:58:42.248 >
19:58:42.249 > CF: 70 f6 24 00 8b
19:58:42.249 > sioFuji::sio_process() called
19:58:42.249 > ACK!
19:58:42.249 > Fuji cmd: READ DIRECTORY ENTRY (max=36)
19:58:42.249 > ::dir_nextfile {2:2}
19:58:42.249 > tnfs_readdirx responding from cached entry
19:58:42.250 >  _readdirx_fill_response: dir: Yes, size: 4096, mtime: 2020-08-31 20:05:56, ctime: 2020-12-08 15:58:31 "Holmes_CD1"
19:58:42.251 > ::read_direntry "Holmes_CD1"
19:58:42.251 > ->SIO write 36 bytes
19:58:42.253 > COMPLETE!
19:58:42.268 >
19:58:42.292 > CF: 70 f6 24 00 8b
19:58:42.292 > sioFuji::sio_process() called
19:58:42.292 > ACK!
19:58:42.292 > Fuji cmd: READ DIRECTORY ENTRY (max=36)
19:58:42.292 > ::dir_nextfile {2:2}
19:58:42.292 > tnfs_readdirx responding from cached entry
19:58:42.292 >  _readdirx_fill_response: dir: Yes, size: 4096, mtime: 2020-12-08 15:57:56, ctime: 2020-12-08 15:58:31 "netgames"  
19:58:42.292 > ::read_direntry "netgames"
19:58:42.292 > ->SIO write 36 bytes
19:58:42.292 > COMPLETE!
19:58:42.292 >
19:58:42.292 > CF: 70 f6 24 00 8b
19:58:42.292 > sioFuji::sio_process() called
19:58:42.292 > ACK!
19:58:42.292 > Fuji cmd: READ DIRECTORY ENTRY (max=36)
19:58:42.292 > ::dir_nextfile {2:2}
19:58:42.292 > tnfs_readdirx responding from cached entry
19:58:42.292 >  _readdirx_fill_response: dir: Yes, size: 4096, mtime: 2020-12-16 10:48:15, ctime: 2020-12-16 10:48:15 "networking"
19:58:42.292 > ::read_direntry "networking"
19:58:42.292 > ->SIO write 36 bytes
19:58:42.292 > COMPLETE!
19:58:42.306 >
19:58:42.306 > CF: 70 f6 24 00 8b
19:58:42.306 > sioFuji::sio_process() called
19:58:42.306 > ACK!
19:58:42.306 > Fuji cmd: READ DIRECTORY ENTRY (max=36)
19:58:42.308 > ::dir_nextfile {2:2}
19:58:42.308 > tnfs_readdirx responding from cached entry
19:58:42.308 >  _readdirx_fill_response: dir: Yes, size: 4096, mtime: 2020-11-24 18:20:51, ctime: 2020-12-08 15:58:31 "printing"
19:58:42.309 > ::read_direntry "printing"
19:58:42.309 > ->SIO write 36 bytes
19:58:42.310 > COMPLETE!
19:58:42.324 >
19:58:42.327 > CF: 70 f6 24 00 8b
19:58:42.327 > sioFuji::sio_process() called
19:58:42.327 > ACK!
19:58:42.327 > Fuji cmd: READ DIRECTORY ENTRY (max=36)
19:58:42.327 > ::dir_nextfile {2:2}
19:58:42.327 > tnfs_readdirx responding from cached entry
19:58:42.327 >  _readdirx_fill_response: dir: Yes, size: 4096, mtime: 2020-10-24 19:48:54, ctime: 2020-12-08 15:58:31 "tools"
19:58:42.327 > ::read_direntry "tools"
19:58:42.327 > ->SIO write 36 bytes
19:58:42.327 > COMPLETE!
19:58:42.340 >
19:58:42.341 > CF: 70 f6 24 00 8b
19:58:42.341 > sioFuji::sio_process() called
19:58:42.341 > ACK!
19:58:42.341 > Fuji cmd: READ DIRECTORY ENTRY (max=36)
19:58:42.341 > ::dir_nextfile {2:2}
19:58:42.341 > tnfs_readdirx responding from cached entry
19:58:42.341 >  _readdirx_fill_response: dir: no, size: 92176, mtime: 2020-10-21 16:12:45, ctime: 2020-12-08 15:58:31 "config.atr"
19:58:42.343 > ::read_direntry "config.atr"
19:58:42.343 > ->SIO write 36 bytes
19:58:42.344 > COMPLETE!
19:58:42.358 >
19:58:42.359 > CF: 70 f6 24 00 8b
19:58:42.359 > sioFuji::sio_process() called
19:58:42.359 > ACK!
19:58:42.359 > Fuji cmd: READ DIRECTORY ENTRY (max=36)
19:58:42.359 > ::dir_nextfile {2:2}
19:58:42.359 > tnfs_readdirx responding from cached entry
19:58:42.360 >  _readdirx_fill_response: dir: no, size: 92176, mtime: 2020-11-13 20:43:44, ctime: 2020-12-08 15:58:31 "fnc-tools.atr"
19:58:42.361 > ::read_direntry "fnc-tools.atr"
19:58:42.361 > ->SIO write 36 bytes
19:58:42.363 > COMPLETE!
19:58:42.380 > 
19:58:42.402 > CF: 70 f6 24 00 8b
19:58:42.402 > sioFuji::sio_process() called
19:58:42.402 > ACK!
19:58:42.402 > Fuji cmd: READ DIRECTORY ENTRY (max=36)
19:58:42.402 > ::dir_nextfile {2:2}
19:58:42.402 > tnfs_readdirx responding from cached entry
19:58:42.402 >  _readdirx_fill_response: dir: no, size: 42535, mtime: 2020-07-28 19:31:28, ctime: 2020-12-08 15:58:31 "index.php"
19:58:42.402 > ::read_direntry "index.php"
19:58:42.402 > ->SIO write 36 bytes
19:58:42.402 > COMPLETE!
19:58:42.402 >
19:58:42.402 > CF: 70 f6 24 00 8b
19:58:42.402 > sioFuji::sio_process() called
19:58:42.402 > ACK!
19:58:42.402 > Fuji cmd: READ DIRECTORY ENTRY (max=36)
19:58:42.402 > ::dir_nextfile {2:2}
19:58:42.402 > tnfs_readdirx responding from cached entry
19:58:42.402 >  _readdirx_fill_response: dir: no, size: 133136, mtime: 2020-09-25 17:30:00, ctime: 2020-12-08 15:58:31 "SAM-Test.atr"
19:58:42.402 > ::read_direntry "SAM-Test.atr"
19:58:42.402 > ->SIO write 36 bytes
19:58:42.503 > COMPLETE!
19:58:42.503 >
19:58:42.503 > CF: 70 f6 24 00 8b
19:58:42.503 > sioFuji::sio_process() called
19:58:42.503 > ACK!
19:58:42.503 > Fuji cmd: READ DIRECTORY ENTRY (max=36)
19:58:42.503 > ::dir_nextfile {2:2}
19:58:42.503 > tnfs_readdirx returning EOF based on cached value
19:58:42.503 > Reached end of of directory
19:58:42.503 > ->SIO write 36 bytes
19:58:42.503 > COMPLETE!
19:58:42.503 >
19:58:42.503 > CF: 70 f5 02 00 68
19:58:42.503 > sioFuji::sio_process() called
19:58:42.503 > ACK!
19:58:42.503 > Fuji cmd: CLOSE DIRECTORY
19:58:42.503 > COMPLETE!

 

-Thom

Link to comment
Share on other sites
MrFSL Moonsweeper

MrFSL

Posted
Posted

I have found a continuous ping to the fujinet is a helpful tool. I sit right next to my wifi router (less than 10 feet away too) and didn't realize I was having wifi issues.

 

I should start a thread asking folks to report their latency on pings. It would be good to know what "normal" looks like. For me with the device getting external power and away from any interference I still see latency averaging around 300ms which is pretty awful. All other devices on the network average 6.

 

Since I discovered a device creating noise and interfering my fujinet now works pretty darn well. It was seeing ping drops and latency at 1200 ms that helped me understand what was going on.

Link to comment
Share on other sites
FifthPlayer Dragonstomper

FifthPlayer

Posted
Posted
1 hour ago, mozzwald said:

I've restarted the fujinet.online tnfs server if you wanna try it again just in case it's an issue there.

Thank you, the situation has improved (browsing is working ok) but I still get the occasional glitch when trying to boot off a disk image.

 

I have also noticed throughput when booting off a network image is significant slower than booting the inbuilt config app, and the data seems to come in chunks with a pause in between each.  I would have expected SIO to be the bottleneck (plain old SIO, no high-speed mods) so maybe I do have wifi issues such as interference.  I'll experiment some more and see what I can discover.

 

Link to comment
Share on other sites
FifthPlayer Dragonstomper

FifthPlayer

Posted
Posted (edited)
23 hours ago, MrFSL said:

I have found a continuous ping to the fujinet is a helpful tool. I sit right next to my wifi router (less than 10 feet away too) and didn't realize I was having wifi issues.

 

I should start a thread asking folks to report their latency on pings. It would be good to know what "normal" looks like. For me with the device getting external power and away from any interference I still see latency averaging around 300ms which is pretty awful. All other devices on the network average 6.

 

Since I discovered a device creating noise and interfering my fujinet now works pretty darn well. It was seeing ping drops and latency at 1200 ms that helped me understand what was going on.

 

I've connected my Fujinet to an external USB power supply and I've also disconnected the wireless keyboard dongle from my RPi that I know from experience can cause interference issues with other equipment.  So far, accessing remote sites is working well, knock on wood.

 

Thank you for the continuous ping suggestion.  Here are some ping statistics I'm getting for my Fujinet.  It seems like 300ms latency might be close to "normal":

Ping statistics for 192.168.1.33:
Packets: Sent = 146, Received = 146, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 453ms, Average = 229ms

Edited by FifthPlayer
cut/paste again
  • Thanks 1
Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
AtariAge
Forums
Store
General
Follow AtariAge

Copyright ©1998-2023 AtariAge

×
×
  • Create New...