Jump to content
tschak909

#FujiNet Testing and Bug Reporting Thread

Recommended Posts

That is not true. It is also displayed in this way even if the B key on the Fujinet has not been pressed. See my debug. I bought the hardware ready. Version 1.3 Fujinet.

Share this post


Link to post
Share on other sites
11 minutes ago, Pmetzen said:

That is not true. It is also displayed in this way even if the B key on the Fujinet has not been pressed. See my debug. I bought the hardware ready. Version 1.3 Fujinet.

Sounds like you have a hardware problem then. The button should not press itself :) Contact your vendor about repair or replacement

Share this post


Link to post
Share on other sites

Whether this is a hardware problem, I dare to doubt. This is because the error only occurs when a file is not read in and it takes too long and timeouts occur. Then comes the Heinweis with the B button.

Share this post


Link to post
Share on other sites

It seems to be more of a TNFS server problem for some. Because copying the files works well on my own TNFS server. Many TNFS servers are somewhere, far away.

Share this post


Link to post
Share on other sites
32 minutes ago, Pmetzen said:

Whether this is a hardware problem, I dare to doubt. This is because the error only occurs when a file is not read in and it takes too long and timeouts occur. Then comes the Heinweis with the B button.

The button has a pull up resistor to 3.3V and when the button is pressed it is connected to GND. The firmware checks if the button is connected to GND. It should only show this message if you have pressed the button. I don't see how the TNFS timeout can cause the button to be detected as pressed. I have had plenty of TNFS timeouts and never seen this happen which leads me to believe there is a hardware problem. Try powering the FujiNet from USB while testing the TNFS copy and see if that helps any.

  • Like 1

Share this post


Link to post
Share on other sites

But that's the way it is with me. Whenever TNFS timeout problems arise, that's the case. I tested it myself on my own TNFS server , which can be reached via Dyndns. There is no timeout problem. There is no problem there.

I have already supplied the Fujinet with electricity in order to log this done. You can see in the Dubug exactly that after several timeouts this hint comes. I didn't press a B button. Strange.

  • Like 1

Share this post


Link to post
Share on other sites

Take a close look at the debug. Here's another excerpt from the debug. No B key is pressed. Several timeouts occur and access to the Fujinet after message "Fujinet is still copying the file is no longer possible. Only after a reset Fujinet goes again. The activity lamp lights up permanently. Error Reading Host Slots. I had to restart Fujinet. Then everything goes again. But in the Dubug you can definitely see BUTTON_B: SHORT PRESS
[22:41:36] ACTION: Send debug_tape message to SIO queue.. There it is only indicated that I should press the b key briefly. As long as I do not restart the Fujinet, the debug runs through the infinite loop and logs, logs. However, Fujinet is no longer accessible.

Share this post


Link to post
Share on other sites

Here is the Minutes

 

 

