Great work!
Is there a file I can drop into easyeda to rework the pcb?
2 Likes
The kicad files are posted
1 Like
I don’t know know how to use/nav github
it’s showing code but not a file to dl
This is the correct link.
Okay I click on thumbwheel but it’s showing cad files don’t I want a kitcad format zip to drop into easyeda
Oooh grab everything then extract the file thanks
2 Likes
Kicad doesn’t wanna make files compatible with easyeda, so I had redo the whole thing from the schematic to make some changes.
Wanted to make it as small as possible to allow alot of different case shape options.
Still gotta do the ground pour, add logos and increasing trace size as much as allowable.
This is opposite.
Kicad is free & open source software. Easyeda doesn’t want to import Kicad files unless you pay them.
2 Likes
I mean unless easyeda is full of shit, they have option to import kicad files but per their instructions the export option from kicad as zip has been removed.
Even messing with the files from github, showing hidden files, and rezipping didn’t work. couldn’t even get the schematic to import just a really shit version of the pcb that was basically useless.
Careful!
According to the datasheet of the module, it is highly discouraged to have the PCB antenna directly on top of another board. It can affect the performance in very unexpected ways. If you still wanna risk it, at least make sure there is no copper whatsoever underneath the antenna section.
6 Likes
I was thinking of using an IPEX antenna coming off the board.
How’s the reset button on the mini? I made the pcb pads so when you remove it from the mini you can solder it onto the fancy.
After crashing quite a lot of FPV drones I’m not a fan of IPEX connectors on things subjected to heavy vibrations, and I wouldn’t risk it on something I’m riding…you should at least check out ways to secure it properly such as using a pigtail with an IPEX MHF I LK locking connector:
https://www.i-pex.com/product/mhf-I-lk
The reset button is a simple momentary button that if I’m not mistaken shorts the RST pin with GND. I find it quite useless in this application, but sure, its functionatlity can be emulated as you did. Make sure the arduinos you get use the same button footprint though! (For example the official arduino pro mini uses a different one)
3 Likes
I meant as a replacement for the button you used on the fancy not a reset.
It’s too small for the shells I designed and not very sturdy for my taste, but with an appropriate 3D printed extension it could work. I would rather use a different one with more travel and “clicky” feeling though.
3 Likes
Can I get a second set of eyes on this output?
19:19:24.495 → Frequency: 2497500000Hz
19:19:24.495 → Ellapsed: 2.00s | VBat: 0.00V | SNR: 13dB | RSSI: -32dBm
19:19:24.495 → -------------- TASKS --------------
19:19:24.495 → receiveThrottlePacket | 30Hz
19:19:24.495 → writePPMValue | 49Hz
19:19:24.495 → sendTMPacket | 2Hz
19:19:24.495 → checkBattery | 1Hz
19:19:24.495 → setLEDs | 10Hz
19:19:24.495 → -----------------------------------
19:19:24.495 → Packets/s: 30
19:19:24.495 → TM packets/s: 2
19:19:24.495 → Errors: 0
19:19:26.447 → ////////ERROR//////////
19:19:26.540 → Incorrect identity 203
19:19:26.540 → //////////////////////
19:19:26.540 → Frequency: 2497500000Hz
19:19:26.540 → Ellapsed: 2.00s | VBat: 0.00V | SNR: 12dB | RSSI: -32dBm
19:19:26.540 → -------------- TASKS --------------
19:19:26.540 → receiveThrottlePacket | 20Hz
19:19:26.540 → writePPMValue | 49Hz
19:19:26.540 → sendTMPacket | 1Hz
19:19:26.540 → checkBattery | 1Hz
19:19:26.540 → setLEDs | 10Hz
19:19:26.540 → -----------------------------------
19:19:26.540 → Packets/s: 19
19:19:26.540 → TM packets/s: 1
19:19:26.540 → Errors: 1
19:19:28.493 → ////////ERROR//////////
19:19:28.540 → Receive timeout
19:19:28.540 → //////////////////////
19:19:28.540 → Frequency: 2497500000Hz
19:19:28.540 → Ellapsed: 2.00s | VBat: 0.00V | SNR: -100dB | RSSI: -100dBm
19:19:28.540 → -------------- TASKS --------------
19:19:28.540 → receiveThrottlePacket | 10Hz
19:19:28.540 → writePPMValue | 45Hz
19:19:28.540 → sendTMPacket | 1Hz
19:19:28.540 → checkBattery | 1Hz
19:19:28.540 → setLEDs | 10Hz
19:19:28.540 → -----------------------------------
19:19:28.540 → Packets/s: 10
19:19:28.540 → TM packets/s: 1
19:19:28.540 → Errors: 2
19:19:30.586 → ////////ERROR//////////
19:19:30.586 → Incorrect identity 139
19:19:30.586 → //////////////////////
19:19:30.586 → Frequency: 2497500000Hz
19:19:30.586 → Ellapsed: 2.00s | VBat: 0.00V | SNR: 13dB | RSSI: -32dBm
19:19:30.586 → -------------- TASKS --------------
19:19:30.586 → receiveThrottlePacket | 16Hz
19:19:30.586 → writePPMValue | 48Hz
19:19:30.586 → sendTMPacket | 2Hz
19:19:30.586 → checkBattery | 1Hz
19:19:30.586 → setLEDs | 10Hz
19:19:30.586 → -----------------------------------
19:19:30.586 → Packets/s: 16
19:19:30.586 → TM packets/s: 2
19:19:30.586 → Errors: 2
19:19:32.585 → ////////ERROR//////////
19:19:32.632 → Incorrect identity 139
19:19:32.632 → //////////////////////
19:19:32.632 → Frequency: 2497500000Hz
19:19:32.632 → Ellapsed: 2.00s | VBat: 0.00V | SNR: 12dB | RSSI: -31dBm
19:19:32.632 → -------------- TASKS --------------
19:19:32.632 → receiveThrottlePacket | 29Hz
19:19:32.632 → writePPMValue | 49Hz
19:19:32.632 → sendTMPacket | 2Hz
19:19:32.632 → checkBattery | 1Hz
19:19:32.632 → setLEDs | 10Hz
19:19:32.632 → -----------------------------------
19:19:32.632 → Packets/s: 28
19:19:32.632 → TM packets/s: 2
19:19:32.632 → Errors: 1
19:19:34.631 → ////////ERROR//////////
19:19:34.678 → Incorrect identity 203
19:19:34.678 → //////////////////////
19:19:34.678 → Frequency: 2497500000Hz
19:19:34.678 → Ellapsed: 2.00s | VBat: 0.00V | SNR: 12dB | RSSI: -31dBm
19:19:34.678 → -------------- TASKS --------------
19:19:34.678 → receiveThrottlePacket | 16Hz
19:19:34.678 → writePPMValue | 49Hz
19:19:34.678 → sendTMPacket | 2Hz
19:19:34.678 → checkBattery | 1Hz
19:19:34.678 → setLEDs | 10Hz
19:19:34.678 → -----------------------------------
19:19:34.678 → Packets/s: 15
19:19:34.678 → TM packets/s: 2
19:19:34.678 → Errors: 2
19:19:36.724 → ////////ERROR//////////
19:19:36.724 → Receive timeout
2 register tests work fine on both but weirdly my radio resets every few seconds on tx. can see SNR: -100dB | RSSI: -100dBm a few times - I can’t figure out why seeing that 2 registers works perfectly on both rx and tx
Can you check that the antenna is correctly selected on both modules? That output is a symptom of very low power output/poor Rx sensitivity.
1 Like
yeah, just looked all good. I am thinking it might be the buck not supplying a clean 5v
How are you setting up your connection to the computer to get these traces?
During all my testing I hooked up the RX to a regulated power supply set to 5V (simulating the VESC) while the FTDI had the power jumper removed.
When I had no battery on it, the TX was being fed 3.3V using the FTDI chip (with the jumper in the correct position).
Is it possible that you have set your FTDI to 5V and the LoRa module is being cooked?
P.D: Not actually an FTDI but a clone, sometimes a CH340, but basically any chinese USB-to-serial converter works the same.