Page 11 of 11

Re: uip-tool

Posted: Mon May 04, 2020 5:18 pm
by Bikerbob
I am using a 220w psu on my pak68/3 build, it is 5.00V lots of power 23amp but just 5.00v. I will check the megaSTs and the megaSTE that does get the Netusbee working.. see what their 5v rail puts out.

James

Re: uip-tool

Posted: Mon May 04, 2020 6:52 pm
by sqward
susher wrote:. i.e. the cumulative propagation delay through the chips is just too high if the voltage is precisely 5V but sneaks in if slightly higher.
Any chance you could verify that by swapping the chips for LS versions?

Re: uip-tool

Posted: Mon May 04, 2020 9:23 pm
by agranlund
I gave up on the NetUsbee for my accelerated ST as well.
It works fine with the stock 68000 CPU, and it works with the 030 if I clock it with the 8Mhz clock.
Never got it to work when running it at 50 or 32 Mhz though. I suspected maybe it was just hyper sensitive to slight timing deviations but I found out about the ParCP-USB so never bothered investigating the NetUSBee issue any further.

Re: uip-tool

Posted: Tue May 05, 2020 7:59 am
by susher
sqward wrote:
susher wrote:. i.e. the cumulative propagation delay through the chips is just too high if the voltage is precisely 5V but sneaks in if slightly higher.
Any chance you could verify that by swapping the chips for LS versions?
I'm not sure you'd be able to get LS chips in SOIC packages and I wouldn't be confident in removing and replacing such small surface mount devices anyway.

Re: uip-tool

Posted: Wed May 06, 2020 3:26 pm
by Reylan
agranlund wrote:I gave up on the NetUsbee for my accelerated ST as well.
It works fine with the stock 68000 CPU, and it works with the 030 if I clock it with the 8Mhz clock.
Never got it to work when running it at 50 or 32 Mhz though. I suspected maybe it was just hyper sensitive to slight timing deviations but I found out about the ParCP-USB so never bothered investigating the NetUSBee issue any further.
What is paracp usb ? I search on Google with no luck...

Re: uip-tool

Posted: Wed May 06, 2020 3:48 pm
by saulot

Re: uip-tool

Posted: Wed May 06, 2020 3:58 pm
by sqward
Can I as the moderator to move all Netusbee "support" posts to a separate topic?

Re: uip-tool

Posted: Thu May 07, 2020 9:07 pm
by 8bitguy1
susher wrote: on my STE, it will work with the stock power supply but not with the Exxos power supply which has less noise and better voltage control. i.e. the hardware only just about works under the best of conditions.
Wished I'd have known that before I ordered the Exxos Power Supply for my STE. Has anyone else reported this issue?

Re: uip-tool

Posted: Thu May 07, 2020 11:57 pm
by neanderthal
sqward wrote:Can I as the moderator to move all Netusbee "support" posts to a separate topic?
Yeap,pop it into hardware or something since we are not talking 'Applications' anymore.

Re: uip-tool

Posted: Sat Oct 03, 2020 5:29 pm
by JuanPC2020
Can you improve it?
for example:
Add Network MIDI driver?
ipMIDI ?
rptMIDI ?

https://www.tobias-erichsen.de/software/rtpmidi.html
https://nerds.de/en/ipmidi.html
https://hackaday.io/project/156332-pedalino/log/153754-ipmidi

:contract:
:coffe:
sqward wrote: Thu Jan 01, 2015 5:25 pm Hello

Some time ago I've started working on a tool that would allow me to quickly upload files over ethernet (netusbee) to my Atari. This was mainly meant to speed up my development iteration but in the end I've decided to add web interface for the benefit of general public. It doesn't require Sting or MiNT. It's a self-contained binary with uIP embedded TCP/IP stack with DHCP. Run it on your Atari and point your PC browser to the IP address you'll see on the Atari screen. As far as I can tell it works on all TOS machines (tested on ST, TT, Falcon and CT60).

Image

It supports drag&drop of files from your PCs desktop.

It's largely unfinished. I'm hoping someone will help me get HTML part to the point it will be a genuinely useful tool.

Code and a binary can be found here:
git repo: https://bitbucket.org/sqward/uip-tools
binary: https://bitbucket.org/sqward/uip-tools/downloads/

Hope someone will find it useful.

uIPtool tutorial


Re: uip-tool

Posted: Sat Oct 03, 2020 5:52 pm
by sqward
I don't think so. MIDI software for ST has the habit of talking to the hardware directly so there's no way to make any apps work with rtpMidi out of the box. Also, I speculate that the overhead of packet oriented nature of Ethernet would make rtpMidi perform poorly on ST.

Re: uip-tool

Posted: Sun Nov 29, 2020 11:56 am
by lastic
First thanks for such an excellent tool ! Saves a lot of hassle looking/plugging/unplugging SD cards and/or USB-sticks.

Have you considered adding a TNFS client which has been used extensively on SpectraNet (ZX Spectrum) and recently on the 8-bit Atari's ?

https://fujinet.online/support/

The server side exists and can be run on PC/ARM/MacOS/Linux etc ...

Re: uip-tool

Posted: Sun Nov 29, 2020 12:02 pm
by sqward
It actually crossed my mind. I've read somewhere that TNFS uses UDP which would be ideal for uip. I'm not sure how this could work on ST. Maybe I'll play with it at some point. However, I have other priorities with uiptool, like adding remote debugger.

Thanks for you interest in my tool!

Re: uip-tool

Posted: Sun Nov 29, 2020 9:07 pm
by neanderthal
JuanPC2020 wrote: Sat Oct 03, 2020 5:29 pm Can you improve it?
for example:
Add Network MIDI driver?
ipMIDI ?
rptMIDI ?

https://www.tobias-erichsen.de/software/rtpmidi.html
https://nerds.de/en/ipmidi.html
https://hackaday.io/project/156332-peda ... 754-ipmidi
Those as far I can see is using networks(ethernet) and such for popping around midi messages over networks so would be a couple of problems.
First.
NetUSBee uses the standard ROM port of the ST-line as does almost all of the dongle copy protectiongs of the time for pro software.
And it would pretty much just be those that could benefit from that.
Btw folks dont test expanders with late time extender dongles like NetUSBee,the expanders are mostly just for same brand protect cartridges,there are some that have already busted some stuff cause of testing.

Second.
Someone would have to write a driver to interact via the interface in question(what ever that would be).
For example Cubase would need a driver for it to know that it can use some interface for popping in and out midi data.

And last,I have a feel that these network things are to skip the rather high cost of midicables and to do some basic synchro when need be,start/stop signals for equipment and such.So have to check up on that RFC document there.At least on 'public' networks all sorts of proper timing is rather off,,as everbody who has done online gaming knows.