#datapoint — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #datapoint, aggregated by home.social.
-
https://www.europesays.com/ie/313124/ Digital Wallet Use Still Lags in the Physical Store #ConsumerInsights #DataPoint #DigitalWallets #Éire #FeaturedNews #IE #Ireland #Mobile #News #PaymentsIntelligence #PYMNTSIntelligence #PYMNTSNews #Technology #TheDataPoint
-
Regression learns from examples.
House size → house price.
Repeated many times.Patterns don’t come from one data point — they emerge from many.
#manytimes #house #houseprice #timepatterns #datapoint #examples
-
Week 15 Data Dump: Can Philip Rivers save Colts fantasy stars? + Identifying true LEAGUE WINNERS https://www.rawchili.com/nfl/588786/ #Chargers #Colts #DataPoint #Football #JaxsonDart #JonathanTaylor #MattHarmon #MichaelWilson #NFL #PhilipRivers #RayGarvin #YahooFantasy
-
Week 15 Data Dump: Can Philip Rivers save Colts fantasy stars? + Identifying true LEAGUE WINNERS https://www.rawchili.com/nfl/588786/ #Chargers #Colts #DataPoint #Football #JaxsonDart #JonathanTaylor #MattHarmon #MichaelWilson #NFL #PhilipRivers #RayGarvin #YahooFantasy
-
Week 14 Data Dump: Can we trust these WRs and RBs in the push for the fantasy PLAYOFFS?! https://www.rawchili.com/nfl/572079/ #ChubaHubbard #DataPoint #EmekaEgbuka #Football #JamesonWilliams #MattHarmon #NFL #RayGarvin #Steelers #YahooFantasy
-
Week 14 Data Dump: Can we trust these WRs and RBs in the push for the fantasy PLAYOFFS?! https://www.rawchili.com/nfl/572079/ #ChubaHubbard #DataPoint #EmekaEgbuka #Football #JamesonWilliams #MattHarmon #NFL #RayGarvin #Steelers #YahooFantasy
-
77% of Chief Product Officers Use Gen AI for Cybersecurity https://www.byteseu.com/1516206/ #AI #ArtificialIntelligence #cybersecurity #DataPoint #FeaturedInsights #FeaturedNews #GenerativeAI #News #PaymentsIntelligence #PYMNTSIntelligence #PYMNTSNews
-
The key switches I chose for the Datapoint 2200 keyboard required a plate so I made one up. Done as a PCB it’s not cheap but the Matt black finish works really well.
The only issue is that it slightly obstructs a couple of capacitors 🙁
I still need to source the hardware to properly mount it to the keyboard.
-
The key switches I chose for the Datapoint 2200 keyboard required a plate so I made one up. Done as a PCB it’s not cheap but the Matt black finish works really well.
The only issue is that it slightly obstructs a couple of capacitors 🙁
I still need to source the hardware to properly mount it to the keyboard.
-
The key switches I chose for the Datapoint 2200 keyboard required a plate so I made one up. Done as a PCB it’s not cheap but the Matt black finish works really well.
The only issue is that it slightly obstructs a couple of capacitors 🙁
I still need to source the hardware to properly mount it to the keyboard.
-
The key switches I chose for the Datapoint 2200 keyboard required a plate so I made one up. Done as a PCB it’s not cheap but the Matt black finish works really well.
The only issue is that it slightly obstructs a couple of capacitors 🙁
I still need to source the hardware to properly mount it to the keyboard.
-
The key switches I chose for the Datapoint 2200 keyboard required a plate so I made one up. Done as a PCB it’s not cheap but the Matt black finish works really well.
The only issue is that it slightly obstructs a couple of capacitors 🙁
I still need to source the hardware to properly mount it to the keyboard.
-
Top row numbers can be shifted and keypad numbers can't. Both share an edge detector circuit and multiplexer 'line'. Top row key short to ground whereas keypad key have an SIO (or S10) signal. The keyboard logic board uses an analogue edge detector with 74121 pulse generator.
On the Pico I'm handling this by driving the SIO line low. When a keypress is detected I drive it high. If the keypress is still detectable then it's a top row key. If not then keypad.
-
Top row numbers can be shifted and keypad numbers can't. Both share an edge detector circuit and multiplexer 'line'. Top row key short to ground whereas keypad key have an SIO (or S10) signal. The keyboard logic board uses an analogue edge detector with 74121 pulse generator.
On the Pico I'm handling this by driving the SIO line low. When a keypress is detected I drive it high. If the keypress is still detectable then it's a top row key. If not then keypad.
-
Top row numbers can be shifted and keypad numbers can't. Both share an edge detector circuit and multiplexer 'line'. Top row key short to ground whereas keypad key have an SIO (or S10) signal. The keyboard logic board uses an analogue edge detector with 74121 pulse generator.
On the Pico I'm handling this by driving the SIO line low. When a keypress is detected I drive it high. If the keypress is still detectable then it's a top row key. If not then keypad.
-
Top row numbers can be shifted and keypad numbers can't. Both share an edge detector circuit and multiplexer 'line'. Top row key short to ground whereas keypad key have an SIO (or S10) signal. The keyboard logic board uses an analogue edge detector with 74121 pulse generator.
On the Pico I'm handling this by driving the SIO line low. When a keypress is detected I drive it high. If the keypress is still detectable then it's a top row key. If not then keypad.
-
Top row numbers can be shifted and keypad numbers can't. Both share an edge detector circuit and multiplexer 'line'. Top row key short to ground whereas keypad key have an SIO (or S10) signal. The keyboard logic board uses an analogue edge detector with 74121 pulse generator.
On the Pico I'm handling this by driving the SIO line low. When a keypress is detected I drive it high. If the keypress is still detectable then it's a top row key. If not then keypad.
-
The #Datapoint2200 keyboard PCBs have arrived and they look fantastic. Somehow larger than I expected, and very imposing.
#datapoint #ttlcomputer #vintagecomputer #retroconputer #mechanicalkeyboard
-
The #Datapoint2200 keyboard PCBs have arrived and they look fantastic. Somehow larger than I expected, and very imposing.
#datapoint #ttlcomputer #vintagecomputer #retroconputer #mechanicalkeyboard
-
The #Datapoint2200 keyboard PCBs have arrived and they look fantastic. Somehow larger than I expected, and very imposing.
#datapoint #ttlcomputer #vintagecomputer #retroconputer #mechanicalkeyboard
-
The #Datapoint2200 keyboard PCBs have arrived and they look fantastic. Somehow larger than I expected, and very imposing.
#datapoint #ttlcomputer #vintagecomputer #retroconputer #mechanicalkeyboard
-
The #Datapoint2200 keyboard PCBs have arrived and they look fantastic. Somehow larger than I expected, and very imposing.
#datapoint #ttlcomputer #vintagecomputer #retroconputer #mechanicalkeyboard
-
Went out to dinner tonight with a red friend. Not a lawyer, not online, said he gets most of his info from the WSJ. Anyway, he wants Trump gone. #datapoint
RE: https://bsky.app/profile/did:plc:cz3p35o2uexpt6l5sngcnu2j/post/3lkqzv3ts722h -
Went out to dinner tonight with a red friend. Not a lawyer, not online, said he gets most of his info from the WSJ. Anyway, he wants Trump gone. #datapoint
RE: https://bsky.app/profile/did:plc:cz3p35o2uexpt6l5sngcnu2j/post/3lkqzv3ts722h -
Went out to dinner tonight with a red friend. Not a lawyer, not online, said he gets most of his info from the WSJ. Anyway, he wants Trump gone. #datapoint
RE: https://bsky.app/profile/did:plc:cz3p35o2uexpt6l5sngcnu2j/post/3lkqzv3ts722h -
I've now added some photos to the repository (link in previous toot). Not the best quality but there's now something to look at.
Here's a couple of those for the Decoder PCB. There are more in the repository itself.
-
I've now added some photos to the repository (link in previous toot). Not the best quality but there's now something to look at.
Here's a couple of those for the Decoder PCB. There are more in the repository itself.
-
I've now added some photos to the repository (link in previous toot). Not the best quality but there's now something to look at.
Here's a couple of those for the Decoder PCB. There are more in the repository itself.
-
I've now added some photos to the repository (link in previous toot). Not the best quality but there's now something to look at.
Here's a couple of those for the Decoder PCB. There are more in the repository itself.
-
I've now added some photos to the repository (link in previous toot). Not the best quality but there's now something to look at.
Here's a couple of those for the Decoder PCB. There are more in the repository itself.
-
I've just pushed a very long overdue update to my Datapoint 2200 repository.
New stuff includes schematics for video, keyboard and keyboard logic.
I've added a fair few LEDs to the processor PCB for most of the main registers, but I need to analyse which other signals deserve to have them.
I also need to add some photos and PCB renders to the readme.
-
I've just pushed a very long overdue update to my Datapoint 2200 repository.
New stuff includes schematics for video, keyboard and keyboard logic.
I've added a fair few LEDs to the processor PCB for most of the main registers, but I need to analyse which other signals deserve to have them.
I also need to add some photos and PCB renders to the readme.
-
I've just pushed a very long overdue update to my Datapoint 2200 repository.
New stuff includes schematics for video, keyboard and keyboard logic.
I've added a fair few LEDs to the processor PCB for most of the main registers, but I need to analyse which other signals deserve to have them.
I also need to add some photos and PCB renders to the readme.
-
I've just pushed a very long overdue update to my Datapoint 2200 repository.
New stuff includes schematics for video, keyboard and keyboard logic.
I've added a fair few LEDs to the processor PCB for most of the main registers, but I need to analyse which other signals deserve to have them.
I also need to add some photos and PCB renders to the readme.
-
I've just pushed a very long overdue update to my Datapoint 2200 repository.
New stuff includes schematics for video, keyboard and keyboard logic.
I've added a fair few LEDs to the processor PCB for most of the main registers, but I need to analyse which other signals deserve to have them.
I also need to add some photos and PCB renders to the readme.
-
#Datapoint 2200: I have the memory cards designed and assembled but no memory chips. My plan is to add a 'backpack' board using modern parts.
Each card uses 32x 512 bit shift memory chips. The best modern option is probably 512 bit FIFOs and tie the outputs back to the inputs to recirculate data.
You can get 9-bit or 18-bit wide chips but every bit is read and written together. So you need a multiplexer on each bit to select new data or recirculate.
🧵
-
#Datapoint 2200: I have the memory cards designed and assembled but no memory chips. My plan is to add a 'backpack' board using modern parts.
Each card uses 32x 512 bit shift memory chips. The best modern option is probably 512 bit FIFOs and tie the outputs back to the inputs to recirculate data.
You can get 9-bit or 18-bit wide chips but every bit is read and written together. So you need a multiplexer on each bit to select new data or recirculate.
🧵
-
#Datapoint 2200: I have the memory cards designed and assembled but no memory chips. My plan is to add a 'backpack' board using modern parts.
Each card uses 32x 512 bit shift memory chips. The best modern option is probably 512 bit FIFOs and tie the outputs back to the inputs to recirculate data.
You can get 9-bit or 18-bit wide chips but every bit is read and written together. So you need a multiplexer on each bit to select new data or recirculate.
🧵
-
#Datapoint 2200: I have the memory cards designed and assembled but no memory chips. My plan is to add a 'backpack' board using modern parts.
Each card uses 32x 512 bit shift memory chips. The best modern option is probably 512 bit FIFOs and tie the outputs back to the inputs to recirculate data.
You can get 9-bit or 18-bit wide chips but every bit is read and written together. So you need a multiplexer on each bit to select new data or recirculate.
🧵
-
#Datapoint 2200: I have the memory cards designed and assembled but no memory chips. My plan is to add a 'backpack' board using modern parts.
Each card uses 32x 512 bit shift memory chips. The best modern option is probably 512 bit FIFOs and tie the outputs back to the inputs to recirculate data.
You can get 9-bit or 18-bit wide chips but every bit is read and written together. So you need a multiplexer on each bit to select new data or recirculate.
🧵
-
What's the main challenge in assembling old code on a modern(ish) assembler? The old assemblers only consider the first few letters of a mnemonic significant. The 8008 has an INC opcode. My assembler has an INCLUDE directive.
(The old code doesn't use INCLUDE, but I need to import symbols from other files. The easy way is to write public symbols to a file in suitable format for an INCLUDE).
-
What's the main challenge in assembling old code on a modern(ish) assembler? The old assemblers only consider the first few letters of a mnemonic significant. The 8008 has an INC opcode. My assembler has an INCLUDE directive.
(The old code doesn't use INCLUDE, but I need to import symbols from other files. The easy way is to write public symbols to a file in suitable format for an INCLUDE).
-
What's the main challenge in assembling old code on a modern(ish) assembler? The old assemblers only consider the first few letters of a mnemonic significant. The 8008 has an INC opcode. My assembler has an INCLUDE directive.
(The old code doesn't use INCLUDE, but I need to import symbols from other files. The easy way is to write public symbols to a file in suitable format for an INCLUDE).
-
What's the main challenge in assembling old code on a modern(ish) assembler? The old assemblers only consider the first few letters of a mnemonic significant. The 8008 has an INC opcode. My assembler has an INCLUDE directive.
(The old code doesn't use INCLUDE, but I need to import symbols from other files. The easy way is to write public symbols to a file in suitable format for an INCLUDE).
-
What's the main challenge in assembling old code on a modern(ish) assembler? The old assemblers only consider the first few letters of a mnemonic significant. The 8008 has an INC opcode. My assembler has an INCLUDE directive.
(The old code doesn't use INCLUDE, but I need to import symbols from other files. The easy way is to write public symbols to a file in suitable format for an INCLUDE).
-
I wrote a Z80 assembler a few years ago. Thankfully I subclassed out the Z80 specific stuff. I've been updating it for Datapoint mnemonics and syntax.
I've also typed in the #Datapoint operating system listing from the Programmers Manual (46 pages. Nothing to a child of the 80s).
I'm now working through the files to get them to assemble. Currently there's a circular reference to resolve (comment out on first build), a couple of directives to add and an opcode which doesn't officially exist.
-
I wrote a Z80 assembler a few years ago. Thankfully I subclassed out the Z80 specific stuff. I've been updating it for Datapoint mnemonics and syntax.
I've also typed in the #Datapoint operating system listing from the Programmers Manual (46 pages. Nothing to a child of the 80s).
I'm now working through the files to get them to assemble. Currently there's a circular reference to resolve (comment out on first build), a couple of directives to add and an opcode which doesn't officially exist.
-
I wrote a Z80 assembler a few years ago. Thankfully I subclassed out the Z80 specific stuff. I've been updating it for Datapoint mnemonics and syntax.
I've also typed in the #Datapoint operating system listing from the Programmers Manual (46 pages. Nothing to a child of the 80s).
I'm now working through the files to get them to assemble. Currently there's a circular reference to resolve (comment out on first build), a couple of directives to add and an opcode which doesn't officially exist.
-
I wrote a Z80 assembler a few years ago. Thankfully I subclassed out the Z80 specific stuff. I've been updating it for Datapoint mnemonics and syntax.
I've also typed in the #Datapoint operating system listing from the Programmers Manual (46 pages. Nothing to a child of the 80s).
I'm now working through the files to get them to assemble. Currently there's a circular reference to resolve (comment out on first build), a couple of directives to add and an opcode which doesn't officially exist.
-
I wrote a Z80 assembler a few years ago. Thankfully I subclassed out the Z80 specific stuff. I've been updating it for Datapoint mnemonics and syntax.
I've also typed in the #Datapoint operating system listing from the Programmers Manual (46 pages. Nothing to a child of the 80s).
I'm now working through the files to get them to assemble. Currently there's a circular reference to resolve (comment out on first build), a couple of directives to add and an opcode which doesn't officially exist.