Using 'COM4' as serial port.
Showing logs:
[22:27:45]
[22:27:45]CF: 70 f7 00 00 68
[22:27:45]sioFuji::sio_process() called
[22:27:45]ACK!
[22:27:45]Fuji cmd: OPEN DIRECTORY
[22:27:45]<-SIO read 256 bytes
[22:27:45]ACK!
[22:27:45]Opening directory: "/Tools/Fujinet", pattern: ""
[22:27:45]::dir_open {0:1} "/Tools/Fujinet", pattern ""
[22:27:45]::dir_open actual path = "/Tools/Fujinet"
[22:27:45]COMPLETE!
[22:27:45]
[22:27:45]CF: 70 e4 00 00 55
[22:27:45]sioFuji::sio_process() called
[22:27:45]ACK!
[22:27:45]Fuji cmd: SET DIRECTORY POSITION
[22:27:45]::dir_seek {0:1} 0
[22:27:45]COMPLETE!
[22:27:45]
[22:27:45]CF: 70 f6 80 00 e7
[22:27:45]sioFuji::sio_process() called
[22:27:45]ACK!
[22:27:45]Fuji cmd: READ DIRECTORY ENTRY (max=128)
[22:27:45]::dir_nextfile {0:1}
[22:27:45]::read_direntry "config.atr"
[22:27:45]->SIO write 128 bytes
[22:27:45]COMPLETE!
[22:27:46]
[22:27:46]CF: 70 f5 00 00 66
[22:27:46]sioFuji::sio_process() called
[22:27:46]ACK!
[22:27:46]Fuji cmd: CLOSE DIRECTORY
[22:27:46]COMPLETE!
[22:27:46]
[22:27:46]CF: 70 d8 03 01 4d
[22:27:46]sioFuji::sio_process() called
[22:27:46]ACK!
[22:27:46]<-SIO read 256 bytes
[22:27:46]ACK!
[22:27:46]copySpec: /fnc-tools.atr|/Tools/Fujinet/
[22:27:46]append source file
[22:27:46]::mount {2} "atari-apps.irata.online"
[22:27:46]::mount_local Attempting mount of "atari-apps.irata.online"
[22:27:46]::mount_tnfs {2:2} "atari-apps.irata.online"
[22:27:46]::mount_tnfs Currently connected to host "atari-apps.irata.online"
[22:27:46]::mount {0} "SD"
[22:27:46]::mount_local Attempting mount of "SD"
[22:27:46]Type is already LOCAL
[22:27:46]fujiHost #2 opening file path "/fnc-tools.atr"
[22:27:46]TNFS open file: "/fnc-tools.atr" (0x0001, 0x01b6)
[22:27:46]File opened, handle ID: 0, size: 92176, pos: 0
[22:27:46]fujiHost #0 opening file path "/Tools/Fujinet/fnc-tools.atr"
[22:27:48]Timeout after 2000 milliseconds. Retrying
[22:28:06]Timeout after 2000 milliseconds. Retrying
[22:28:16]Timeout after 2000 milliseconds. Retrying
[22:28:19]Timeout after 2000 milliseconds. Retrying
[22:28:22]Timeout after 2000 milliseconds. Retrying
[22:28:26]Timeout after 2000 milliseconds. Retrying
[22:28:35]Timeout after 2000 milliseconds. Retrying
[22:28:38]Timeout after 2000 milliseconds. Retrying
[22:28:49]Timeout after 2000 milliseconds. Retrying
[22:28:55]Timeout after 2000 milliseconds. Retrying
[22:29:07]Timeout after 2000 milliseconds. Retrying
[22:29:18]Timeout after 2000 milliseconds. Retrying
[22:29:22]Timeout after 2000 milliseconds. Retrying
[22:29:34]Timeout after 2000 milliseconds. Retrying
[22:29:42]Timeout after 2000 milliseconds. Retrying
[22:29:52]Timeout after 2000 milliseconds. Retrying
[22:29:56]Timeout after 2000 milliseconds. Retrying
[22:30:09]Timeout after 2000 milliseconds. Retrying
[22:30:13]Timeout after 2000 milliseconds. Retrying
[22:30:19]Timeout after 2000 milliseconds. Retrying
[22:30:24]Timeout after 2000 milliseconds. Retrying
[22:30:33]Timeout after 2000 milliseconds. Retrying
[22:30:39]Timeout after 2000 milliseconds. Retrying
[22:30:42]Timeout after 2000 milliseconds. Retrying
[22:30:47]Timeout after 2000 milliseconds. Retrying
[22:30:56]Timeout after 2000 milliseconds. Retrying
[22:31:01]Timeout after 2000 milliseconds. Retrying
[22:31:05]Timeout after 2000 milliseconds. Retrying
[22:31:11]Timeout after 2000 milliseconds. Retrying
[22:31:16]Timeout after 2000 milliseconds. Retrying
[22:31:19]Timeout after 2000 milliseconds. Retrying
[22:31:27]Timeout after 2000 milliseconds. Retrying
[22:31:30]Timeout after 2000 milliseconds. Retrying
[22:31:36]Timeout after 2000 milliseconds. Retrying
[22:31:39]Timeout after 2000 milliseconds. Retrying
[22:31:49]Timeout after 2000 milliseconds. Retrying
[22:31:56]Timeout after 2000 milliseconds. Retrying
[22:32:01]Timeout after 2000 milliseconds. Retrying
[22:32:10]Timeout after 2000 milliseconds. Retrying
[22:32:13]Timeout after 2000 milliseconds. Retrying
[22:32:19]Timeout after 2000 milliseconds. Retrying
[22:32:23]Timeout after 2000 milliseconds. Retrying
[22:32:27]Timeout after 2000 milliseconds. Retrying
[22:32:34]Timeout after 2000 milliseconds. Retrying
[22:32:38]Timeout after 2000 milliseconds. Retrying
[22:32:43]Timeout after 2000 milliseconds. Retrying
[22:32:47]Timeout after 2000 milliseconds. Retrying
[22:32:52]Timeout after 2000 milliseconds. Retrying
[22:32:58]Timeout after 2000 milliseconds. Retrying
[22:33:04]Timeout after 2000 milliseconds. Retrying
[22:33:07]Timeout after 2000 milliseconds. Retrying
[22:33:19]Timeout after 2000 milliseconds. Retrying
[22:33:23]Timeout after 2000 milliseconds. Retrying
[22:33:31]Timeout after 2000 milliseconds. Retrying
[22:33:53]Timeout after 2000 milliseconds. Retrying
[22:33:58]Timeout after 2000 milliseconds. Retrying
[22:34:11]Timeout after 2000 milliseconds. Retrying
[22:34:14]Timeout after 2000 milliseconds. Retrying
[22:34:18]Timeout after 2000 milliseconds. Retrying
[22:34:23]Timeout after 2000 milliseconds. Retrying
[22:34:28]Timeout after 2000 milliseconds. Retrying
[22:34:33]Timeout after 2000 milliseconds. Retrying
[22:34:43]Timeout after 2000 milliseconds. Retrying
[22:34:56]Timeout after 2000 milliseconds. Retrying
[22:35:00]Timeout after 2000 milliseconds. Retrying
[22:35:19]Timeout after 2000 milliseconds. Retrying
[22:35:23]Timeout after 2000 milliseconds. Retrying
[22:35:30]Timeout after 2000 milliseconds. Retrying
[22:35:34]Timeout after 2000 milliseconds. Retrying
[22:35:37]Timeout after 2000 milliseconds. Retrying
[22:35:42]Timeout after 2000 milliseconds. Retrying
[22:35:48]Timeout after 2000 milliseconds. Retrying
[22:35:51]Timeout after 2000 milliseconds. Retrying
[22:35:56]Timeout after 2000 milliseconds. Retrying
[22:36:02]Timeout after 2000 milliseconds. Retrying
[22:36:27]Timeout after 2000 milliseconds. Retrying
[22:36:35]Timeout after 2000 milliseconds. Retrying
[22:36:43]Timeout after 2000 milliseconds. Retrying
[22:36:48]Timeout after 2000 milliseconds. Retrying
[22:36:59]Timeout after 2000 milliseconds. Retrying
[22:37:11]Timeout after 2000 milliseconds. Retrying
[22:37:18]Timeout after 2000 milliseconds. Retrying
[22:37:21]Timeout after 2000 milliseconds. Retrying
[22:37:25]Timeout after 2000 milliseconds. Retrying
[22:37:42]Timeout after 2000 milliseconds. Retrying
[22:37:47]Timeout after 2000 milliseconds. Retrying
[22:37:54]Timeout after 2000 milliseconds. Retrying
[22:38:08]Timeout after 2000 milliseconds. Retrying
[22:38:11]Timeout after 2000 milliseconds. Retrying
[22:38:15]Timeout after 2000 milliseconds. Retrying
[22:38:20]Timeout after 2000 milliseconds. Retrying
[22:38:25]Timeout after 2000 milliseconds. Retrying
[22:38:38]Timeout after 2000 milliseconds. Retrying
[22:38:42]Timeout after 2000 milliseconds. Retrying
[22:38:49]Timeout after 2000 milliseconds. Retrying
[22:38:54]Timeout after 2000 milliseconds. Retrying
[22:39:00]Timeout after 2000 milliseconds. Retrying
[22:39:05]Timeout after 2000 milliseconds. Retrying
[22:39:15]Timeout after 2000 milliseconds. Retrying
[22:39:27]Timeout after 2000 milliseconds. Retrying
[22:39:46]Timeout after 2000 milliseconds. Retrying
[22:39:51]Timeout after 2000 milliseconds. Retrying
[22:39:56]Timeout after 2000 milliseconds. Retrying
[22:40:05]Timeout after 2000 milliseconds. Retrying
[22:40:13]Timeout after 2000 milliseconds. Retrying
[22:40:29]Timeout after 2000 milliseconds. Retrying
[22:40:38]Timeout after 2000 milliseconds. Retrying
[22:40:50]Timeout after 2000 milliseconds. Retrying
[22:40:54]Timeout after 2000 milliseconds. Retrying
[22:41:03]Timeout after 2000 milliseconds. Retrying
[22:41:17]Timeout after 2000 milliseconds. Retrying
[22:41:36]BUTTON_B: SHORT PRESS
[22:41:36]ACTION: Send debug_tape message to SIO queue
[22:41:43]Timeout after 2000 milliseconds. Retrying
[22:41:47]Timeout after 2000 milliseconds. Retrying
[22:41:53]Timeout after 2000 milliseconds. Retrying
[22:41:58]Timeout after 2000 milliseconds. Retrying
[22:42:02]Timeout after 2000 milliseconds. Retrying
[22:42:09]Timeout after 2000 milliseconds. Retrying
[22:42:16]Timeout after 2000 milliseconds. Retrying
[22:42:22]Timeout after 2000 milliseconds. Retrying
[22:42:43]Timeout after 2000 milliseconds. Retrying
[22:42:51]Timeout after 2000 milliseconds. Retrying
[22:42:55]Timeout after 2000 milliseconds. Retrying
[22:43:05]Timeout after 2000 milliseconds. Retrying
[22:43:10]Timeout after 2000 milliseconds. Retrying
[22:43:13]Timeout after 2000 milliseconds. Retrying
[22:43:27]Timeout after 2000 milliseconds. Retrying
[22:43:42]Timeout after 2000 milliseconds. Retrying
[22:43:45]Timeout after 2000 milliseconds. Retrying
[22:43:54]Timeout after 2000 milliseconds. Retrying
[22:43:59]Timeout after 2000 milliseconds. Retrying
[22:44:06]Timeout after 2000 milliseconds. Retrying
[22:44:09]Timeout after 2000 milliseconds. Retrying
[22:44:20]Timeout after 2000 milliseconds. Retrying
[22:44:35]Timeout after 2000 milliseconds. Retrying
[22:44:39]Timeout after 2000 milliseconds. Retrying
[22:44:46]Timeout after 2000 milliseconds. Retrying
[22:44:54]Timeout after 2000 milliseconds. Retrying
[22:45:08]Timeout after 2000 milliseconds. Retrying
[22:45:12]Timeout after 2000 milliseconds. Retrying
[22:45:16]Timeout after 2000 milliseconds. Retrying
[22:45:21]Timeout after 2000 milliseconds. Retrying
[22:45:25]Timeout after 2000 milliseconds. Retrying
[22:45:29]Timeout after 2000 milliseconds. Retrying
[22:45:32]Timeout after 2000 milliseconds. Retrying
[22:45:36]Timeout after 2000 milliseconds. Retrying
[22:45:42]Timeout after 2000 milliseconds. Retrying
[22:45:48]Timeout after 2000 milliseconds. Retrying
[22:45:52]Timeout after 2000 milliseconds. Retrying
[22:45:58]Timeout after 2000 milliseconds. Retrying
[22:46:04]Timeout after 2000 milliseconds. Retrying
[22:46:08]Timeout after 2000 milliseconds. Retrying
[22:46:12]Timeout after 2000 milliseconds. Retrying
[22:46:18]Timeout after 2000 milliseconds. Retrying
[22:46:22]Timeout after 2000 milliseconds. Retrying
[22:46:28]Timeout after 2000 milliseconds. Retrying
[22:46:40]Timeout after 2000 milliseconds. Retrying
[22:46:54]Timeout after 2000 milliseconds. Retrying
[22:47:00]Timeout after 2000 milliseconds. Retrying
[22:47:05]Timeout after 2000 milliseconds. Retrying
[22:47:11]Timeout after 2000 milliseconds. Retrying
[22:47:23]Timeout after 2000 milliseconds. Retrying
[22:47:26]Timeout after 2000 milliseconds. Retrying
[22:47:36]Timeout after 2000 milliseconds. Retrying
[22:47:40]Timeout after 2000 milliseconds. Retrying
[22:47:45]Timeout after 2000 milliseconds. Retrying
[22:47:51]Timeout after 2000 milliseconds. Retrying
[22:47:55]Timeout after 2000 milliseconds. Retrying
[22:48:03]Timeout after 2000 milliseconds. Retrying
[22:48:18]Timeout after 2000 milliseconds. Retrying
[22:48:31]Timeout after 2000 milliseconds. Retrying
[22:48:43]Timeout after 2000 milliseconds. Retrying
[22:48:46]Timeout after 2000 milliseconds. Retrying
[22:48:51]Timeout after 2000 milliseconds. Retrying
[22:49:04]Timeout after 2000 milliseconds. Retrying
[22:49:26]BUTTON_B: SHORT PRESS
[22:49:26]ACTION: Send debug_tape message to SIO queue
[22:49:36]Timeout after 2000 milliseconds. Retrying
[22:49:44]Timeout after 2000 milliseconds. Retrying
[22:49:51]Timeout after 2000 milliseconds. Retrying
[22:50:06]Timeout after 2000 milliseconds. Retrying
[22:50:09]Timeout after 2000 milliseconds. Retrying
[22:50:18]Timeout after 2000 milliseconds. Retrying
[22:50:33]Timeout after 2000 milliseconds. Retrying
[22:50:38]Timeout after 2000 milliseconds. Retrying
[22:51:06]Timeout after 2000 milliseconds. Retrying
[22:51:19]Timeout after 2000 milliseconds. Retrying
[22:51:24]Timeout after 2000 milliseconds. Retrying
[22:51:28]Timeout after 2000 milliseconds. Retrying
[22:51:37]Timeout after 2000 milliseconds. Retrying
[22:51:49]BUTTON_B: SHORT PRESS
[22:51:49]ACTION: Send debug_tape message to SIO queue
[22:52:04]Timeout after 2000 milliseconds. Retrying
[22:52:10]Timeout after 2000 milliseconds. Retrying
[22:52:15]Timeout after 2000 milliseconds. Retrying
[22:52:23]Timeout after 2000 milliseconds. Retrying
[22:52:34]Timeout after 2000 milliseconds. Retrying
[22:52:37]Timeout after 2000 milliseconds. Retrying
[22:52:50]Timeout after 2000 milliseconds. Retrying
[22:53:11]Timeout after 2000 milliseconds. Retrying
[22:53:25]Timeout after 2000 milliseconds. Retrying
[22:53:41]Timeout after 2000 milliseconds. Retrying
[22:53:44]Timeout after 2000 milliseconds. Retrying
[22:53:51]Timeout after 2000 milliseconds. Retrying
[22:53:54]Timeout after 2000 milliseconds. Retrying
[22:53:59]Timeout after 2000 milliseconds. Retrying
[22:54:02]Timeout after 2000 milliseconds. Retrying
 

 

