I checked them when I built the interface, but I will check again. I will order a few BAT43.Derek_Stewart wrote:Hi François,
Are the connections to the Network sockets correct?
Francois
I checked them when I built the interface, but I will check again. I will order a few BAT43.Derek_Stewart wrote:Hi François,
Are the connections to the Network sockets correct?
These sockets were very easy to figure out as the bottom is open so you can see what goes where. I am sure I wired them correctly. But to make sure I did the following measurements with the interface removed from the Q68.mk79 wrote:Hm, my money so far is on the socket. But hard to tell as I couldn't find your model anywhere. All similar looking ones had one contact come out on the top, which doesn't seem to be the case with yours.
Cheers, Marcel
The LFXP2 is usually more robust than the datasheet specifies. But in theory, only the network I/O could indeed be broken and the rest of your Q68 works well.FrancoisLanciault wrote:Peter, if you are reading this, is it conceivable that although the Q68 works well, the circuitry associated with the network is broken ? Remember that I had an issue that destroyed both my keyboard and SD card a few months ago. That is why I ask if it would be a good idea to monitor the output of the network pin (without the adapter) to see it behave correctly.
Hi Peter,Peter wrote: What you could do, is to remove your circuit and just apply GND or 3.3V to the QLNET line. Then check if you see bit 0 of PC.MCTRL (at $18020) change accordingly.
Make sure no network driver is loaded, so the Q68 does not attempt to drive the line high while you apply GND!
Sorry, these sockets were bought at a local electronic shop, so I have no number or spec sheet.Derek_Stewart wrote:Hi François,
Can you tell me what type of socket you are using?
Byte, as for the original QL.FrancoisLanciault wrote:is PC.MCTRL a byte long or a word long (peek or peek_w)
That's correct in inactive state (Bit 0 = 0). When you pull the line high, it should change.FrancoisLanciault wrote:I have checked with nothing plugged and the value of peek(hex("18020")) is 56.
Not strange at all, PC.MCTRL is a hardware register and only for byte wide access. Hardware registers don't always behave like RAM.FrancoisLanciault wrote:P.S. something is strange. The value of peek(hex("18021")) is 68. So the value of peek_w(hex("18020")) should be 14404 (56*256+68). But the value of peek_w(hex("18020")) is also 68...