Hi
Your latest chart seems to have an issue in that I can't see the display, just the "outline".
Anyway I don't think I have your chip but I can test the component on another PIC to check activity. Probably not until the weekend though.
Regards
Search found 1725 matches
- Wed Feb 25, 2026 9:35 pm
- Forum: Bug Reports
- Topic: TM1637
- Replies: 18
- Views: 492
- Wed Feb 25, 2026 4:46 pm
- Forum: General
- Topic: SmartScope Offer
- Replies: 10
- Views: 1118
Re: SmartScope Offer
Ha ha....
- Wed Feb 25, 2026 4:04 pm
- Forum: General
- Topic: SmartScope Offer
- Replies: 10
- Views: 1118
Re: SmartScope Offer
Hi I can't imagine using it with a touchscreen, as I always have a laptop or PC around. Seems I overlooked that when I ordered. It does ask Touch / Mouse / Keyboard when opened, but the mouse option isn't great so far as I have a trackpad on laptop. I'll go through the manual when I get time and I'm...
- Wed Feb 25, 2026 2:59 pm
- Forum: General
- Topic: SmartScope Offer
- Replies: 10
- Views: 1118
Re: SmartScope Offer
Hi Eventually received my scope. Comes with two probes, a ten x F2F Dupont ribbon jumper (quality), and a dozen clips that can attach to the Dupont's plus a USB cable. It has two scope channels, an eight channel logic analyser and four digital output channels plus an AWG output. It seems to be well ...
- Wed Feb 25, 2026 8:58 am
- Forum: Bug Reports
- Topic: TM1637
- Replies: 18
- Views: 492
Re: TM1637
Hi
If that's working OK then your oscillator and chip are running at the correct speed.
As your chart simulates in v11 I can only suggest double checking all hardware connections. If you have a logic analyser / scope you could check for activity on your Data and Clock pins (B1 / B2).
Regards
If that's working OK then your oscillator and chip are running at the correct speed.
As your chart simulates in v11 I can only suggest double checking all hardware connections. If you have a logic analyser / scope you could check for activity on your Data and Clock pins (B1 / B2).
Regards
- Wed Feb 25, 2026 12:23 am
- Forum: Bug Reports
- Topic: TM1637
- Replies: 18
- Views: 492
Re: TM1637
Hi
I don't have the hardware to test with, but the "count" chart simulates OK in v11 (if brightness is set to high value).
Can you try a one-second flash test on hardware just as a sanity check?
Regards
I don't have the hardware to test with, but the "count" chart simulates OK in v11 (if brightness is set to high value).
Can you try a one-second flash test on hardware just as a sanity check?
Regards
- Wed Feb 25, 2026 12:07 am
- Forum: Bug Reports
- Topic: TM1637
- Replies: 18
- Views: 492
Re: TM1637
Hi
The above is a very different chart to the one you originally asked about.
What problem?
No display or not counting pulses?
Regards
The above is a very different chart to the one you originally asked about.
What problem?
No display or not counting pulses?
Regards
- Tue Feb 24, 2026 11:50 pm
- Forum: Bug Reports
- Topic: TM1637
- Replies: 18
- Views: 492
Re: TM1637
Hi
I am using the latest edition of FC with updated databases and if I change brightness to a high level, it works fine in simulation.
Can you be more specific with your issue?
Regards
I am using the latest edition of FC with updated databases and if I change brightness to a high level, it works fine in simulation.
Can you be more specific with your issue?
Regards
- Tue Feb 24, 2026 8:27 am
- Forum: Bug Reports
- Topic: TM1637
- Replies: 18
- Views: 492
Re: TM1637
Hi Following on from Wingnut, 3 x 1.5v AA batteries may not last very long as it looks like you will be powering relays as well as everything else, however that is a problem for another day. Also, you are using an external oscillator with a 19.xx crystal but your picture isn't clear enough to see if...
- Mon Feb 23, 2026 4:08 pm
- Forum: General
- Topic: how to check which resources (like Timers) in use
- Replies: 4
- Views: 164
Re: how to check which resources (like Timers) in use
Hi
Perhaps include the timer being used in the macro name, then a quick glance in Project Explorer would show? There may well be a better way though.
Regards
Perhaps include the timer being used in the macro name, then a quick glance in Project Explorer would show? There may well be a better way though.
Regards