Share this post


Link to post
Share on other sites

So is the B button on the device damaged is the one question presented , and is the firmware also doing some shenanigans is the other question presented... maybe it's both.

 

As always update your firmware... it's always a good time to update...

Share this post


Link to post
Share on other sites

Once again I am having trouble with my FujiNet device.  It refuses to access the net.  Latest update is 3/15/2021

Here is the log error:

Unexpected error: could not open port 'COM38': PermissionError(13, 'Access is denied.', None, 5)
[18:29:55]WIFI_EVENT_STA_DISCONNECTED
[18:29:55]Stopping web service
[18:29:55]WiFi reconnect attempt 1 of 8
[18:29:55]WIFI_EVENT_STA_CONNECTED
[18:29:56]IP_EVENT_STA_GOT_IP
[18:29:56]Obtained IP address: 192.168.0.100
[18:29:56]Starting web server on port 80
[18:30:45]WIFI_EVENT_STA_DISCONNECTED
[18:30:45]Stopping web service
[18:30:45]WiFi reconnect attempt 1 of 8
[18:30:46]WIFI_EVENT_STA_CONNECTED
[18:30:46]IP_EVENT_STA_GOT_IP
[18:30:46]Obtained IP address: 192.168.0.100
[18:30:46]Starting web server on port 80
[18:31:14]WIFI_EVENT_STA_DISCONNECTED
[18:31:14]Stopping web service
[18:31:14]WiFi reconnect attempt 1 of 8
[18:31:14]WIFI_EVENT_STA_CONNECTED
[18:31:15]IP_EVENT_STA_GOT_IP
[18:31:15]Obtained IP address: 192.168.0.100
[18:31:15]Starting web server on port 80

 

