mozzwald

I do have a 400 and pulled it out last night. It did reset when hot plugging fujinet. I'm not sure what the SIO hardware differences are b/w the release machines and the later. Will have to investigate. I guess you'll just have to live without hotplugging on the 400/800 unless something gets figured out in the future. I will make a build for you to test. To sd card or network?

It's a little more involved than that, see the post below

Have not heard of this issue until now and I do not have an 800 to test with. I went to go add an issue on github for it and there's one already there https://github.com/FujiNetWIFI/fujinet-platformio/issues/378 I'm not sure what it would take to make this a configurable option. I have enough parts on hand to build 2 external antenna fujinets. If you're interested, pm me and we can figure something out. Are you able to build the firmware if I provide some changes or do you need me to provide custom firmware files to be applied with fujinet-flasher? Instructions for building firmware are at https://github.com/FujiNetWIFI/fujinet-platformio/wiki/pio-6-x-howto

@XL Freak SD and SDHC are known to work. I've used up to a 32GB Sandisk card (don't recall what class). Others have tried the same Sandisk size but the card would not work. I suspect there is inconsistency with the cards and their internal controller. We've always recommended the lower capacity cards (2-4GB) but those are harder to come by these days. There is a brief section in the wiki quick start guide about the sd card.

Maybe inrush current to Fujinet causing brown out on the 800? Not sure. While I've done hot plugging on my 800XL without issue, it's not really recommended. We can try to see if changing the pinmode for Fujinet audio out when not in use makes a difference. IIRC, the 400/800 only supported 2 printers and Fujinet SAM uses printer 4. Maybe there's another way it could be implemented? A new SAM device with commands? I can't remember why those don't work on 800. Maybe @bocianu can explain There is the option to build Fujinet with external antenna which I did in the past, but it was not very popular so I stopped making them. I could bring that option back and do those custom builds. It's more work and more parts which = higher cost, but if there's interest I will make them.

@Teleprompter @chad5200 I've added a 10 ring timeout to the code. Tested locally with telnet and works fine. Is this something that needs to be configurable or is 10 rings a good fit for most situations? Right now it's hard coded. Test build firmware is available on my personal fork of FujiNet code https://github.com/mozzwald/fujinet-platformio/releases/download/v1.0-pre6/fujinet-ATARI-v1.0-pre6.zip and can be installed with the FujiNet-Flasher following the instructions on the wiki https://github.com/FujiNetWIFI/fujinet-platformio/wiki/FujiNet-Flasher#flashing-a-custom-firmware-file

Directly from modem.h, how about these changes? Feel free to edit the text below and reply with any suggestions. /* Keep strings under 40 characters, for the benefit of 40-column users! */ #define HELPL01 " FujiNet Virtual Modem 850" #define HELPL02 "=======================================" #define HELPL03 "" #define HELPL04 "ATWIFILIST | List avail networks" #define HELPL05 "ATWIFICONNECT<ssid>,<key> Set up WiFi" #define HELPL06 "ATH | Hangup" #define HELPL07 "ATDT<host>:<port> | Connect by TCP" #define HELPL08 "ATIP | See my IP address" #define HELPL09 "ATNET<0|1> | Dis/enable TELNET" #define HELPL10 " | command handling" #define HELPL11 "ATPORT<port> | Set listening port" #define HELPL12 "ATE<0|1> | Echo OFF/ON" #define HELPL13 "AT | Returns OK" #define HELPL14 "ATGET<URL> | HTTP GET" #define HELPL15 "AT+TERM=<termtype>| Set telnet term" #define HELPL16 " | type (DUMB, VT52," #define HELPL17 " | VT100, ANSI)" #define HELPL18 "AT[+or-]SNIFF | Dis/enable sniffer" #define HELPL19 "ATA | Answer/ANSWER Mode" #define HELPL20 "ATO | Answer/Originate" #define HELPL21 "ATS0=<0|1> | AutoAnswer on/off" #define HELPL22 "ATTERMANSI | Set TERM to ANSI" #define HELPL23 "ATCPM | Go into CP/M" #define HELPL24 "ATPBLIST | List Phonebook" #define HELPL25 "ATPBCLEAR | Clear Phonebook" #define HELPL26 "ATPB<num>=<host> | Add to Phonebook" #define HELPPORT1 "Listening to connections on port " #define HELPPORT2 "which result in RING that you can" #define HELPPORT3 "answer with ATA." #define HELPPORT4 "No incoming connections are enabled."

