hexa | Hexa : The ultimate companion for Azure | Azure library

Lets print "hello world" as both characters, and as numbers (in hex format):

Qt allows scheduling an update for only a portion (region) of the widget, thus optimizing the result. This requires two step:

1. calling update(QRect) with an appropriate rectangle that covers only the part of the widget that requires repainting;
2. checking the event.rect() and then implement painting in order to paint only that region;

If you know for sure that only the first X rows are going to change color, then:

You can easily create it with e.g.

Thanks to @Brits i got it running. I had to use read_float(0, functioncode=4, number_of_registers=2) where 0 is decimal. If i want to read 001A i had to convert from hex to dec = 26. Works very good

I would recommend get it working between your code and a Modbus emulator, not the PLC. Once you get YOUR code working, then you can work on the PLC.

What's cool about using an emulator initially, you could also use IT to be the Master to talk to the PLC (similar to how you got your code working as the Master to the emulator as the Slave). The emulator can provide good understanding of both sides before getting the 2 ends to talk to themselves (i.e. the actual Master and the actual Slave(s)). Emulators can also provide good diagnostic details. That's one issue when diagnosing comm - which side is causing the problem (or is it a physical layer issue, e.g. wired wrong). A good emulator can help diagnose issues before doing "real" comm.

I don't know how wild for efficiency you are with this, but here's an approach!

tl;dr See this JSFiddle

To move from four players to six players, you have to understand the math that underlies the four player case and then apply it to the six player case.

You can think of each player's location as a given number of degrees (or radians) around a circle with an origin at the center of the table. In the four player case, the 1st player (index 0) will be at degrees 0, the 2nd player will be at 90 degrees, etc.

To determine how one player's movement affects the movement of a card on another person's screen that is not at the same angle, you need to break down the movement of the card in terms of its basis. In this case, the basis is composed of two orthogonal vectors that define the current player's movement space. The first vector is the vector generated using the angle. The second vector can be found by taking the current angle and adding 90 degrees (Pi/2 radians). For the four player case, the 1st player will have a primary basis vector of 0 degrees, which is (1,0). The 1st players secondary basis vector will be 0+90=90 degrees, which is (0,1).

To translate the mouse movement (delta screen x and y) into movement using an arbitrary basis, you take the dot product of delta screen x and y and the x and y of each vector in the basis. In the four player case, when the 1st player moves a card, the dot product of the primary and secondary basis result in the x delta and the y delta, respectively.

After you calculate this for the current player, you can to move the cards on other player's screens in terms of their basis. To do this, take the movement that has been converted into movement along the two bases and apply it to each other player's basis. In the four player case, the 2nd player's primary basis is 90 degrees = (1,0) and the secondary basis is 90+90 degrees = (-1,0). Thus to mirror the movement at the 2nd player's position, the original x movement is converted to y movement and the original y movement is converted to -x movement.

To change this to a game with an arbitrary number of players and with a potential offset from 0 degrees for the 1st player, you need to follow the same math. First, calculate the bases for each player. Second, use dot products to calculate the delta of the card being movement in terms of its basis. Third, apply this movement to the bases of the other players.

The example below lets you change the number of players and the starting offset angle. The cards are divs and there is a canvas superimposed over the divs to show the primary axes (red) and the secondary axes (blue) for each basis.

You forgot the result. The items key is in the result.

Your problem is in the elsecase in which you convert num[i] from char to its ascii equivalent. Thus, for instance, if you try to convert A0, the 0is converted into 48 but not 0. To correct, you should instead convert your num[i] into its equivalent integer (not in asci).

To do so, replace :