IP address is wrong.  It should state: 192.168.254.17

Need I replace it again?!?

Share this post


Link to post
Share on other sites
7 minutes ago, FreddieBear said:

Once again I am having trouble with my FujiNet device.  It refuses to access the net.  Latest update is 3/15/2021

Here is the log error:

Unexpected error: could not open port 'COM38': PermissionError(13, 'Access is denied.', None, 5)
[18:29:55]WIFI_EVENT_STA_DISCONNECTED
[18:29:55]Stopping web service
[18:29:55]WiFi reconnect attempt 1 of 8
[18:29:55]WIFI_EVENT_STA_CONNECTED
[18:29:56]IP_EVENT_STA_GOT_IP
[18:29:56]Obtained IP address: 192.168.0.100
[18:29:56]Starting web server on port 80
[18:30:45]WIFI_EVENT_STA_DISCONNECTED
[18:30:45]Stopping web service
[18:30:45]WiFi reconnect attempt 1 of 8
[18:30:46]WIFI_EVENT_STA_CONNECTED
[18:30:46]IP_EVENT_STA_GOT_IP
[18:30:46]Obtained IP address: 192.168.0.100
[18:30:46]Starting web server on port 80
[18:31:14]WIFI_EVENT_STA_DISCONNECTED
[18:31:14]Stopping web service
[18:31:14]WiFi reconnect attempt 1 of 8
[18:31:14]WIFI_EVENT_STA_CONNECTED
[18:31:15]IP_EVENT_STA_GOT_IP
[18:31:15]Obtained IP address: 192.168.0.100
[18:31:15]Starting web server on port 80

 

