WhatI want to accomplish is having a physical cable with an SD card shaped plug on one end, and something such as a USB plug on the other which I can hook into a device and feed SD format data through. I hope that makes sense.
The end goal involves a 3D printer. I have a 3D printer which only reads files from an SD card, but what I want to do is essentially hook up a Pi or such to that SD port and have the 3D printer read from a virtual drive on the Pi.
You could try using a Wifi SD card such as Toshiba Flash Air 16GB Class 10 Wireless Memory Card/Wifi SD Card- that should allow you to drop files onto the card while it's still in the printer. (You have to hope the printer spots the files changing, rather than getting a list of files at the start and working through them. Perhaps it does, perhaps not.)
I just received the flipper and everything seems to be working. Scanning and emulating of RFID tags, sending IR signals and reading NFC cards. But when I try to emulate a NFC card Flipper is showing the icon that it is emulating, but when I scan it with my phone or another NFC reader, nothing is received. I tried all sides of the flipper, and with multiple different cards.
Both can be read from my mobile phone NFC reader, but nothing is received when I try to emulate with the flipper and read from my phone (tried a oneplus and a samsung).
I also just tried the amiibu files on my nintendo switch, and it did work there.
I tried a year or so ago to add my iPhone 12 Pro to my access control system. I was to grab ids from the phone and add them to user records. I was never able to get them to work.Today for no good reason I tried with the same iPhone and os 15.5.
I was able to unlock my doors. It took multiple attempts as the iPhone cycled through ids before it hits the matching id in my access control software.I was pretty surprised and I'm now wondering how to get it to use correct sooner/consistently.
This should work. I can already unlock the my doors with my phone it just runs through a series of keys before it sends a matching key.I think I just need to establish which key belongs to my building so that there are fewer errors or turn off the beep on failure...
Tried the Wallet Creator as given above. But unfortunaly it will not work. It can provide a serialnr. But it will not scan the NFC inside the lock or card. So we have to look further. Anyone a solution?
Perhaps it's time the European Commission leaned on Apple on this front, after basically forcing them to use USB-C.This stranglehold on the NFC chip in Apple mobile devices could really be considered market protectionism.And since no tech journalist dares to mumble this, maybe the EC should.
So here's something that's not possible on the PicoGUS 2.0 card, but is on the 1.x cards as well as the Femto: WiFi. Thanks to yyzkevin again, NE2000 emulation is working on the PicoGUS with a Pico-W. It'll still be a while before it's polished: it'll need support from pgusinit to set the SSID and WPA2 password, and I'm also going to start storing card settings in flash so you don't have to run pgusinit all the time.
TBD if it can run alongside other firmwares. WiFi uses a lot of RAM and requires its own IRQ so that will limit the other emulations it can coexist with. It may be possible to have a custom ne2000 packet driver that can multiplex the IRQ with the sound card but it's probably not going to be perfect.
Since the cards are unobtainium, could someone make a tutorial how to order pcb's with smd components soldered from some pcb manufacturer? I glanced the github repo but couldn't figure out how to do it.
I think at least pcbway has some kind of project page where you can order ready made projects, I think that the project creator gets some commission too.
It's been a bit too long since my last batch but I wouldn't exactly say the cards are unobtanium. Between myself and -
1.com/ we have 1000 cards currently in production that will be available in the next few weeks. Getting more sellers lined up outside of the US is in the works as well.
BTW I haven't used PCBWay because they aren't very competitive with their assembly costs. I don't think making the design available through their shared projects makes sense, either, since those would be small orders. If someone were to order 10 boards for example, it'd cost about $100/board. PicoGUS is cool and all but as the creator and knowing all of its warts it is not in my opinion worth $100.
Edit: with emm386.exe it works on port 220 but only with himem.sys it gives that error, this is strange...
Edit2: and after few boots the same error with emm386.exe too. This started with the sb-firmware.
What does an Apple II VGA Card, a Z80-CPM SoftCard and an USB-Apple II Mouse Interface Card have in common? Well, almost everything. All three are the same card. Same hardware. Just differing software. The magic of software-defined hardware. It can emulate many things. It just depends on software.
I started a project to add USB support to the Apple II - extending the PICO-based Apple2 VGA cards. The cards are based on excellent work by Mark Aikens, David Kuder and others. The hardware is using the surprisingly powerful and flexible PICO microcontroller. The first and most obvious application of the A2USB project is a complete Apple II Mouse Interface Card emulation, supporting a USB mouse.
Recently I installed an A2VGA card, adding VGA output to my Apple II. As others in this forum, I used through-hole PCBs by Ralle Palaveev - since these are easier to tinker with than SMD boards. A nice extension to my trusty green phosphor CRT. The machine already had Ethernet + MicroSD connectors (DAN ][ Card). In another post I mentioned "probably USB should be next". Well, I wasn't joking...
If you have such card, you have already used this port to download the firmware to the PICO. But the flexible PICO comes with built-in USB Host support, so it can also act as a host controller. You can connect USB slave devices, like keyboards or mice. Just a bit of software is missing to make it all work and add USB support to the Apple II.
The first and most obvious application of A2USB is the emulation of an Apple II Mouse Interface Card. This card was introduced in 1984 (40 years ago! Happy Anniversary, Apple II Mouse Interface Card! :) ), shortly after the first Mac was launched. It consists of a peripheral interface adapter (PIA) MC6821. Cards were also made using compatible Rockwell 6520/6521 PIAs. And it has an MC6805 microcontroller as a slave device.
The microcontroller monitors the mouse buttons and movements and communicates with the Apple II's 6502 through one of the PIA's 8bit ports. It's using a very simple command based protocol: the 6502 sends commands, the slave controller responds with the requested data.
The card also has a 2KB ROM, which is mapped to the slot's 256byte address window. The ROM is split into 8 pages, which are also selected through I/O ports of the PIA. The ROM contains the necessary driver routines to communicate with the 6805 slave controller. Its interface routines are neatly documented in Apple's Mouse Interface Card manual, including programming examples in BASIC, assembler etc (oh, the good old days...).
If you followed the "DAN][ Controller" topic in this forum, then the overall design will look extremely familiar: it's the same concept. The DAN][ card just uses (slightly) different components, like the 8522 PIA (instead of an 6821/6520) and a modern ATMEGA instead of the MC6805 microcontroller. The solution using the PIA-controlled paged ROM is basically identical. (Sure, the DAN][ connects SDcards, not a mouse, but you get the idea.)
Emulating the Mouse Card on the PICO/A2VGA boards is mainly a matter of combining existing software - elements of Mark Aikens's and David Kuder's original VGA firmware and the stock PICO "tinyUSB host library". And, of course, the emulation of the PIA & Mouse Interface Card itself.
It's pretty cool but also slightly frightening to see that current tiny lower-power microcontrollers have become so powerful, they can just connect to the 6502 bus with "bit-banged" GPIO lines. And they are fast enough to run entire software routines for every single 6502 CPU cycle. And just for context: the RP2040 currently costs 80cents - much cheaper than the good old ATMEGAs (an entire PICO PCB module costs about 4-5 bucks).
If you are interested in adding an "USB Mouse Interface Card" to your Apple II, here's what you (currently) need. Remember, the project is at an early stage. Right now, a bit of tinkering is needed to apply some modifications. If you don't like tinkering and testing, better wait until updated PCBs are available - and the firmware has been tested on more machines:
If you soldered the PICO directly to the PCB, try to get a cable with really thin plug. I got one with a very thick plug (the plastic is almost 7mm high), which doesn't fit mechanically when the PICO is directly soldered on top of the Palaveev PCBs. Otherwise, if you make new boards, make sure to use pins to provide at least a few millimeters of clearance between the PCB and the PICO module. Clearance isn't an issue with David's PCBs, due to his different design (PCB doesn't protrude below the MicroUSB port).
3a8082e126