There is no "install", it's just a program that is run from terminal. Put the downloaded program somewhere (I'll assume it's in Downloads for this example): cd ~/Downloads chmod 755 tnfsd.macos.amd64 ./tnfsd.macos.amd64 /path/to/your/atari/disk/images Macos may prompt you about the program being from the internet and you may need to approve it/allow it to run in settings. You may also need to allow tnfsd to use the firewall port 16384.

There is some limited info on the wiki about c64 fujinet hardware https://github.com/FujiNetWIFI/fujinet-platformio/wiki/Commodore-FujiNet-Quickstart-Guide

@x=usr(1536) think what needs to happen is to switch over to the "new" tnfsd repo (https://github.com/FujiNetWIFI/tnfsd). This is the repo created by the upstream spectranet project. I forked it to FujiNet so I could push the last bug fix upstream but did not have time to compare the code with our older "spectranet" named repo. If we can verify all our FujiNet updates are already in the new repo (and push any upstream that are needed) you could use that for Homebrew. edit: it would also be nice for github actions to build the binaries when pushing a release, or someone would need to manually create the release

The MacOS tnfsd binary never got updated on github and is old. I've put the latest version at https://fujinet.online/download if you want to try it

I wouldn't suspect that just yet. When FujiNet is not associated to wifi, it will flash all the lights when turned on and the lights turn off. The white LED will only turn on when connected to wifi. Holding button A when turning it on puts the Fujinet into flashing mode where it's ready to install new firmware which is not what you want. After turning on the Fujinet, press button A and you should see the blue LED blink a couple times indicating a disk rotation was initiated. I can't really help with the incognito/u1mb stuff since I don't own one and never used one. can you just disable SDX and boot it like a normal atari and config would probably boot.

I'm not exactly sure what you mean here. can you please clarify? I could not replicate either of these issues

This issue was fixes some time ago. Some major changes were introduced last month to enable building with newer esp-idf and seem to have broken that fix. Will investigate. This is a known issue. CONFIG was rewritten to be cross platform and this feature was not implemented in the newer code. will take a look Thanks for reporting

This is something that needs changed in the auto build. Will be fixed for the next release

@_The Doctor__ The error you reported Unexpected error: could not open port 'COM3': PermissionError(13, 'Access is denied.', None, 5) means something has the port open or you don't have permission to access the port. Probably not related to the USB port or cable.

Running it as administrator? Something else on the system taking control of the serial port? Maybe reboot and run the flasher first thing

fixed. sorry about that

A new firmware update is available from https://fujinet.online/download "version": "v1.0-pre4", "version_date": "2023-05-01 00:40:20", "build_date": "2023-05-04 19:13:07", "description": "FujiNet v1.0 Prelease 4", "git_commit": "b9957c2e", Notable Notions: Long standing TNFS Packet out of order sequence errors fixed Config copy file has better checking if an error occurred and remove destination file if error I'm tagging this a v1.0 pre-release. It is using a newer Espressif platform version and has been tested by a small number of people with no new problems. Going forward, I hope to have the automated github builds working completely and we will probably use semantic versioning. Please do not respond to this thread. If you have an issue, start a new post in the FujiNet subforum, open an issue on the github tracker or ask for assistance in Discord chat.

Thanks for testing and confirming it works. This has been a long standing issue and I'm glad it's fixed. This will be pushed to the flasher after some other things are fixed/changed and more testing is done. I'm working on having github build the firmware automatically and will be starting that with a v1.0 build. No more git hash for version numbers which should make it easier to see if you need an upgrade.

Everything looks fine to me v1.7 replaced the MicroUSB with USB-C and added a bulk capacitor to SIO 5V, no super caps here. The extra capacitor was added for the rare occasion when the Atari would have graphical glitching when FujiNet was bus powered only, probably due to Atari not supplying enough power through the SIO port. I think I've heard of 3 people having the issue. Powering the Fuji from USB or adding a capacitor eliminated the issue.

Correct, just select the ZIP file and hit the Flash FujiNet Firmware button

Fujinet will work anywhere in the chain

Thanks for testing @rietveld! Here's a new build with the graphical glitch in config fixed. fujinet-ADAM-v1.0-pre2.zip

Attached below is a new firmware for the Coleco ADAM FujiNet. This is a testing firmware that uses the latest espressif platform which is a major upgrade. I am requesting testers to go through and see if there are any issues before we push it as a regular release. Another notable change is a bug fix to the TNFS code where the packet order sequence would be incorrect if a packet timed out. The firmware can be installed with the latest FujiNet-Flasher from https://fujinet.online/download and using the "Custom Firmware File" option. If anyone can test and report issues (or no issues) it would be much appreciated. fujinet-ADAM-0.5.1b7ccf31-BETA.zip