IP address is wrong.  It should state: 192.168.254.17

Need I replace it again?!?

Looks like You're connecting to another access point?

-Thom

 

Share this post


Link to post
Share on other sites

Yes it does look that way yet I have no control of the FujiNet update.  Should I press RESET on FN while it's updating?

Latest debug scan:

Using 'COM38' as serial port.
Showing logs:
[18:51:54][18:51:54]
[18:51:54]--~--~--~--
[18:51:54]FujiNet 0.5.2656cf16 2021-03-19 17:56:48 Started @ 4
[18:51:54]Starting heap: 4056748
[18:51:54]PsramSize 3917592
[18:51:54]himem phys 4456448
[18:51:54]himem free 4456448
[18:51:54]himem reserved 262144
[18:51:54]Detected Hardware Version: 1.1-1.5
[18:51:54]Enabled Safe Reset Button C
[18:51:54]SPIFFS mounted.
[18:51:54]SD mounted.
[18:51:54]fnConfig::load
[18:51:54]Found copy of config file on SD - copying that to SPIFFS
[18:51:54]copy_file "/fnconfig.ini" -> "/fnconfig.ini"
[18:51:54]copy_file copied 757 bytes
[18:51:54]fnConfig::load read 757 bytes from config file
[18:51:54]WIFI_EVENT_STA_START
[18:51:54]WiFi connect attempt to SSID "Frontier7904"
[18:51:54]esp_wifi_connect returned 0
[18:51:54]disk UNMOUNT
[18:51:54]disk MOUNT
[18:51:54]ATR MOUNT
[18:51:54]mounted ATR: paragraphs=5760, sect_size=128, sect_count=720, disk_size=0
[18:51:54]Creating a default printer using FS_SDFAT storage and type 12
[18:51:54]SSH client initialized.
[18:51:54]ModemSniffer::ModemSniffer(FS_SDFAT)
[18:51:54]SIO SETUP
[18:51:54]Set HSIO baud from 0 to 67431 (index 6), alt=68209
[18:51:54]Available heap: 3892184
[18:51:54]Setup complete @ 532 (528ms)
[18:51:55]WIFI_EVENT_STA_CONNECTED
[18:51:56]IP_EVENT_STA_GOT_IP
[18:51:56]Obtained IP address: 192.168.0.100
[18:51:56]SNTP client start
[18:51:56]Starting web server on port 80
[18:52:02]WIFI_EVENT_STA_DISCONNECTED
[18:52:02]Stopping web service
[18:52:02]WiFi reconnect attempt 1 of 8
[18:52:03]WIFI_EVENT_STA_CONNECTED
[18:52:03]IP_EVENT_STA_GOT_IP
[18:52:03]Obtained IP address: 192.168.0.100
[18:52:03]Starting web server on port 80
[18:52:53]WIFI_EVENT_STA_DISCONNECTED
[18:52:53]Stopping web service
[18:52:53]WiFi reconnect attempt 1 of 8
[18:52:53]WIFI_EVENT_STA_CONNECTED
[18:52:53]IP_EVENT_STA_GOT_IP
[18:52:53]Obtained IP address: 192.168.0.100
[18:52:53]Starting web server on port 80
[18:53:13]WIFI_EVENT_STA_DISCONNECTED
[18:53:13]Stopping web service
[18:53:13]WiFi reconnect attempt 1 of 8
[18:53:13]WIFI_EVENT_STA_CONNECTED
[18:53:14]IP_EVENT_STA_GOT_IP
[18:53:14]Obtained IP address: 192.168.0.100
[18:53:14]Starting web server on port 80
[18:54:03]WIFI_EVENT_STA_DISCONNECTED
[18:54:03]Stopping web service
[18:54:03]WiFi reconnect attempt 1 of 8
[18:54:03]WIFI_EVENT_STA_CONNECTED
[18:54:04]IP_EVENT_STA_GOT_IP
[18:54:04]Obtained IP address: 192.168.0.100
[18:54:04]Starting web server on port 80

 

