Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Mega 2560 problem
#21

Despite the value shown on the schematic, all Pro2 PLUS boards were and are supplied with an 4 Ohms resistor at R1. Value is not very critical, it could be 4.3 Ohms, but not too high, or it will heat significantly and TFT brightness will lower.
Reply
#22

Hello

I just start troubleshooting and I guess you can advice.
1. the LCD is blank …
and when I try the Flashmemory_test it's looking blank !

Maybe something I missed …
Undecided


Attached Files Image(s)
   
Reply
#23

I think you mean the TFT display is blank...

Before installing the Meduino 2650 board on Pro2 PLUS board, do you have removed the diode illustrated on the image bellow?

[Image: mega_mini_usbmod.jpg]

This procedure is very important and referred in several places on the forum and also on the WeatherDuino Wiki.

If the diodo wasn't removed, always disconnect the USB cable before disconnecting the board mains power supply, otherwise board damage will occur.

Things to check:
- Check voltage at the 3.3V rail
- Does the 3.3V voltage regulator appear to be very hot?
- Disconnect all the wires to the TFT display and run the Flasmemory test again. Are you getting the same results?

Rgs
Reply
#24

Hi, After the construction of the pro 2 plus receiver, the transmitter, the 4pro wireless display, and the AQM II transmitter, I tested everything and everything seems to work. The only doubt I have left is that, as soon as I turn on the pro 2 plus receiver, it starts the initialization sequence and does not complete it because, to the tx transmitter, I connected only a T/H sensor and not yet an anemometer and a rain gauge. Reading several articles in the forum, it seems that the pro 2 plus receiver completes the initialization only when it receives data from all three sensors. If it does not complete initialization, the touch display remains locked. Can you confirm it? Can I somehow simulate the connection of the two missing sensors in order to cheat the receiver and thus close the sequence? Thanks
Reply
#25

(17-06-2020, 20:29)bombenm Wrote:  ...
Can I somehow simulate the connection of the two missing sensors in order to cheat the receiver and thus close the sequence?


Hi,

Yes, you can!
Just program the Pro2 PLUS to work is Test Mode. You will find how at the end of the Config_Options.h

Bear in mind that, running a system in Test mode, have some collateral effects. After you end all your test, and right before starting to use your system in prodution, you MUST perform a Factory Reset (search the forum about how to do it).


Code:
// --------------------------------------------------------------------------------------
//   Test Mode : Never run a live system in test mode
// --------------------------------------------------------------------------------------
bool Test_Mode = true;    // false= Normal working mode, true= Test mode only (no logger, no usb connection)

Rgs.
Reply
#26

(17-06-2020, 23:15)Werk_AG Wrote:  
(17-06-2020, 20:29)bombenm Wrote:  ...
Can I somehow simulate the connection of the two missing sensors in order to cheat the receiver and thus close the sequence?


Hi,

Yes, you can!
Just program the Pro2 PLUS to work is Test Mode. You will find how at the end of the Config_Options.h

Bear in mind that, running a system in Test mode, have some collateral effects. After you end all your test, and right before starting to use your system in prodution, you MUST perform a Factory Reset (search the forum about how to do it).
 
Code:
// --------------------------------------------------------------------------------------
// Test Mode : Never run a live system in test mode
// --------------------------------------------------------------------------------------
bool Test_Mode = true; // false= Normal working mode, true= Test mode only (no logger, no usb connection)

Rgs.

Hi Werk,
 Today I tried to load the latest version of software, in test mode, into the receiver, hoping that everything would work.
Unfortunately nothing happened, in the sense that the display is always frozen on the same page that I photographed.
The receiver transmits the data to the weatherduino 4pro.
I noticed that it shows three dots, two of which are green and one red.
I also photographed the system initialization and it looks good to me.
Anyone have any ideas?
In your opinion, could it be a problem with the display (connections or hardware problems)?
Thanks
Reply
#27

(18-06-2020, 20:25)bombenm Wrote:  
(17-06-2020, 23:15)Werk_AG Wrote:  
(17-06-2020, 20:29)bombenm Wrote:  ...
Can I somehow simulate the connection of the two missing sensors in order to cheat the receiver and thus close the sequence?


Hi,

Yes, you can!
Just program the Pro2 PLUS to work is Test Mode. You will find how at the end of the Config_Options.h

Bear in mind that, running a system in Test mode, have some collateral effects. After you end all your test, and right before starting to use your system in prodution, you MUST perform a Factory Reset (search the forum about how to do it).
 
Code:
// --------------------------------------------------------------------------------------
// Test Mode : Never run a live system in test mode
// --------------------------------------------------------------------------------------
bool Test_Mode = true; // false= Normal working mode, true= Test mode only (no logger, no usb connection)

Rgs.

Hi Werk,
 Today I tried to load the latest version of software, in test mode, into the receiver, hoping that everything would work.
Unfortunately nothing happened, in the sense that the display is always frozen on the same page that I photographed.
The receiver transmits the data to the weatherduino 4pro.
I noticed that it shows three dots, two of which are green and one red.
I also photographed the system initialization and it looks good to me.
Anyone have any ideas?
In your opinion, could it be a problem with the display (connections or hardware problems)?
Thanks


Attached Files Image(s)
       
Reply
#28

(18-06-2020, 20:42)bombenm Wrote:  In your opinion, could it be a problem with the display (connections or hardware problems)?

Hi,

Is the touch screen working?
At start it should not go to the Menu screen, that's why I'm asking if the touch is working.

Rgs
Reply
#29

(18-06-2020, 22:45)Werk_AG Wrote:  
(18-06-2020, 20:42)bombenm Wrote:  In your opinion, could it be a problem with the display (connections or hardware problems)?

Hi,

Is the touch screen working?
At start it should not go to the Menu screen, that's why I'm asking if the touch is working.

Rgs

No, when i turn on the receiver,  after the initialization process, it shows the menu screen and the tuch screen does not work.
Reply
#30

(18-06-2020, 23:04)bombenm Wrote:  
(18-06-2020, 22:45)Werk_AG Wrote:  
(18-06-2020, 20:42)bombenm Wrote:  In your opinion, could it be a problem with the display (connections or hardware problems)?

Hi,

Is the touch screen working?
At start it should not go to the Menu screen, that's why I'm asking if the touch is working.

Rgs

No, when i turn on the receiver,  after the initialization process, it shows the menu screen and the tuch screen does not work.
Even the display of the 4pro device does not work the touch screen.
The information is displayed by changing the various screens every few minutes.
Reply




Users browsing this thread: 1 Guest(s)