 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Pico Radar
  Page 7 of 7 |
|||||
| Author | Message | ||||
phil99 Guru  Joined: 11/02/2018 Location: AustraliaPosts: 2891 |
Work-around 2. Parallel a second GP pin with the OPTION TOUCH T_ISR pin and set that to trigger your ISR. Or just add a comment above the SetPin line:- 'If Option GUI Controls has been set use OPTION GUI CONTROLS DISABLE Edited 2025-12-19 09:29 by phil99 |
||||
| ville56 Guru Joined: 08/06/2022 Location: AustriaPosts: 366 |
what a waste!!  73 de OE1HGA, Gerald |
||||
Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 8401 |
Well, not really. You are asking for two different jobs. They should be entitled to their own pins. :) Mick Zilog Inside! nascom.info for Nascom & Gemini Preliminary MMBasic docs & my PCB designs |
||||
| ville56 Guru Joined: 08/06/2022 Location: AustriaPosts: 366 |
Version V2.0.4 Mostly cleanup but added command "C" to suppress "%Radar- ...." console messages. This prevents implementations on Webmite to stop running in case there is no permanent Telnet console connection. This happens over time, but TBH I dunno why. added simple font handling in pmg routines Known probs: sometimes encountered a loop in the do_synch sub waiting for the header chars. Have to investgate deeper but currently short on spare time. I'm retired, so in reality I do not have sparetime anymore ... Radar-V2.0.4.zip 73 de OE1HGA, Gerald |
||||
| v.lenzer Regular Member  Joined: 04/05/2024 Location: GermanyPosts: 89 |
Hi Gerald! I know the problem; I'm retired too. At this point, I'd like to give you a big compliment on your work. The software is exactly as I've envisioned it since your first post. I removed the GUI Controls option. Unfortunately, the problem persists. I still get no response when I press "Menu" (with a stylus, finger, or fingernail). However, the touch calibration worked. Here are my options and pins: PicoMite MMBasic RP2040 V6.01.00RC25 OPTION SYSTEM SPI GP6,GP3,GP4 OPTION COLOURCODE ON OPTION CPUSPEED (KHz) 200000 OPTION LCDPANEL ILI9341, LANDSCAPE,GP7,GP2,GP5 OPTION TOUCH GP14,GP15 GUI CALIBRATE 0, 4174, -566, -3773, 523 GP0 1 OFF GP1 2 OFF GP2 4 Boot Reserved : LCD Reset GP3 5 Boot Reserved : SPI SYSTEM MOSI GP4 6 Boot Reserved : SPI SYSTEM MISO GP5 7 Boot Reserved : LCD CS GP6 9 Boot Reserved : SPI SYSTEM CLK GP7 10 Boot Reserved : LCD DC GP8 11 OFF GP9 12 INTL GP10 14 OFF GP11 15 OFF GP12 16 OFF GP13 17 OFF GP14 19 Boot Reserved : TOUCH CS GP15 20 Boot Reserved : TOUCH IRQ GP16 21 OFF GP17 22 OFF GP18 24 OFF GP19 25 OFF GP20 26 OFF GP21 27 OFF GP22 29 OFF GP23 41 DOUT GP24 42 DIN GP25 43 HEARTBEAT GP26 31 OFF GP27 32 OFF GP28 34 OFF GP29 44 AIN Best wishes! Joachim |
||||
| ville56 Guru Joined: 08/06/2022 Location: AustriaPosts: 366 |
Joachim, what is your line 51 in V2.0.4? In the code I published it is const touch_pin = "GP9" 'define the Touch Interrupt Pin and the matching option list is OPTION TOUCH GP10,GP9 So please check if your "option touch" setting and line 51 match. If you keep the settings from your earlier post, line 51 should read const touch_pin = "GP15" If not, change it accordingly. If they match you should try to put some debugging print statements in the sub __t_isr. At least it should be executed at every high-low transition on GP15 (in your case). You also could check the logic level on GP15. It should be high if the screen is not touched, low if touched. Just to see if the touchscreen is working correctly. Maybe you also could try to nuke the flash and reflash the firmware and settings. Sometimes there are some leftovers that can cause strange behaviours. Not often, but did happen. 73 de OE1HGA, Gerald |
||||
| v.lenzer Regular Member Joined: 04/05/2024 Location: GermanyPosts: 89 |
THANK YOU! It works great! And this is my little RADAR BASE  In line 320 I added "if cons_char ="M" or cons_char ="1" then text 310,mm.vres-mm.fontheight,cons_char 'shows mode in right bottom corner" (after I took the photo) Edited 2025-12-20 03:07 by v.lenzer Best wishes! Joachim |
||||
| ville56 Guru Joined: 08/06/2022 Location: AustriaPosts: 366 |
Cute little box, nice work indeed.  73 de OE1HGA, Gerald |
||||
| ville56 Guru Joined: 08/06/2022 Location: AustriaPosts: 366 |
some improvements ... - EXECUTE statements removed as far as possible, as this was not really reliable. Did lead to crashes sometimes. I have no idea why, but removing "execute" did cure it. It's now more code, but also more stable. - new function SWAP ... this swappes left/right. This is to have proper display depending on the direction you have the display looking to (front or back of the sensor). The side seen from the sensors view is annotated with L and R. - the settings of single/multi and swap are now saved into non volatile memory. So if set once, they are kept over system reboot/power cycle. Radar-V2.0.5.zip 73 de OE1HGA, Gerald |
||||
| v.lenzer Regular Member Joined: 04/05/2024 Location: GermanyPosts: 89 |
Very good idea about the swap feature, Gerald! And thanks for adopting the idea of displaying "Single/Multi"! I added this here for my purposes. '++++++++++++++++++++++ font settings ++++++++++++++++++++++++++ 'used for info and annotation on graphic screens and menus const fnt = 7 'font number const fnt_mul = 1 'font multiplier const lr_fnt = 1 'font for L/R annotation const lr_fnt_mul = 2 'font multiplier const grid_unit = " m" 'define grid text unit 'const grid_unit = "mm" const txt_mark_fact = 4000 'factor for distance display (4000=meters, 4=millimeters) 'const txt_mark_fact = 4 Personally, I like it better if the distance is given in meters. But that's a matter of taste. If you like, you could include this in the next update. But only if you think it's good! Edited 2025-12-21 21:35 by v.lenzer Best wishes! Joachim |
||||
| ville56 Guru Joined: 08/06/2022 Location: AustriaPosts: 366 |
will incorporate that, maybe feet could also be an option for our non-metric friends. 73 de OE1HGA, Gerald |
||||
| Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 8401 |
Feet? What's wrong with standardising on deci-cubits? It's such a simple conversion too: 1 deci-cubit = 45.7mm = 1.8in ;) Mick Zilog Inside! nascom.info for Nascom & Gemini Preliminary MMBasic docs & my PCB designs |
||||
| ville56 Guru Joined: 08/06/2022 Location: AustriaPosts: 366 |
must be 45.72 mm ... and let me guess, you want the scale numbering in roman numbers. Would at least fit the time period of the cubit.  73 de OE1HGA, Gerald |
||||
| Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 8401 |
hmmm... now there's an idea.... :) a% = &R("XVIII") Do you think it might be useful in MMBasic? Maybe not. Mick Zilog Inside! nascom.info for Nascom & Gemini Preliminary MMBasic docs & my PCB designs |
||||
| bfwolf Senior Member  Joined: 03/01/2025 Location: GermanyPosts: 103 |
I suggest not to offer feet but only inch, cause when using feet, displaying decimal fractions is AFAIK "unusual"..  Instead, feet + inch + fractional inch are written - e.g. 7'6"3/16 - and calculating this from mm is "no fun".. https://www.calculatorsoup.com/calculators/construction/feetandinches.php inch + milli-inch is at least usual for PCBs.. Edited 2025-12-22 09:35 by bfwolf |
||||
| ville56 Guru Joined: 08/06/2022 Location: AustriaPosts: 366 |
reminds me at times when we had to learn about the Whitworth threads.  . The only question in the classroom was "why". And it was not about the exact shape of the threads but the, for us then, strange fractions used to express the parameters. But all a question of getting used to, I think. For me it is still impossible to think in fractions of 2, 4, 8, 16, 32 ... but I'm used to think in powers of that  73 de OE1HGA, Gerald |
||||
| Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 8401 |
I rather like decimal inches when mm precision isn't needed. They are easy to use if you can find a rule with them on it (a dying breed, unfortunately). From my engineering days, though, I usually think in mm now, not even cm. Mind you, I rarely think of mm distances above 3000mm, they become m after that. I don't drive so km are still foreign to me and I revert to miles. I might get used to metric at some point. :) When you are laying out control panel doors on a manual drawing board 12mm to the inch is a really nice scale to work to. :) Mick Zilog Inside! nascom.info for Nascom & Gemini Preliminary MMBasic docs & my PCB designs |
||||
| ville56 Guru Joined: 08/06/2022 Location: AustriaPosts: 366 |
have now added the option to change between meters and inches on the fly. It is in the menue and it is non volatile. Also taken Joachims advise to go from mm to meter. edit: there was a silly bug ... corrected version Radar-V2.0.6.zip Edited 2025-12-23 05:39 by ville56 73 de OE1HGA, Gerald |
||||
| v.lenzer Regular Member Joined: 04/05/2024 Location: GermanyPosts: 89 |
Works perfect in two Radar-Bases! Best wishes! Joachim |
||||
| Page 7 of 7 |
|||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