Share this post


Link to post
Share on other sites

if you look at the fnConfig.ini file that's on the SD card, it should mention which access point (and password) it is using to connect.

 

-Thom

 

Share this post


Link to post
Share on other sites
3 hours ago, tschak909 said:

Looks like You're connecting to another access point?

-Thom

 

That's just what I was going to suggest as well... Sounds like another network is configured with 192.168.0.0/24 instead of the 192.168.254.0/24 that is expected.

Share this post


Link to post
Share on other sites
13 hours ago, Calab said:

That's just what I was going to suggest as well... Sounds like another network is configured with 192.168.0.0/24 instead of the 192.168.254.0/24 that is expected.

Indeed but can I change the config.ini file from a word processor to fix this issue. It's a replacement FN from The Brewing Academy as they replaced my unfixable FujiNet recently. 

 

Share this post


Link to post
Share on other sites

I am unfamilar with the EXEC type of file fnconfig.ini.  I'd like to get into it and change the access numbers to reflect what I have.  Perhaps this is why I can't get onto the net.  Anyone here familar with this file type?

Share this post


Link to post
Share on other sites

It's just a text file that #FujiNet reads to get configuration, and can be edited with any text editor.

-Thom

 

Share this post


Link to post
Share on other sites
18 hours ago, tschak909 said:

if you look at the fnConfig.ini file that's on the SD card, it should mention which access point (and password) it is using to connect.

 

-Thom

 

Yes, how do I "look" at it? And how do I change it?

Share this post


Link to post
Share on other sites

open it with any text editor. e.g. Windows can edit the file by right clicking on the file and selecting Edit. Macintosh users can drag and drop it into TextEdit..

 

-Thom

 

Edited by tschak909

Share this post


Link to post
Share on other sites

Okay thank you Thom.  I've managed to view the file but can't see the network config part as in: 192.168.254.21  Is it just missing?

[General]
devicename=FujiNet
hsioindex=6
rotationsounds=1
configenabled=1
boot_mode=0
timezone=PST+8PDT


[WiFi]
SSID=Frontier7904
passphrase=3660347924

[Bluetooth]
devicename=FujiNetSIO2BT
enabled=0
baud=19200

[Network]
sntpserver=pool.ntp.org

[Host1]
type=SD
name=SD

[Host2]
type=TNFS
name=ATARI-APPS.IRATA.ONLINE

[Host3]
type=TNFS
name=fujinet.online

[Host4]
type=TNFS
name=FujiNet.us.to

[Host5]
type=SD
name=atari8.us

[Host6]
type=SD
name=fujinet.pl

[Host7]
type=TNFS
name=stguild-bbs.ddns.net

[Mount1]
hostslot=4
path=/Top-games/retrogamer.net top10/Yoomp ! (NTSC Version).xex
mode=r

[Printer1]
type=12
port=1

[Modem]
sniffer_enabled=0

[Cassette]
play_record=0 Play
pulldown=0 B Button Press

 

Share this post


Link to post
Share on other sites

The critical part is the SSID and passphrase, which should match your home network.

 

The IP address is dynamically assigned by your router.

 

-Thom

Share this post


Link to post
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.

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...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...